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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2023.3.0b7):
Fixed in: 2023.3.0b7