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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0b7):
Fixed in: 2023.3.0b7