Search Issue Tracker
Fixed
Fixed in 2021.3.25f1, 2022.2.18f1, 2023.1.0b14, 2023.2.0a12
Votes
0
Found in
2021.3.19f1
2022.2.7f1
2023.1.0b5
2023.2.0a3
Issue ID
UUM-27540
Regression
No
Crash on physx::Dy::SolverCoreGeneralPF::solveVParallelAndWriteBack when entering Play Mode
Reproduction steps:
1. Open the attached “repro-project“
2. Open "VR_Van" Scene
3. Enter Play Mode
4. Observe the crash
Reproducible with: 2021.3.19f1, 2022.2.7f1, 2023.1.0b5, 2023.2.0a3
Could not test with: 2020.3.45f1 - due to errors when downgrading the project
Reproduced on: Windows 10 Pro
First few lines of the stack trace:
0x00007FF755B1F419 (Unity) physx::Dy::SolverCoreGeneralPF::solveVParallelAndWriteBack
0x00007FF755B1E5FE (Unity) physx::Dy::DynamicsContext::solveParallel
0x00007FF755B1E590 (Unity) physx::Dy::solveParallel
0x00007FF755A330B2 (Unity) physx::Cm::BaseTask::run
0x00007FF7539B0652 (Unity) PhysxJobFunc
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
Add comment