Search Issue Tracker
Third Party Issue
Votes
0
Found in
2020.3.35f1
2021.3.5f1
2022.1.6f1
2022.2.0a17
2023.1.0a2
Issue ID
UUM-7396
Regression
No
GameObjects with "AddForceAtPosition" are not rotating to the force direction when Force has a positive angle
How to reproduce:
1. Open project "PhysicsForce.zip"
2. Enter Play Mode and press the Pause button near the Play button
3. In the Hierarchy window select "Cube (1)" GameObject
4. In the Inspector window change "Force Test" Component "Y Angle Rotate" to 30
5. In the Hierarchy window select "Cube (2)" GameObject
6. In the Inspector window change "Force Test" Component "Y Angle Rotate" to -30
7. Unpause the Game
8. Observe the result
Expected result: Both GameObjects are moving towards the force direction
Actual result: GameObject with positive angle (Cube (1)) is moving not towards the force direction
Reproducible with: 2019.4.37f1, 2020.3.31f1, 2021.2.17f1, 2022.1.0b13, 2022.2.0a8
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
This is a complex issue inside PhysX (even with the latest PhysX 5). Nvidia is aware and looking into it but for now here are a few workarounds:
- Do not use the Patch Friction type, it only picks 2 out of 4 contacts and the result is never going to be symmetrical.
- Use the Two-Directional Friction type. It works on all 4 of the produced contacts and has the best chance of producing a symmetrical result.
- Bump us the velocity (and potentially position) iteration count to increase the convergence of the friction constraints