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
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
Resolution Note:
Behaviour caused by non-optimal friction settings rather than torque