Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.29f1c1
2021.3
2022.1
2022.2
Issue ID
1419785
Regression
No
Physics2D.Simulate(0) does not trigger OnTriggerEnter2D and OnTriggerExit2D when they were triggered once before
Reproduction steps:
1. Open the attached project "PhysicsSimulateBug.zip"
2. Open the Console Window
3. Enter Play Mode
4. Observe the Logs in the Console Window
Expected result: "Enter Trigger" and "Exit Trigger" should be logged in the Console after every enter and exit from the trigger when the Physics2D.Simulate(0) is called
Actual result: "Enter Trigger" and "Exit Trigger" are logged in the Console only once when the Physics2D.Simulate(0) is called
Reproducible with: 2019.4.39f1, 2020.3.34f1, 2021.3.3f1, 2022.1.1f1, 2022.2.0a8
Not reproducible with: 2022.2.0a9, 2022.2.0a14
Note: if the Physics2D.Simulate(Mathf.Epsilon) method is called, the OnTriggerEnter2D and OnTriggerExit2D Events are called every time, but using the Physics2D.Simulate(0) method these Events are called only one time each in total
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 2022.2):
Fixed in: 2022.2.0a9