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 potentially adding a duplicate component when migrating the grabbable component #28

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Exairnous
Copy link
Contributor

Depends on: #27

Prevents an extra Networked Transform component from being added to the host during the migration of the grabbable component if a Networked Transform component is somehow already present on the host.

This shouldn't generally be needed, but a duplicate Networked Transform component was added during the migration of an old blend file and adding a guard to prevent duplicates doesn't hurt.

Scene grabbables support was reverted (Hubs-Foundation/hubs#6515) in the Hubs client due to bugs and is now only present for the Hubs Client's addons branch and its behavior graphs add-on.  This commit restores the scene grabbables and physics support (along with fixes/improvements that were added to it in the main Blender add-on) to the behavior graphs Blender add-on to allow the functionality to be used with the Hubs Client's addons branch and its behavior graphs add-on.  A corresponding commit to the main Blender add-on removes support for scene grabbables/physics in the main Blender add-on so it maintains compatibility with the current Hubs Client.
…able component

Prevents an extra Networked Transform component from being added to the host during the migration of the grabbable component if a Networked Transform component is somehow already present on the host.

This shouldn't generally be needed, but a duplicate Networked Transform component was added during the migration of an old blend file and adding a guard to prevent duplicates doesn't hurt.
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