Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2020.1.0b8
2020.2
2020.2.0f1
2021.1
Issue ID
1300309
Regression
Yes
Crash on physx::Scb::Body::addSpatialAcceleration when removing child from ArticulationBody with force in Play Mode
Reproduction steps:
1. In the user's attached project open "SampleScene"
2. Enter Play Mode
3. Enable Add Some Force component on the "Cube" game object
4. Drag out the child object of “Cube” (“Sphere”)
Expected result: Editor does not crash
Actual result: Editor crashes
Reproducible with: 2020.1.0b8, 2020.1.17f1, 2020.2.1f1, 2021.1.0a10
Not reproducible with: 2020.1.0a23, 2020.1.0b7, 2021.1.0b1
Could not test with: 2018.4.30f1, 2019.4.17f1, 2020.1.0a14 (no articulation body component)
2020.1.0a15, 2020.1.0a22 (no articulation body force)
Comments (1)
-
PallArinbj
Feb 08, 2021 16:03
Any plans to fix this in 2020?
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2021.1):
Does no longer reproduce with 2021.1.0b1