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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Add comment