fix: NetworkShow client synchronization duplicate players and NetworkShow with ChangeOwnership fixes [Backport] #3493
Conversation
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
NoelStephensUnity
changed the title
NoelStephensUnity
added a commit
that referenced
this pull request
Jun 10, 2025
The PR resolves the issue discovered when investigating the [Forum-1651980 issue](https://discussions.unity.com/t/netcode-for-gameobjects-2-4-0-released/1651980/2). The initial client synchronization pre-serialization preparation was not excluding any spawned `NetworkObject` instances that had a pending visibility update for the client being synchronized. This fix adds this check to that process. [MTTB-1372](https://jira.unity3d.com/browse/MTTB-1372) ## Changelog - Fixed: Issue where the initial client synchronization pre-serialization process was not excluding spawned `NetworkObjects` that already had pending visibility for the client being synchronized. ## Testing and Documentation - Includes the `PlayerSpawnObjectVisibilityTests`. - 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 requires a backport to v1.0 (#3493)
EmandM
approved these changes
Jun 10, 2025
NoelStephensUnity
deleted the
fix/networkshow-client-synchronization-duplicate-players-backport
branch
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.
The PR resolves the issue discovered when investigating the Forum-1651980 issue. The initial client synchronization pre-serialization preparation was not excluding any spawned
NetworkObjectinstances that had a pending visibility update for the client being synchronized. This fix adds this check to that process.MTTB-1372
This addresses the Forum-Support-1646996 issue where it was determined if you invoke
NetworkObject.NetworkShowand then immediately invokeNetworkObject.ChangeOwnership(or somewhere within the same callstack for that frame) the target client will get an error regarding an unnecessaryChangeOwnershipMessage.MTTB-1337
Changelog
NetworkObjectsthat already had pending visibility for the client being synchronized.NetworkObject.NetworkShowandNetworkObject.ChangeOwnershipconsecutively within the same call stack location could result in an unnecessary change in ownership error message generated on the target client side.Testing and Documentation
Backport
This is a back port of #3488.
This is a partial back port of #3468.