Right now some plugins will dynamically expand their children when loading geometry and delete the children when disposing the tile. However this means that the loaders don't behave as expected when the optimized "loadAncestors" setting is set to false since children aren't available until the parents are processed.
Somehow we need to know that an unloaded tile can "expand" further as well as afford unloading. Using a mechanism similar to "external tilesets" may work? Eg automatically insert an "external" node that will instantiate 3-4 layers of nodes. Then disposal should "just work" as it does with external tile sets.
The affected plugins:
- ImageFormatPlugins (deprecated)
- GeneratedSurfacePlugin
- QuantizedMeshPlugin
Right now some plugins will dynamically expand their children when loading geometry and delete the children when disposing the tile. However this means that the loaders don't behave as expected when the optimized "loadAncestors" setting is set to false since children aren't available until the parents are processed.
Somehow we need to know that an unloaded tile can "expand" further as well as afford unloading. Using a mechanism similar to "external tilesets" may work? Eg automatically insert an "external" node that will instantiate 3-4 layers of nodes. Then disposal should "just work" as it does with external tile sets.
The affected plugins: