Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
2022.3.73f1
6000.0.68f1
6000.3.10f1
6000.4.0b10
6000.5.0a7
6000.6.0a1
Issue ID
UUM-135903
Regression
No
Rigidbody.angularVelocity.magnitude differs between versions when using "Rigidbody.AddTorque" with "ForceMode.VelocityChange"
Reproduction steps:
1. Open the attached "IN-134949_AddTorque.zip" project
2. Open the "Assets/Scene.unity" scene
3. Enter Play mode
4. Press Space
5. Open the Console window
6. Scroll to the top
7. Find the log entry "AddTorque VelocityChange:" and look at the second subsequent "Torque:" log entry
Actual result: The second "Torque:" value is "1.45 rad/s" (or "2.17 rad/s" in some cases)
Expected result: The second "Torque:" value is "2.86 rad/s"
Reproducible with: 2022.2.0a11, 2023.1.0a14, 2022.3.73f1
Not reproducible with: 6000.0.69f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a7
Could not test with: 2022.2.0a10 (CS246 error, no definition of “SimulationMode”)
Fixed in: 2023.1.0a15
Reproduced on: Windows 11
Not reproducible on: No other environments tested
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
Add comment