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
- On Script import/reimport MonoImporter does not generate consistent results due to updating Custom packages
- [Entities Graphics] Size of the Content Update generated folder increases when changes are made to the Scene
- In Play Mode, an extra Sync Call is made every frame when a GameObject has a Rigidbody 2D component
- Crash on block_remove when a scene is opened in a specific project
- The GameObject with a Hinge Joint Component does not return to the initial position when the Use Motor property is toggled off
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a9