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
- Matching Selectors list not updating correctly with element's pseudo-state updates
- [Android] Crash on vendor/lib64/egl/libGLES_mali.so when Graphics Jobs(Experimental) is disabled and the Player is running on the Google Pixel 6 with the March security patch installed
- Profiler does not profile after building the Project with Autoconnect Profiler Option enabled
- Editor slows down when selecting a script with the [HideInInspector] attribute on arrays with dynamic values
- [XR] Custom Pass not working as intended with Single Pass Instanced when XR is initialized after runtime start
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.