Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0p4
Issue ID
945434
Regression
No
Joint is attached but no longer functions when connected body is disabled and reenabled
To reproduce:
1. Open attached Unity project "DisablingConnectedObjects.zip"
2. Open "TestScene" scene
3. Go into Play mode
4. Disable AttachedBody GameObject
5. Reenable AttachedBody
Expected result: Upon disabling the AttachedBody GameObject, Fixed Joint component of the Anchor GameObject should change the Connected Body to None or missing, as AttachedBody is no longer connected after being reenabled.
Actual result: Fixed Joint still shows AttachedBody as its Connected Body, but that is no longer the case after it is reenabled
Reproduced on: 5.6.3f1, 2017.1.0p5, 2017.2.0b8, 2017.3.0a6
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
This happens because Rigidbody would create a new physics engine actor when you disable and enable it back. This new actor is never communicated to the joint component for perf reasons apparently. This won't be fixed until we redo our Rigidbody infrastructure to retain the physics engine actors when deactivating.