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
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Customize handled extensions" part in the External Tools settings tab is not aligned with other properties
- Editor Diagnostics foldouts do not open when clicked on the foldout title
- [UI Builder] Visual Elements are not placed at the mouse cursor position when Absolute Position Placement is enabled
- "Width" and "Height" text is misaligned with slider ends in Screen Match Mode Parameters section of Panel Settings Asset
- Editor does not quit when Editor is not in focus and any floating window is opened
Add comment