fix: provide alternate tick registration method #3022
Draft
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 PR provides an alternate way to register a
NetworkRigidbodyBase
instance (child) with a rootNetworkRigidbodyBase
instance (parent) for tick synchronizing a joint attached child's state updates with the parent's/root's state updates.Changelog
NetworkRigidbodyBase.AddToTickSynchronizedUpdates
for custom joint type solutions that just need to keep the attached objects synchronized with the root (parent) that the object(s) are attached to.NetworkRigidbodyBase.RemoveFromTickSynchronizedUpdates
to remove any addedNetworkRigidbodyBase
instances from tick synchronized updates.Testing and Documentation