Search Issue Tracker
By Design
Votes
1
Found in
4.3.0f4
Issue ID
585065
Regression
No
2D hinge joints teleport the object when entering play mode
To reproduce:
1. Open attached project
2. Open test scene
3. Enter play mode
Expected result: 2D hinge works just as 3D does
Actual result: 2D hinge teleports and get's messed up
Closed By Design:
The 2D hinge is configured incorrectly which is why it doesn't work.
The scale of the object is 1/1/1 therefore hinge anchor points are normalized to this however a Box of a size 0.4/4.15 is used and this has nothing to do with joints!
Therefore, the anchors need to be set on the Y axis correctly.
For the 2dchain hierarchy using the reference 1 as the root, 2 as the child, 3 as the next child and 4 as the final child I did the following:
2dchain1:
anchor = 0,2
connected anchor = 0,10 (global position of static position)
2dchain2:
anchor = 0,2
connected anchor = 0,-2
2dchain3:
anchor = 0,2
connected anchor = 0,-2
2dchain4:
anchor = 0,2
connected anchor = 0,-2
In other words, the anchor is the "top" of the chain and the connected anchor is the connected one, in this case you connect to the parent so "-2" is the Y position of the bottom of the chain.
The only oddity, which is soon to chain in a coming release, is the "2dchain1" which uses "0,10". When you don't specify a connected rigid-body then the static ground-body is used and this coordinate is a world-space body. This is okay until you wish to use this as a prefab. In the future, this will become a local-space value.
Also, in a coming release, joint anchors will be auto-calculated for some joints just like 3D.
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
Add comment