Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a2
2021.2.0b1
2022.1
Issue ID
1355826
Regression
Yes
Play Mode Profiler does not wait for Application.targetFrameRate
Reproduction steps:
1. Open the attached "ProfilerNotShowingWaitForTargetFPS.zip" project
2. Enter Play Mode
3. Open the Statistics panel (Game window > Stats)
4. Open the Profiler (Window > Analysis > Profiler)
5. Select Play Mode to be profiled
6. Compare frame rates in the Statistics panel and the Profiler
Expected result: Frame rates in the Statistics and the Profiler are relatively the same
Actual result: Profiler does not wait for Application.targetFrameRate ("WaitForTargetFPS" process missing)
Reproducible with: 2021.2.0a2, 2021.2.0b7, 2022.1.0a5
Not reproducible with: 2018.4.36f1, 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0a1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a8
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b13