Change CesiumCameraController
and CesiumFlyToController
to use CesiumGlobeAnchor
on parent GameObjects
#422
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #415.
Currently, the
CesiumCameraController
andCesiumFlyToController
expect to be on an object with aCesiumOriginShift
andCesiumGlobeAnchor
present. This makes it difficult to setup on XR rigs, as detailed in the issue above. This changes both classes to useCesiumGlobeAnchor
components present on parent objects, while using theReset
event to still create an anchor if none is present, as was the previous behavior.