Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0a9
2019.3.1f1
2020.1
Issue ID
1220812
Regression
Yes
Crash in physx::Dy::SolverCoreGeneralPF::solveVParallelAndWriteBack on collisions when Directional Friction Type is used
How to reproduce:
1. Open tester-attached project (Physx_Crash.zip)
2. Open the 'CrashScene' and enter Play Mode
3. Select the 'RampsAndPaddleRingStandPrefab' GameObject
4. In the Inspector window check the 'Triggered' checkbox on the Paddle Ring Emitter script
5. Follow the particles being emitted from the ramp
Expected result: no crash occurs after a few of collisions
Actual result: the Editor crashes when the particles reach the wall on the other side of the arena
Reproducible with: 2019.3.0a9, 2019.3.3f1, 2020.1.0a24
Not reproducible with: 2018.4.17f1, 2019.3.0a8
Could not test with: 2017.4.37f1(project crashes upon launch)
Notes:
One-Directional or Two-Directional Friction Type must be selected in Physics settings in order to reproduce the crash
-
inkipinki
Feb 10, 2022 13:02
Running into the same issue on Unity 2021.2.8f1.
Patch friction "solves the issue".
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
A rather unique condition that is hopefully gone in the upcoming PhysX 5 release.