Profiler is showing VSync even when it is disabled in the settings

Heyy, I saw the profiler to analyze the scene and I found that the VSync activities are consuming a lot of resources, then I checked my quality settings and saw it is Disabled. How do I fix this?

Here's a image of my settings:

Profiler:

 

That's already turned off

 

Hii, no I didnt had any script changing VSync. It was maybe a bug. The profiler was showing VSync since 2 days, now, on third day it automatically erased from profiler. Should I report a bug?

 

Think I ran into this today on 2020.3.11f1.

Was working on my server project that does no rendering, and when in Editor was noticing v-sync in profile. It was pushing to 60 FPS steady which led me to think it was the Application.targetFrameRate = 60 setting I had configured in code on Awake() of the main application. I had vSyncCount set to 0 in code, all of my profiles have 0 v-sync counts, and the game view had v-sync off, but it was still showing. I assumed based off this that targetFrameRate is set to override the sync count and gets labeled under v-sync in profiler (not sure if that is intended or if its still technically v-sync).

It is important to note that if you set targetFrameRate at all, simply commenting the line will not remove this v-sync from showing in the profile as it looks like targetFrameRate is saved between compiles. You either have to explicitly set targetFrameRate to 0 or remove the targetFrameRate, recompile, and completely restart the editor to see the change in v-sync in the profiler. This could lead to some confusion if anyone is trying to track down whats causing the v-sync to show in the profiler beyond obvious settings.

@tanmaykulkarni were you using Application.targetFrameRate anywhere in code?

 

Heyy, that issue is fixed now. It was a simple bug. I just restarted my system several time and the vsync section had disappeared.
Thanks for replying!