Search Issue Tracker
Fixed
Votes
0
Found in
6000.0.22f1
Issue ID
UUM-83528
Regression
Yes
Collision between GameObjects is not detected when using Collider.layerOverridePriority
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/CollisionTest.unity” Scene
3. Make sure that the Scene view tab is opened
4. Enter the Play Mode
5. Observe the Scene view
Expected result: The collision between CubeA and CubeB is detected and cubes repel each other
Actual result: Collision between CubeA and CubeB is not detected
Reproducible with: 2023.3.0a19, 6000.0.22f1
Not reproducible with: 2022.3.48f1, 2023.3.0a18
Couldn't test with: 2021.3.44f1 (Could not resolve compilation errors)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: Enabling the updateLayerOverridePriority checkbox in the Collision Test component attached to CubeB resolves 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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-83048