fix: NetworkTransform cannot set non-synchronized axis on non-authority instances#3471
Merged
NoelStephensUnity merged 10 commits intodevelop-2.0.0from Jun 2, 2025
Conversation
…onized-axis-nonauthority
EmandM
approved these changes
Jun 2, 2025
Member
EmandM
left a comment
There was a problem hiding this comment.
Yay for getting the test working!
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
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.
Issue verified when investigating ForumSupport-939437.
This PR resolves the issue in v2.x where you cannot update non-synchronized axis values on non-authority instances without having them be reset by the next frame.
MTTB-1334
Changelog
NetworkTransforminstances would not allow non-synchronized axis values to be updated locally.Testing and Documentation
NetworkTransformNonAuthorityTestsintegration test.Backport
This fix is specific to NGO v2.x.