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

PhysicalBoneSimulator3D child being added to Skeleton3D by Engine always #95238

Closed
samsface opened this issue Aug 7, 2024 · 1 comment · Fixed by #95239
Closed

PhysicalBoneSimulator3D child being added to Skeleton3D by Engine always #95238

samsface opened this issue Aug 7, 2024 · 1 comment · Fixed by #95239
Milestone

Comments

@samsface
Copy link
Contributor

samsface commented Aug 7, 2024

Tested versions

4.3-rc2: bug happens
4.3-dev-5: does not

System information

Ubuntu 22.04.2 LTS with Godoto 4.3-rc2

Issue description

When you instance a scene with a Skeleton3D, the engine automatically adds a PhysicalBoneSimulator3D as a child of the Skeleton3D.

This caused issues in my project because my code was iterating over the Skeleton3D's children, expecting their types to match those shown in the editor scene tree.

image

Steps to reproduce

  1. Add a Skeleton3D to a scene in the editor.
  2. Add MeshInstance as a child to the Skeleton3D in the editor.
  3. Run the scene

Expected:

  • The remote scene tree should show a Skeleton3D with just a MeshInstance as the only child.

Actual:

  • The remote scene tree shows there has been a PhysicalBoneSimulator3D added.

Minimal reproduction project (MRP)

bug-repo.zip

@AThousandShips
Copy link
Member

This should have been made internal as it was listed as internal in the documentation, will write a fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants