Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.0a6
Issue ID
754739
Regression
No
[MSE] GameObject duplication on moving joint-referenced GO to another scene
1. What happened
If you have a Physics joint referencing another GameObject in the same scene, and then move the GameObject to a separate scene and enter play mode, a duplicate game object is created in the first scene. This is not restored to the previous state after leaving play mode.
2. How we can reproduce it using the example you attached
- Load scenes '2' and e.g. 'Ground1' (if not loaded)
- Select 'DoorBlock' GO
- In its 'Hinge Joint'>'Connected body' select a rigid-body GO from the same scene (e.g. Sphere)
- Move 'Sphere' GO to another scene (e.g. Ground1)
- Enter Play mode
---> Notice that 'Sphere' GO is created in scene '2'
- Exit Play mode
---> 'Sphere' GO now exists in both scenes.
Expected: GO should not be duplicated. Likely the best thing would be to remove reference to GO the moment it is moved to another scene. Might be worthwhile informing user in console about the action (smth like 'Reference to ... was removed because ...').
Same behaviour in 5.3.0f4.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
This is a duplicate of issue #750117