Search Issue Tracker
Fixed
Fixed in 6000.0.64f1, 6000.2.15f1, 6000.3.0f1, 6000.4.0a6, 6000.5.0a2
Votes
0
Found in
6000.0.58f2
6000.2.6f2
6000.3.0b11
6000.4.0a2
6000.5.0a1
Issue ID
UUM-126746
Regression
No
Crash on physx::Scb::Body::setKinematicTarget when Moving Disabled Parent Kinematic Rigidbody
How to reproduce:
1. Open the attached project "IN-122707"
2. Open scene “PrototypeSceneTemplate“
3. Enter Play mode
4. Observe the Crash
Reproducible with: 6000.2.6f2
Reproducible on: Windows 11 Enterprise
Not reproducible on: No other environments tested
Reproducible on devices:
Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740 (reporter)
Note: CQA was not able to reproduce the issue
First few lines of the stack trace:
0x00007FFDC59169E0 (Unity) physx::Scb::Body::setKinematicTarget
0x00007FFDC5916D33 (Unity) physx::NpRigidDynamic::setKinematicTarget
0x00007FFDC3BE1CDF (Unity) PhysicsCommands::Physx::BodySetKinematicTarget
0x00007FFDC36CA5BC (Unity) Rigidbody::Move
0x00007FFDC2AB2B6D (Unity) Rigidbody_CUSTOM_Move
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment