Garrett Johnson

Thanks - I'm not sure my other approach was unloading tiles. As I mentioned it looks like this is just related to the default cache size of the TilesRenderer. In...

@Brakebein this issue is for data overlays that contain an arbitrary level of procedural detail like GeoJSON. Please make a new issue for your question.

Related to https://github.com/NASA-AMMOS/3DTilesRendererJS/issues/943#issuecomment-3435625747 It would be best to remove any possible dependency on the "capabilities" object or data shapes from XML loaders since the best way for users to use...

This can be done by removing the "used" check from the cache (and the "loaded" check can be moved to the priority callback) but the fade plugin is not so...

You've mentioned it in the other issue but this should be fixed with https://github.com/NASA-AMMOS/3DTilesRendererJS/commit/8266a35af1db54b22589158f07f7510c030eaac9 & #1274. That bug in effect meant that "enableTileSplitting" wasn't working when used with quantized mesh...

> I would like to have the overlayed aerial imagery to be loaded at zoom level 20 and keeping the 3d buildings at zoom level 10. Thanks I understand, now...

> Do you expect me to submit a PR? I know it's not always obvious what the source of the current behavior might be so I generally just wanted to...

Thinking this through a bit more - this can be a bit difficult to design this so it "just works". It's possible to infer something akin to a "geometric error"...

Sorry in advance for the long response - just trying to get some thoughts out and this is not necessarily an intuitive topic 😅 > Thank you for giving another...

Thanks @shotamatsuda! And sorry for the delay in reply. I suppose some (all?) of my concerns from https://github.com/mrdoob/three.js/issues/30185 are finally coming to pass, so I'm trying to decide what to...