fix: client-server owner authoritative nested NetworkTransform invalid synchronization #3099
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.
This is a special case for client-server where a server is spawning an owner authoritative
NetworkObject
but has yet to serialize anything. When the server detects that:NetworkTransform
.NetworkTransform
is owner authoritative.NetworkObject
is not owned by the server.SynchronizeState.IsSynchronizing
is set to false.Then the server would skip the final initialization step which resulted in the loss of the initial
SynchronizeState
settings.This PR checks for the above conditions during the initial spawning of a
NetworkObject
and then:SynchronizingState
is updated to the instantiated prefab's default flags/settings.SynchronizingState.IsSynchronizing
flag so theNetworkTransform
runs through the final initialization steps.MTTB-483
fix: #3082
Changelog
NetworkTransform
components clearing their initial prefab settings when in owner authoritative mode on the server side while using a client-server network topology which resulted in improper synchronization of the nestedNetworkTransform
components.Testing and Documentation