Search Issue Tracker

In Progress

Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X

Fix In Review for 6000.3.0a3

Votes

0

Found in

2021.3.40f1

2022.3.35f1

6000.0.8f1

6000.1.0a7

6000.2.0a1

6000.3.0a1

7000.0.0a1

Issue ID

UUM-74665

Regression

Yes

Switching the Profiler to Edit Mode while profiling Playmode makes the Editor ignore a modified targetFrameRate

-

Reproduction steps:
1. Open the attached “ReproProj” project
2. Open the “Assets/Scenes/SampleScene” scene
3. Enter the Play mode
4. Turn on the Profiler via Window -> Analysis -> Profiler
5. Set the Profiler to Play mode and record for a few seconds, then pause profiling (but stay in playmode)
6. Select the penultimate frame and observe the Timeline
7. Set the Profiler to Edit mode and record for a few seconds, then stop
8. Select the penultimate frame and observe the Timeline

Expected Result: The Edit mode frame should have a frame take about 90-100 ms the same as the Play mode
Actual Result: The Edit mode frame takes only about 20-30 ms

Reproducible with: 2021.2.0b13, 2021.2.0b17, 2021.2.19f1. 2021.3.40f1, 2022.3.35f1, 6000.0.8f1
Application.targetFrameRate is completely ignored (independent of Profiler target) on: 2021.2.0a2, through to 2021.2.0b12 
Not reproducible on: 2020.2.7f1, 2021.1.28f1, 2021.2.0a1.

Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested

Additional Notes:
- The time spend waiting for the Target Frame Rate is hidden within the Editor loop, which is not how it should be.
- It would be nice to know what the targetFrameRate and vSync settings for a frame where to more easily spot mistakes like the one in this script, which set the targetFrameRate to 10.
- Application.targetFrameRate remains set to 10 while profiling Edit Mode, the Editor just ignores it.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.