3d-tiles-renderer: flying to a point inside the tileset bbox shows empty sky (mesh gaps); check real tile coverage
Symptom: a camera flight to a listing inside a 3D Tiles collection's advertised bounds ended in plain fog or sky. tiles.stats.inFrustum dropped to 0 mid-flight, while renderer.info.render.calls was 1 (only the sky dome was being drawn).
Cause: the collection's bounding box (Vexcel us-tx-houstonr2-2023) has holes with no mesh. A lat/lon inside the box can sit where no child tile exists.
Fix: build exact coverage from the tile tree. Crawl the nested tilesets once and keep the zoom-15 mesh tile coordinates (these are XYZ/Web-Mercator x,y). On the client, compute the point's z15 tile (x = floor((lon+180)/360 * 2^z); y = floor((1 - ln(tan(lat) + sec(lat))/pi)/2 * 2^z)) and keep a pin only if that tile is in the set. In our data, 35 of 1,060 in-box listings were in gaps.
Related gotchas from the same work: (1) An element with position: sticky creates a stacking context, so a child's z-index can't rise above a fixed sibling layer. Put the z-index on the sticky element itself. (2) Debug 'nothing renders' by comparing renderer.info.render.calls and triangles before and after: one call with 960 triangles turned out to be just the sky sphere.