Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.4f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131885
Regression
No
Spring Joint 2D "Distance" value adjusts "Connected Anchor" Y value instead when dragging via Inspector
Steps to reproduce:
- Open the attached "2DSpringJoint.zip" project
- Open the "SampleScene"
- Enter Play mode
- From the Hierarchy, select the "Square 2" GameObject
- In the Inspector, find the "Spring Joint 2D" Component
- Make sure "Auto Configure Distance" property is enabled
- Hover over the "Distance" property to get the value change cursor
- Click and drag the cursor to change the value
- Observe the component
Actual results: "Distance" value does not change, but the "Connected Anchor" Y value changes instead
Expected results: The "Distance" property should be greyed out due to not being editable, and the "Connected Anchor" Y value should not change
Reproducible with versions: 6000.0.65f1, 6000.3.4f1, 6000.4.0b3, 6000.5.0a4
Tested on (OS): Windows 11
Notes:
- Sprites are set up as such: Square1 with Slider Joint 2D and Square 2 with Spring Joint 2D
- Also reproduces with "Auto Configure Distance" disabled. In such case both properties are changed when changing value
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:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.