Search Issue Tracker
By Design
By Design in 6000.0.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
Comments (1)
-
jared-cone
Jan 27, 2026 23:21
Is there anything in the data to let us know if we need to flip the normal?
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Currently the way we display normals is always from the PoV of the "body B" from the shape collision pair. This means that either body in that pair can be body B as order is not guaranteed.
We will be filing a separate task to improve the UX of normals with respect to this detail.
Resolution Note (6000.0.X):
Currently the way we display normals is always from the PoV of the "body B" from the shape collision pair. This means that either body in that pair can be body B as order is not guaranteed.
We will be filing a separate task to improve the UX of normals with respect to this detail.