New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose model ready through the Entity API #4727
Comments
also reported here: https://groups.google.com/forum/#!topic/cesium-dev/25XIuI25F7A |
The approach described in that forum post is flawed. 3D Tiles are the way to do what they want. I'm still not convinced we'll ever need this as there is always a better way to do what our users want without this functionality (and having this functionality will lead them down a bad implementation path). There could be exceptions, but I haven't heard them yet. |
Congratulations on closing the issue! I found these Cesium forum links in the comments above: https://groups.google.com/forum/#!topic/cesium-dev/25XIuI25F7A If this issue affects any of these threads, please post a comment like the following:
I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome. 🌍 🌎 🌏 |
Here's a potential use case that can't be done in the Entity layer that I don't see addressed here. This forum thread is trying to use Thoughts? |
This person wants to show a loading screen until all of the textures have finished loading on his glTF model: |
I think another thing that could solve that user's issue is if they could toggle the |
I don't have a good answer for what to do for things like this, other than "don't use the entity API for models" =/ There's a reason we didn't add 3D Tiles to the Entity API. If you want more control, you need to work with the primitives at a lower level. These kind of use-cases are just really not what the Entity API was designed for. |
Actually, I just realized It's still annoying that you can't control whether entities are async or not, but I think adding a flag there too would solve so many cases where I as a developer would rather risk frame drops rather than showing an entity and having it appear on screen an unknown amount of frames later. It sounds like this would be easy to add a toggle for unless I'm missing something. |
Just want to add here, I think exposing a generic |
Users want to know when the model is ready so they can have custom functionality when the model is loading and when the scene is ready
From #3910:
Maybe tie it into the boolean returned from
DataSourceDisplay.update
? This boolean is supposed to the true when when all data sources are ready to be displayed and false otherwise.The text was updated successfully, but these errors were encountered: