-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Tracking of ellipsoids still not quite working. #4929
Comments
The red sphere above is a bit of a red herring, the real problem is the selection indicator (and the If it looks like the green crosshairs are hanging out at some kind of midpoint between the entity's position and its original position, you're correct, it's the midpoint. What's happening here is that at load time, a new bounding sphere is created for the Ellipsoid graphics, just once, based on whatever Prior to the fix in #4907, dynamic graphics would recalculate their bounding sphere every frame, by pulling a copy of the cached attribute bounding sphere and transforming it by the current modelMatrix. But the fix removed this modelMatrix transform, and as a result the ellipsoid's bounding sphere is frozen in time, correct only for the time of construction of the ellipsoid. At a higher level, Viewer is trying to figure out what to track or select, and asks the entity. The entity then enumerates its primitives, and combines their bounding spheres. In this case, the entity's point graphics are reporting their own bounding sphere, with the correct center point, and the ellipsoid graphics are reporting an out-dated bounding sphere, with an out-dated center point. The entity then combines these two bounding spheres, and finds a center point halfway between the current position and the out-dated position. This then becomes the selected/tracked location. |
Also reported here: https://groups.google.com/forum/?hl=en#!topic/cesium-dev/rCBSbMx8Xmk |
I labeled this |
Not sure if this is an incomplete fix for #4866, or something new. Check out this demo:
The text was updated successfully, but these errors were encountered: