Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.2f1
2019.2.0a1
2019.3.0a1
Issue ID
1154942
Regression
No
Anchor and ConnectedAnchor Gizmos are shown in incorrect position when "Swap Bodies" in "Configurable Joint" is active
How to reproduce:
1. Open attached project "PhysicsTestProject.zip" and scene "SampleScene"
2. Enter Play mode
3. In Scene view, observe anchor gizmos
Expected result: the gizmos are drawn in the middle of "HAND" object
Actual result: the gizmos do not take into account "Swap Bodies" value in "Configurable Joint", therefore, are always drawn in the same position
Reproducible with: 2017.4.27f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2021.1):
The swapBodies feature is behaving as designed. The swap occurs in the physics internals between two PhysX actors and axes of the rigidbodies in the joint. The calculation order of the rigidbodies influences the physics when swapBodies is enabled or disabled. The anchor Gizmos do not change in this swap. There is no visual change in the scene view when this field is toggled.
The documentation for 2021.1.0a1 has been modified to better explain this.
Resolution Note (fix version 2020.1):
The swapBodies feature is behaving as designed. The documentation will be modified to better explain this
Resolution Note (fix version 2019.4):
The swapBodies feature is behaving as designed. The documentation will be modified to better explain this