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
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-83048