Search Issue Tracker
Fixed in 2022.2.X
Duplicate in 2021.3.X
Votes
0
Found in
2021.2.0a2
2021.2.5f1
2022.1
2022.2
Issue ID
1391440
Regression
Yes
Coroutine with WaitForEndOfFrame() finishes too soon when the framerate is capped using Application.targetFrameRate
How to reproduce:
1. Open the attached project "timeRepro"
2. Open the scene "SampleScene" and Enter Play mode (Assets/Scenes/SampleScene.unity)
3. Inspect the Console window (Window > General > Console)
Expected result: The message ">>>>> End" is logged 10 seconds after ">>>>> Start"
Actual result: The message ">>>>> End" is logged 5 seconds after ">>>>> Start"
Reproducible with: 2021.2.0a2, 2021.2.8f1, 2022.1.0b3, 2022.2.0a1
Not reproducible with: 2019.4.34f1, 2020.3.26f1, 2021.2.0a1
Note: Starting from 2021.2.0b13 and up, the message is logged after 1 second
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a9