fix: In-Scene Placed Object Parenting and Serialization Order (back port) #3388
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 the back port of #3387 that resolves some issues with in-scene placed NetworkObjects in parent-child hierarchy and the synchronization of late joining clients when the hierarchy has changed from that of its default hierarchy defined within the scene.
MTT-11883
Changelog
NetworkObjects
could fail to synchronize its transform properly (especially without aNetworkTransform
) if their parenting changes from the default when the scene is loaded and if the same scene remains loaded between network sessions while the parenting is completely different from the original hierarchy.NetworkObject
s to be based on their parent-child hierarchy.Testing and Documentation