Search Issue Tracker
By Design
Votes
0
Found in
2020.1
2020.2
2021.1
2021.1.0a10
Issue ID
1299574
Regression
No
[Physics] Articulation Body values are reset to initial values when the GameObject/Component was disabled and reenabled
How to reproduce:
1. Open the user's attached "Physics_Bugs" project
2. Open the "AB_ValuesNotRestoredAfterReenabling" Scene
3. In the Hierarchy select the "Sphere" GameObject
4. Enter the Play Mode
5. Disable and after a while reenable the Articulation Body Component
Expected results: The velocity Y value (and all other values) should be cached and restored after the Component is reenabled
Actual results: All previous values are lost and upon enabling the Component, default values are set
Reproducible with: 2020.1.0a15, 2020.1.17f1, 2020.2.0f1, 2021.1.0a10
Could not test with: 2018.4.30f1, 2019.4.17f1, 2020.1.0a14 because the Articulation Body Component was not yet introduced
Notes:
- The issue is reproducible when either the Component or the GameObject itself is disabled and reenabled
- The expected results can be seen when disabling/reenabling a GameObject with Rigidbody
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
ArticulationBody doesn't keep a copy of the physics engine state as it can be rather expensive doing so, this is currently by design. A possible workaround is for the user code to save only the subset of required parameters manually.