Search Issue Tracker

Won't Fix

Votes

0

Found in

2020.3

2020.3.28f1

2021.3

2022.1

2022.2

Issue ID

1423831

Regression

No

V-sync profiler markers return 0 when building the project with Development Build option disabled

Profiling

-

Reproduction steps:
1. Open the user's attached project
2. Go to File > Build Settings and enable the Development Build option
3. Press Build And Run
4. In the Player observe the debug information for markers in the top left corner
5. Disable the Development Build option
6. Repeat 3-4 steps

Expected result: Profiler markers related to v-sync return non-zero values in the Development and non-Development builds
Actual result: Profiler markers related to v-sync only return non-zero values in development builds

Reproducible with: 2020.3.34f1, 2021.3.2f1, 2022.1.0f1, 2022.2.0a12
Couldn't test with: 2019.4.38f1 (Couldn't resolve a console error)

Note: Only Gfx.WaitForPresentOnGfxThread returns a non-zero value in the non-Development build

  1. Resolution Note (2022.2.X):

    Both markers are not related to the vsync and can not be used to determine vsync time.
    The best alternative is https://docs.unity3d.com/2022.2/Documentation/ScriptReference/FrameTimingManager.html or native plugin api https://docs.unity3d.com/Manual/NativePluginInterface.html which allows to hook into specific render api

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.