You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: NetworkTransform cannot set non-synchronized axis on non-authority instances (#3471)
Issue verified when investigating
[ForumSupport-939437](https://discussions.unity.com/t/client-network-transform-syncing-unchecked-axis/939437/1).
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](https://jira.unity3d.com/browse/MTTB-1334)
## Changelog
- Fixed: Issue where non-authority `NetworkTransform` instances would
not allow non-synchronized axis values to be updated locally.
## Testing and Documentation
- Includes the `NetworkTransformNonAuthorityTests` integration test.
- No documentation changes or additions were necessary.
<!-- Uncomment and mark items off with a * if this PR deprecates any
API:
### Deprecated API
- [ ] An `[Obsolete]` attribute was added along with a `(RemovedAfter
yyyy-mm-dd)` entry.
- [ ] An [api updater] was added.
- [ ] Deprecation of the API is explained in the CHANGELOG.
- [ ] The users can understand why this API was removed and what they
should use instead.
-->
## Backport
This fix is specific to NGO v2.x.
Copy file name to clipboardExpand all lines: com.unity.netcode.gameobjects/CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ Additional documentation and release notes are available at [Multiplayer Documen
14
14
15
15
### Fixed
16
16
17
+
- Fixed issue where non-authority `NetworkTransform` instances would not allow non-synchronized axis values to be updated locally. (#3471)
17
18
- Fixed issue where invoking `NetworkObject.NetworkShow` and `NetworkObject.ChangeOwnership` consecutively within the same call stack location could result in an unnecessary change in ownership error message generated on the target client side. (#3468)
18
19
- Fixed issue where `NetworkVariable`s on a `NetworkBehaviour` could fail to synchronize changes if one has `NetworkVariableUpdateTraits` set and is dirty but is not ready to send. (#3466)
19
20
- Fixed inconsistencies in the `OnSceneEvent` callback. (#3458)
0 commit comments