Search Issue Tracker
Fixed
Fixed in 2022.3.7f1, 2023.1.7f1, 2023.2.0b3, 2023.3.0a1
Votes
0
Found in
2022.3.5f1
2023.1.4f1
2023.2.0a23
Issue ID
UUM-42690
Regression
No
Angular Offset for RelativeJoint2D is displayed in radians when enabling Auto Configuration Offset
Reproduction steps:
1. Open project “My project (11).zip”
2. Open “SampleScene”
3. Select “Triangle” GameObject through the Hierarchy
4. Under “Relative Joint 2D” enable “Auto Configuration Offset” through the Inspector
5. Observe the “Angular Offset” property
Expected result: the value displayed is 90 - the same as the “Triangle” GameObject Rotation on the Z axis
Actual result: the value displayed is 1.570796
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Reproducible on: macOS Ventura 13.2.1 (Intel), Windows 10 (by the reporter)
Notes:
- Although the value displayed is in radians, Angular Offset itself uses degrees (observe through Scene view)
- 1.570796 radians is 90 degrees
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Resolution Note (fix version 2023.3.0a1):
Fix for this issue will be available on Unity 2023.3.0a1 and above
Resolution Note (fix version 2023.2.0b3):
Fix for this issue is available on Unity 2023.2.0b3 and above
Resolution Note (fix version 2023.1.7f1):
Fix for this issue will be available on Unity 2023.1.7f1 and above
Resolution Note (fix version 2022.3.7f1):
Fix for this issue will be available on Unity 2022.3.7f1 and above