Search Issue Tracker
Fixed
Fixed in 2021.3.17f1, 2022.2.3f1, 2023.1.0a24
Votes
0
Found in
2020.3.41f1
2021.3.12f1
2022.1.21f1
2022.2.0b13
2023.1.0a16
Issue ID
UUM-19333
Regression
No
Angular Offset for Relative Joint 2D displays degrees despite utilizing radians in the Inspector after altering Angular Offset in a script
Reproduction steps:
- Open the user attached project
- Open the “SampleScene” scene
- Enter the Play mode
- In the top left corner of the Game view press on “Set to 180” button
- Note the Joint Angular Offset value in the top left corner of the Game view
- Select “Square” in the Hierarchy
- In the Inspector change value of Angular Offset to 181 in the Relative Joint 2D component
Expected result: Joint Angular Offset value is 181 in the top left corner of the Game view
Actual result: Joint Angular Offset value is 10370.54 in the top left corner of the Game view
Reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.21f1, 2022.2.0b13, 2023.1.0a16
Reproduced on: Windows 10
Note: 10370.54 degrees is 181 radians.
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
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Resolution Note (fix version 2023.1.0a24):
Fix for this issue will be available on Unity 2023.1.0a25 and above
Resolution Note (fix version 2022.2.3f1):
Fix for this issue will be available on Unity 2022.2.3f1 and above
Resolution Note (fix version 2021.3.17f1):
Fix for this issue is available on Unity 2021.3.17f1 and above