Closed kfarr closed 1 month ago
This appears to be an issue in our application and not caused by this repo. In some cases we did not fire runtime.orientToGeocoord
therefore 65 tiles is a successful completion of loading 3dtiles for lat/lon/height 0/0/0 otherwise known as null island
I have experienced and we have user reported errors that sometimes the 3dtiles don't load without an error message. A workaround is to reload the page or to remove / re-add the 3dtiles a-frame component.
I added onProgress logging and a three.js LoadingManager to observe patterns in these "stalled load" attempts. I noticed that in these cases it loads 65 tiles and then LoadingManager fires complete event. [1]
A "real" tile load will result in 300+ tiles before being marked as complete by three.js loadingmanager. [2]
We can create workarounds such as a "watchdog" to test for loading complete with <100 tiles and then automatically reload, or raycaster to see if there is actual a visible ground point etc, but I first wanted to first check and see if this is a known issue.
[1] tiles not loading
[2] tiles loading as expected