Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: provide alternate tick registration method #3022

Draft
wants to merge 3 commits into
base: develop-2.0.0
Choose a base branch
from

Conversation

NoelStephensUnity
Copy link
Collaborator

This PR provides an alternate way to register a NetworkRigidbodyBase instance (child) with a root NetworkRigidbodyBase instance (parent) for tick synchronizing a joint attached child's state updates with the parent's/root's state updates.

Changelog

  • Added: 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.
  • Added: NetworkRigidbodyBase.RemoveFromTickSynchronizedUpdates to remove any added NetworkRigidbodyBase instances from tick synchronized updates.

Testing and Documentation

  • No tests have been added.
  • Documentation changes are needed (public documentation on usage).

For customized solutions, I am adding an additional method that allows users to add a NetworkRigidbodyBase to the tick synchronized udpates.
Adjusting the NetworkTransform side of things
@NoelStephensUnity NoelStephensUnity changed the title Fix/provide alternate tick registration method fix: provide alternate tick registration method Aug 21, 2024
Removing whitespaces
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant