Search Issue Tracker

Not Reproducible

Votes

0

Found in

5.5.0f3

Issue ID

876346

Regression

No

[Android] WaitForTargetFPS doesn't show up in profiler when multithreaded rendering is active

Profiling

-

How to reproduce:
1. Open the attached project "FPSTestProject.zip"
2. Disable multithreaded rendering in Android Player Settings
3. Build and run test scene on Android device (make sure that "autoconnect profiler" is enabled)
4. Notice that displayed frame rate on the screen is around 30 fps and profiler shows WaitForTargetFPS
5. Repeat steps 2-3 with enabled multithreaded rendering

Result: Displayed frame rate on the screen is around 30 fps, but WaitForTargetFPS doesn't show up in the profiler
Expected behavior: profiler shows WaitForTargetFPS

Note: User sets Application.targetFrameRate = 30 (V Sync Count in Quality settings is disabled)

Reproducible: 5.3.7p4, 5.4.4p2, 5.5.1p4, 5.6.0b8

Not reproducible: 2017.3.1f1

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.