1. A concise explanation of the problem you’re experiencing.
We
finally have our Cesium Site to a point where we will be able to show it about.
I have a technical question, if this is an appropriate place to ask it. We
have been moving our Virtual Cities Project data to Cesium. Two typical URLs of
concern would be:
http://comp.umsl.edu/vcities/SLhistory.html ->
The Scott Joplin Neighborhood from the drop down list. In both cases the
concern is building model count. For example, regarding the first, we would
want to consider populating the entire riverfront with existing models. Rather
than 3 Blocks, there might be, say, 30. Is there cache/buffer limits that
we need to consider? Where might I look to understand limitations that might
exist? Any advice would be much appreciated.
2. A minimal code example. If you’ve found a bug, this helps us reproduce and repair it.
3. Context. Why do you need to do this? We might know a better way to accomplish your goal.
4. The Cesium version you’re using, your operating system and browser.
Exciting to see the progress on this project! For cache/buffer limits, do you mean limits on requesting these models from the ion server (if you’re using ion) or limits on the browser itself? CesiumJS should be able to use as much memory as the browser allows it on the device it’s running on. So for that, I would just profile your application with Chrome/Firefox’s debugger tools to see how much memory it’s using. There’s no standard limit that I’m aware of.
Glad to hear it! If you can isolate any issues that aren’t already documented here (https://github.com/AnalyticalGraphicsInc/cesium) we’d definitely love to hear. I can imagine there might be a bit of a slow down when creating too many objects (and there might be ways to make it faster) but bugs/crashes shouldn’t happen.