Matthew Amato
Matthew Amato
@j9liu While I understand what is happening, I still think the overall demo would be very confusing to new users. In reality, we need to majorly rethink all of our...
@javagl I agree that the way CesiumJS is failing here is not very useful and a clear error message or warning about lack of sparse accessors would be the least...
I've seen other globes (at least WorldWind I think) handle this using a separate class, we could call ours `CameraLimiter` or something similar. This class would allow you to set...
Yep, I would love to see this because we'll have good use for it on cesium.com, has been on my todo list forever. I've has discussions with bagnell in the...
@OmarShehata also had some thoughts in https://github.com/AnalyticalGraphicsInc/cesium/issues/8143#issue-491026306
This doesn't seem to happen when devicePixelRatio is 1.0 (at least I don't see the problem on my achine), so I think you're right that it's #8351 related.
@lilleyse @IanLilleyT Since this is a recent regression, any change we can get to it for the next release? (It's okay if the answer is no, just figured I'd ask)....
I assume this is a trivial fix, but @bagnell can you confirm that there's no reason we should be calling `setReady` every frame?
@javagl Unfortunately I don't think one exists. This doesn't affect my project directly, but I wanted to write it up since we noticed it.
Thanks @javagl this definitely looks like a clear cut bug. Even though the model loads in all of the most popular tools, we definitely want to produce content that validates...