You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 2 itowns view loaded on the same page.
On each view, I'm loading a 3dtiles dataset.
I have to wait for the 3dtiles from the first view to finish loading before seeing the tiles from the second view.
Also, when I switch from one view to the other, the 3dtiles disappear and starts requesting all the tiles again.
Context
Manage 2 view with 3dtiles in each
Steps to Reproduce
Create 2 views with 2 3dtile dataset
Interact with each view
Observe that the whole dataset disappear before reloading completely
We indeed share the 3D tiles cache, download and parse queues among all tilesets.
With this new use case in mind, one solution would be to share them per view. To do so, we could:
Add an id property to View
Declare a Map of 3DTilesRendererJS with the view id as key and lruCache, downloadQueue and parseQueue as value.
Take care of filling this map and setting up the cache and queues in OGC3DTilesLayer._setup (that is called by View.addLayer(3DTilesLayer))
That would have the advantages to manage 3DTiles independently for each view and to take care of this setup for our users (which in many cases won't want to deal with this kind of stuff I think). I also can't think of any usecase where one would want to share the same cache and queues amongst views.
I have 2 itowns view loaded on the same page.
On each view, I'm loading a 3dtiles dataset.
I have to wait for the 3dtiles from the first view to finish loading before seeing the tiles from the second view.
Also, when I switch from one view to the other, the 3dtiles disappear and starts requesting all the tiles again.
Context
Manage 2 view with 3dtiles in each
Steps to Reproduce
Screencast.from.04-10-2024.15.11.49.webm
Possible Cause/Fix/Solution
Looks like it's caused by:
itowns/src/Layer/OGC3DTilesLayer.js
Line 197 in c862ca7
The text was updated successfully, but these errors were encountered: