Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.35f1
2022.3.19f1
2023.2.9f1
2023.3.0b6
Issue ID
UUM-63697
Regression
No
DistanceJoint2D distance value does not update GameObjects positions when the value is changed through the script
Reproduction steps:
1. Open the attached “Distance2Djoint.zip” project
2. Open the “SampleScene”
3. Select “A” GameObject
4. In the Inspector find the “Distance Joint 2D” Component and “Distance” property
5. Enter the Play mode
6. Press Right and Left arrow buttons on the keyboard in the Game view
7. Observe the “Distance” property in the Inspector and GameObjects in the Game view
Expected result: Distance value in the Inspector changes and GameObjects are moving
Actual result: Distance value in the Inspector changes, but GameObjects are not moving
Reproducible with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note:
- Changing the value through the Inspector provides the expected result
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Setting this issue back to closed status as it has been addressed previously