Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
949724
Regression
No
Collision.impulse returns very low values during high-velocity collisions
Steps to reproduce:
1. Download and open the attached project
2. Build for 32-bit Standalone
3. Run the build
4. Wait for collision speed to increase
Expected result: the impulse value is always reflective of the collision speed
Actual result: the impulse value is returned incorrectly at high velocity collisions
Reproduced on 5.5.4p2, 5.6.2p4, 2017.1.1p3, 2017.2.0f1, 2017.3.0a6
Notes:
-does not happen on a 64-bit build
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Add comment