Search Issue Tracker
Active
Under Consideration for 2022.3.X
Won't Fix in 2023.2.X
Votes
0
Found in
2022.3.17f1
2023.2.5f1
2023.3.0a19
6000.0.0b11
Issue ID
UUM-60128
Regression
No
Collision normals are inverted when the Motion Type is set to Kinematic
Reproduction steps:
1. Open the attached "PhysicsSamplesKinematicBug.zip" project
2. Open the "Events - Collisions" Scene ( Assets > 6. Events )
3. Enter the Play mode
4. In the Scene view, observe that the blue arrows on the spheres point upwards
5. Exit the Play mode
6. In the Hierarchy, toggle on the "Events - Collisions Subscene" and expand it
7. Select “Event Surface” GameObject and all the child elements of “Boundary” GameObject
8. In the Inspector, change the Physics Body Components Motion Type property from Static to Kinematic
9. Save the Subscene and toggle it off
10. Enter the Play mode
11. In the Scene view, observe that the blue arrows on spheres point downwards
Expected results: Collision normals remain the same
Actual result: Collision normals get inverted
Reproducible with: 2022.3.17f1, 2023.2.5f1, 2023.3.0a19
Couldn’t test with: 2021.3.34f1 (Invalid package dependencies), 2023.3.0b1 - 2023.3.0b2 (Invalid package dependencies)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Collisions still perform correctly
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.