Search Issue Tracker
Third Party Issue
Votes
0
Found in
2018.4
2019.4
2020.1
2020.1.17f1
2020.2
2021.1
Issue ID
1298803
Regression
No
Destroy() with a timer does not work on a specific Project
How to reproduce:
1. Open the "TestDestroyCube" scene in the attached stripped "DemoBacketPhone.zip" Project
2. Note that the red cube represents the issue and the green cube shows that other destroy method override works
3. Enter PlayMode
4. Wait 3 seconds and inspect the Cubes
Expected Behavior: Both cubes get destroyed (Green cube immediately, red cube after 3 seconds)
Actual Behavior: The green cube is destroyed immediately and the red cube is never destroyed
Reproducible with: 2018.4.30f1, 2019.4.17f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a10
Note:
- Only the attached project reproduces the problem, other projects behave as expected
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note:
Attached project has a timescale at 0, which has the effect of pausing the game. So the delayed destroy never completes. By resetting time scale to 1 solves the issue.