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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
A rather unique condition that is hopefully gone in the upcoming PhysX 5 release.