I am also trying to figure aout.

But if FG doubles the FPS wouldn't it make sense to set ingame VSYNC to half refreshrate (30 in this case) and let FG double it to 60?

Actually that was my first thought but at least on my end this doesnt work and the sim is uncontrollably stuttering.

3 hours ago, KL Oo said:

When you figure it out please let me know! I've been trying to get FG working properly on my triple monitor setup for months without any success. For me, if I have everything default in NV Control Panel and turn on FG in MSFS I get tearing and, interestingly I also get a higher main thread timing than if I did not have FG on. Its like FG is actually causing higher main thread time that lowers the natural FG, not withstanding that FG then boosts up the ultimate FPS. Of course the problem with this is also that FG only works on the main monitor/screen so the side monitor suffer a lower nautral frame rate.

 

I have found that using either V-SYNC enabled or putting a max cap on FPS in the NV Control Panel also causes significant main thread timing increase once in MSFS. I have no idea why, I would have that all of that processing is done on the GPU but regardless of what settings I have inside MSFS, with FG on and V_SYNC and/or MAX FRAMES PER SECOND set in NV Control panel I get major stutters and a huge increase in main thread time.

 

So, long story short I have not been able to make it work which is a shame because i"d like to be able to take advantage of FG. I think this issue is unique to those with multi monitors because if I disable the two secondary monitors i get get FG working fine.

 

The best solution I've found is setting adaptive (half) refresh rate in NV Control Panel and just leaving FG off. That way the frames are capped on all three monitors at 30 FPS and I get nice low GPU/main thread times...

 

 

You might want to try this setup (it works like a charm for me):

Monitor Refreshrate: 60Hz

NVCP: Max Frames 60FPS

NVCP VSYNC: On

MSFS Vsync: Off

MSFS FG: On

I get a constant 60FPS with this setup.

I finally have deactivated Freesync on my Monitor and get very smooth simming now,

15 minutes ago, ThomseN_inc said:

I am also trying to figure aout.

But if FG doubles the FPS wouldn't it make sense to set ingame VSYNC to half refreshrate (30 in this case) and let FG double it to 60?

Actually that was my first thought but at least on my end this doesnt work and the sim is uncontrollably stuttering.

Yeah you need to framerate cap and Vsync in the control panel, not in the game or it will introduce a lot of stuttering. Can't use tools like RTSS to cap framerate either.

1 hour ago, GSalden said:

Thank you for helping.
But why would the in-game FPS shoe 50% of that ? Or did you set it to 50% ?

Do you have a 40 series card ?

That would be my question too. Which instance is capping the Sim to 30FPS in this scenario?

19 minutes ago, ThomseN_inc said:

That would be my question too. Which instance is capping the Sim to 30FPS in this scenario?

That I would like to know too

10 minutes ago, GSalden said:

That I would like to know too

My guess would be NVCP Vsync has to be set to 1/2 refresh rate in this case.

37 minutes ago, ThomseN_inc said:

That would be my question too. Which instance is capping the Sim to 30FPS in this scenario?

Regular Vsync and I set my monitor to 60Hz, to confirm Vsync was working for Gsalden. That means the FG FPS was 60 (58, minus the frames Reflex takes away) but the debug FPS shows 30, i.e half of the FG FPS.

1 minute ago, Sethos said:

Regular Vsync and I set my monitor to 60Hz, to confirm Vsync was working for Gsalden. That means the FG FPS was 60 (58, minus the frames Reflex takes away) but the debug FPS shows 30, i.e half of the FG FPS.

Weird. Will check later when i'm back home to see if its the same on my end.^^

1 hour ago, Sethos said:

Regular Vsync and I set my monitor to 60Hz, to confirm Vsync was working for Gsalden. That means the FG FPS was 60 (58, minus the frames Reflex takes away) but the debug FPS shows 30, i.e half of the FG FPS.

If you use regular Vsync and not Adaptive (refreshrate x 50%) the in-game FPS counter should display 58-60 FPS.

So : 60 hertz +  VSync regular = 60 fps -> FR doubles this, so with an external FPS counter you should see 120. 

On my screenshots you can see the MSFS FPS counter and at the top the FPS made bij FG.

You should see almost 60 FPS inside MSFS and almost 120 FPS with an external framerate counter.  

Only with Adaptive 50% you should see : 30 -> 60….
 

 

10 minutes ago, GSalden said:

If you use regular Vsync and not Adaptive (refreshrate x 50%) the in-game FPS counter should display 58-60 FPS.

So : 60 hertz +  VSync regular = 60 fps -> FR doubles this, so with an external FPS counter you should see 120. 

On my screenshots you can see the MSFS FPS counter and at the top the FPS made bij FG.

You should see almost 60 FPS inside MSFS and almost 120 FPS with an external framerate counter.  

Only with Adaptive 50% you should see : 30 -> 60….
 

 

I'm with you. I guess there is someting mixed up here.^^

33 minutes ago, GSalden said:

If you use regular Vsync and not Adaptive (refreshrate x 50%) the in-game FPS counter should display 58-60 FPS.

So : 60 hertz +  VSync regular = 60 fps -> FR doubles this, so with an external FPS counter you should see 120. 

On my screenshots you can see the MSFS FPS counter and at the top the FPS made bij FG.

You should see almost 60 FPS inside MSFS and almost 120 FPS with an external framerate counter.  

Only with Adaptive 50% you should see : 30 -> 60….
 

 

