Search Issue Tracker
Fixed
Fixed in 2023.3.0b7
Votes
1
Found in
2023.3.0b4
Issue ID
UUM-61078
Regression
Yes
Ignored collision reactivates when using “Physics.IgnoreCollision” between colliders
How to reproduce:
1. Open the user’s attached “Bug report.zip” project
2. Enter Play Mode
3. Press “2” on the keyboard
4. Press “3” on the keyboard
5. Observe the result
Expected result: “1“ GameObject falls through both “2” and “3” GameObjects
Actual result: “1” and “2” GameObjects collide with each other
Reproducible with: 2023.3.0a19, 2023.3.0b4
Not reproducible with: 2022.3.17f1, 2023.2.7f1, 2023.3.0a18
Could not test with: 2021.3.34f1 (Strange collisions when entering Play mode)
Reproduced on: macOS 13.6.3 (Intel)
Not reproducible on: No other environment tested
Note: reproducible in the Editor and Standalone Player (macOS)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2023.3.0b7):
Fixed in: 2023.3.0b7