Same situation ( saved flight )

Take a look at the GPU value. GPU is taxed max 64% , temp 72 Celsius max …..

Up to yesterday Vsync on / 30 hertz :

Out of a sudden yesterday Vsync on / 30 hertz :

Vsync off / 30 hertz :

Vsync off / 30 hertz / NVCP 30 fps locked

What happened to Vsync On ??

 

 

Edited December 17, 20214 yr by GSalden

@GSalden,

Did you happen to monitor Windows Task Manager as well?

I have done 2 flights today, each around 3 hours with no issues. I also run Vsync on in the sim set to 30 and it was rock solid the whole time 

Edited December 18, 20214 yr by Ray Proudfoot
Quoted post with embedded images removed.

12 minutes ago, RJC68 said:

Did you happen to monitor Windows Task Manager as well?

I have done 2 flights today, each around 3 hours with no issues. I also run Vsync on in the sim set to 30 and it was rock solid the whole time 

The framerate remains the same here. No issues with that. Not after 2.5h.

I mean the difference of the GPU load between Vsync On today ( GPU at 30 fps in yellow ) now or Vsync Off + locked at 30 ( GPU at 73 fps in green ).

Like the GPU counter acts different today.

 

2 minutes ago, GSalden said:

The framerate remains the same here. No issues with that. Not after 2.5h.

I mean the difference of the GPU load between Vsync On today ( GPU at 30 fps in yellow ) now or Vsync Off + locked at 30 ( GPU at 73 fps in green ).

Like the GPU counter acts different today.

 

Ah sorry my bad,

To be honest I didn't monitor the CPU/GPU loads

10 minutes ago, Rob_Ainscough said:

Did you check MSFS graphics setting?  I’ve had situations where MSFS just decides to change them from one session to the next.  GPU scheduling can cause unpredictable results also.

Cheers Rob

Graphic settings were the same.

And if I set graphics to Low End with Vsync enabled I see the same yellow GPU bar. Like Vsync is keeping the GPU counter at 32-33 ms.. ( 30 fps ).

With Vsync Off and no fps lock :

 

All looks like I would expect, i.e. normal. The "ms" number (milliseconds) is response time. Vsync causes lag. When you have Vsync off, response time is faster (a lower ms number), so less lag, regardless of whether FPS is free or locked/capped. As soon as you turn Vsync on, you get slower response times/more lag, so a higher rate in milliseconds. This is why some people would rather lock/cap their FPS with Vsync off, as performance is better that way (although you might see the odd screen tear still, but not so much as letting your GPU run wild with rendering frames).

Edited December 18, 20214 yr by March Hare

5 hours ago, March Hare said:

All looks like I would expect, i.e. normal. The "ms" number (milliseconds) is response time. Vsync causes lag. When you have Vsync off, response time is faster (a lower ms number), so less lag, regardless of whether FPS is free or locked/capped. As soon as you turn Vsync on, you get slower response times/more lag, so a higher rate in milliseconds. This is why some people would rather lock/cap their FPS with Vsync off, as performance is better that way (although you might see the odd screen tear still, but not so much as letting your GPU run wild with rendering frames).

But why did it look all green those months before yesterday and now the GPU is yellow with a way higher response time ?

5 hours ago, Rob_Ainscough said:

Tearing forbidden but Vsync off so your monitor is VRR?  If so, what range HZ range does your display device(devices) support?   Are you using surround?
 

Cheers, Rob

I use 2 Sony 43” 4K TV’s as one wide view in NVsurround. Frequency both set to 30 hertz.

But as nothing has changed regarding settings in MSFS (checked it) why has the response time of the GPU gone up dramatically with Vsync on… ?

Edited December 18, 20214 yr by GSalden

22 minutes ago, GSalden said:

I use 2 Sony 43” 4K TV’s as one wide view in NVsurround.

But as nothing has changed regarding settings in MSFS why has the response time of the GPU gone up dramatically with Vsync on… ?

With VSync on at 30 fps, the GPU sends frames in synchrony with the monitor, so GPU frametime is consistently 33.3 ms (1000 ms/30).

It must be 33.3 ms in such conditions, no idea why it was showing 12 ms at 30 fps yesterday... maybe the developer mode counter is bugged too.

13 minutes ago, MrFuzzy said:

With VSync on at 30 fps, the GPU sends frames in synchrony with the monitor, so GPU frametime is consistently 33.3 ms (1000 ms/30).

It must be 33.3 ms in such conditions, no idea why it was showing 12 ms at 30 fps yesterday... maybe the developer mode counter is bugged too.

You might be right. As even the main thread counter shows a lower ms with Vsync off than with Vsync On.

But it wonders me why up to Thursday it all looked different and from Friday on it has changed.

No NVidia update , no MSFS update …

it all runs smooth

 

1 hour ago, Rob_Ainscough said:

"Tearing forbidden" is Vsync On ... unless Asobo are referencing something else?  That's why I asked if your monitor was VRR (either Gsync or FreeSync) as Tearing forbidden would indicate some type of G-sync. 

Use of Vsync should only be relevant outside of your VRR range ... but I don't believe VRR is supported in NVSurround?

My guess is NVSurround is confusing MSFS metrics even if both your 43" monitors are set to the same refresh rate.  GPU Scheduling enabled might cause strange results like this also.

Cheers, Rob.

 

What NVsurround does inside MSFS is use 1/2 of the max fps setting with Vsync on. So 60 results in 30. That has always been the case.

Regarding HAGS : it is Off.

Since the beginning of the week I switched to the NV Studio driver. Before I used the 497.09 driver. However, the counter issues showed up 2 days after installing the Studio driver.

Edited December 18, 20214 yr by GSalden

29 minutes ago, Rob_Ainscough said:

For me that's always been the case regardless of NVSurround.  Sounds like it might be a driver issue ... have you tried the DDU route for clean driver install?

Cheers, Rob.

I always use DDU for uninstalling the driver. And I disconnect the IN when the pc reboots.

Then I install the new driver.

Btw : looking at multiple vids where the framerate counter shows they all show a yellow GPU counter with Vsync on.

Perhaps it now works as it should…

It looks like the yellow GPU counter is caused by the framerate is locked in Vsync, when it is able to run at a way higher rate.

But because of the screentearing I need to have Vsync on.

Edited December 18, 20214 yr by GSalden

On 12/18/2021 at 7:29 PM, GSalden said:

It looks like the yellow GPU counter is caused by the framerate is locked in Vsync, when it is able to run at a way higher rate.

Yes that is why it shows yellow, so there is nothing wrong.