Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.2.17f1
2019.3
2020.1
2020.2
Issue ID
1225305
Regression
No
AddTorque and AddRelativeTorque behave differently in opposite Y axis when object is moved forward with AddForce
How to reproduce:
1. Open the user's project
2. Enter Play Mode
3. Click on the Game View with your mouse and drag it to the left and then to the right
Expected: Torque is applied equally to both positive and negative direction on Y axis
Actual: Torque applies lower value in negative direction than in positive direction on Y axis
Reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.3.5f1, 2020.1.0b1, 2020.2.0a2
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
Behaviour caused by non-optimal friction settings rather than torque