Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2020.3
2020.3.23f1
2021.2
2022.1
Issue ID
1383137
Regression
No
GameObject with the Articulation body component result in unrealistic behavior when the GameObject is scaled
How to reproduce:
1. Open the attached project "ARticulationBodiesBug.zip"
2. Open Assets > Scenes > test.unity
3. Enter Play Mode
4. Observe "Cube (1)" GameObject
Expected result: Angular Velocity at Y and Z axes is 5 radians per second
Actual result: Angular Velocity at Y and Z axes keep speeding up until reaches the maximum
Reproducible with: 2020.3.26f1, 2021.2.8f1, 2022.1.0b3
Couldn't test with: 2019.4.34f1 (no ArticulationBody component)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
- “ReferenceError: Pointer_stringify is not defined” error is thrown when downloading a file
- GameObjects are not rendered when using a fragment shader with RWStructuredBuffer in URP
Add comment