Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Tileset being selected for rendering on the other side of the globe?
See original GitHub issue-
Start this Sandcastle Which loads the Montreal tileset. It also has a postRender event registered which prints out the number of montreal tiles selected for rendering whenever the selected value changes.
-
Type
Jamaicainto the geocoder and fly there. (Still 0 tiles selected for rendering) -
Tilt the camera towards the horizon, you’ll notice that the root tile of Montreal gets selected, even though it is well below the horizon practically on the other side of the earth. Zooming in close to the ground doesn’t fix this either, the moment you are looking at the horizon, it selects the tile.
This seems to happens whether terrain or depthTestAgainstTerrain is on or off, so I don’t think that’s the problem. @likangning93 thinks maybe something is wrong with horizon culling?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Even if horizon culling is the culprit, I’m surprised that sse is satisfied for the root tile that far away.
In cesium-native, we don’t do horizon culling at all, because using the ellipsoid is an occluder is unreliable when terrain and photogrammetry may be below it. However, a tile like this on the other side of the globe will get culled by fog. Could be worth doing something similar in CesiumJS if we’re not already.