Search Issue Tracker
Fixed in 5.0.X
Votes
2
Found in
4.3.0b6
Issue ID
572661
Regression
Yes
Trigger/Collision detection problem when TimeScale is set to zero
To reproduce:
1. Open the attached project
2. Run "Test1" scene
3. Notice, that nothing is logged in the console after the objects collide
4. Press "Respawn"
5. Wait until the new objects collide
6. Notice that OnTriggerEnter logs a message to the console though the TimeScale is still set to zero
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
Add comment