No, it's because you still haven't understood that the in-game debug counter is wrong when using FG. My FPS WAS 60FPS, exactly as it was supposed to be, to prove that Vsync was working. The 30FPS was the "bugged" in-game counter displaying HALF of the actual FPS, essentially see it as the FPS without the added generated frames.

Edited June 18, 20232 yr by Sethos

36 minutes ago, Sethos said:

No, it's because you still haven't understood that the in-game debug counter is wrong when using FG. My FPS WAS 60FPS, exactly as it was supposed to be, to prove that Vsync was working. The 30FPS was the "bugged" in-game counter displaying HALF of the actual FPS, essentially see it as the FPS without the added generated frames.

The in-game counter shows the vsync FPS. In your case 60 hertz = 60 fps. With FG on you should see double that amount using a external FPS counter, So 120.

Your in-game franerate counter displays 50% of the FG FPS which should be 120 so you’ll end up with 60 not 30.

Only when using Vsync On and your pc is not capable to run at 60 FPS (heavy scenery) it steps down to 30 (or even 20) which then is doubled by FG to 60 (40).

Just had a Fs friend of mine and he was so kind to test it for me with his 4080z

He uses 60 hertz + Vsync 100% inside MSFS and he sees 60 FPS on the in-ganse framerate limiter. Inside Afterburner he saw 120 FPS.

Myself I do not use Afterburner.

 

 

 

Edited June 18, 20232 yr by GSalden

4 minutes ago, GSalden said:

The in-game counter shows the vsync FPS. In your case 60 hertz = 60 fps. With FG on you should see double that amount using a external FPS counter, So 120.

Your in-game franerate counter displays 50% of the FG FPS which should be 120 so you’ll end up with 60 not 30.

Only when using Vsync On and your pc is not capable to run at 60 FPS (heavy scenery) it steps down to 30 (or even 20) which then is doubled by FG to 60 (40).

Just had a Fs friend of mine and he was so kind to test it for me with his 4080z

He uses 60 hertz + Vsync 100% inside MSFS and he sees 60 FPS on the in-ganse framerate limiter. Inside Afterburner he saw 120 FPS.

Myself I do not use Afterburner.

 

 

 

No, you seem to think that frame generation somehow needs to go on top of whatever you're getting, in some hidden obscure manner, then you've misunderstood it. The framerate reported by RTSS, Steam Overlay or whatever you use that ISN'T the debug window FPS is the correct frame-generated FPS that already has the extra generated frames included. That's why the debug FPS shows exactly half that = that's without the generated frames.

12 minutes ago, Sethos said:

No, you seem to think that frame generation somehow needs to go on top of whatever you're getting, in some hidden obscure manner, then you've misunderstood it. The framerate reported by RTSS, Steam Overlay or whatever you use that ISN'T the debug window FPS is the correct frame-generated FPS that already has the extra generated frames included. That's why the debug FPS shows exactly half that = that's without the generated frames.

You now wrote exactly what I “saying” all the time  🤠

One last try : set your monitors frequency to 60 hertz + Vsync On. 
Without FG you should see 60 FPS in any external FPS counter. The in-game FPS counter should show 60 FPS when you use 100% of the frequency. If you use 50% you should see 30 FPS.  
If your pc cannot achieve 58-60 your FPS drop to 50% of the maximum Vsync value. Which was 60 and will show 30. I am sure you’ll agree on this …?

Beside this you have FG. That doubles the FPS. Every external framerate counter should show double the amount you saw before. In this case 120. 

As the in-game FPS counter only shows the FPS without the added AI FPS you still see 60.

See : https://shakeprint.com/2023/01/08/2296/

See this vid :

- - - 
To go back on-topic : I am still wondering why Vsync, being it enabled in NVCP or inside MSFS does not work anymore on both of my systems. It now is the same as Unlimited….

15 minutes ago, GSalden said:

You now wrote exactly what I “saying” all the time  🤠

One last try : set your monitors frequency to 60 hertz + Vsync On. 
Without FG you should see 60 FPS in any external FPS counter. The in-game FPS counter should show 60 FPS when you use 100% of the frequency. If you use 50% you should see 30 FPS.  
If your pc cannot achieve 58-60 your FPS drop to 50% of the maximum Vsync value. Which was 60 and will show 30. I am sure you’ll agree on this …?

Beside this you have FG. That doubles the FPS. Every external framerate counter should show double the amount you saw before. In this case 120. 

As the in-game FPS counter only shows the FPS without the added AI FPS you still see 60.

See : https://shakeprint.com/2023/01/08/2296/

See this vid :

- - - 
To go back on-topic : I am still wondering why Vsync, being it enabled in NVCP or inside MSFS does not work anymore on both of my systems. It now is the same as Unlimited….

I'm just repeating my own statements for the umpteenth time, which seems to be questioned.

That is how traditional vsync works, by waiting until vblank. However, has nothing to do with what I was showing nor what we were talking about, at all and I also have a Gsync monitor, thus vsync will automatically work more like an adaptive sync. So not sure about the relevance of that.

Yes, it doubles it as part of the process. Meaning if you vsync or frame rate cap to 60, then the frame generation is already part of that process, it isn't added on top of that to randomly go to 120. Now the frame generation is part of the 60fps. That is evident by the fact that the internal render FPS goes to half, your GPU usage increases, CPU usage decreases and input latency is noticeably increased when you're at such low framerates. So no, it wouldn't go to 120 if you cap at 60. You're essentially capping the game to 30 and letting the frame generation bring it up to 60.

Edited June 18, 20232 yr by Sethos