Resync gizmo body on parent object move [SYNTH-334] - #1484
Merged
Conversation
azaleacolburn
approved these changes
Aug 14, 2026
| /** | ||
| * Re-seats the gizmo on its parent after something other than this gizmo moved the parent. | ||
| */ | ||
| public syncToParent() { |
Contributor
There was a problem hiding this comment.
Might want to mark this as unused so people know not to remove it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Task
SYNTH-334
Symptom
GizmoSceneObjectcaches ceach rigid body's transform relative to the gizmo once at construction. If the parent object moves afterward through something other than the gizmo that cache goes stale and causes the gizmo to be out of sync with its assigned component.Solution
Allow for the ability to sync the gizmo to its parent for usage when you want to be able to move the parent component and the attached gizmo at the same time.
Verification
Gizmo behaves normally. We currently do not have any callers that need this functionality. But we will for MAM. Since that pr stack is already going to be quite large I decided to move this into its own chunk.
Before merging, ensure the following criteria are met: