After 2 weeks of a lot of heat outside I started up both pc’s and both updated MSFS to 1.33.8.0 and the NVidia drives to 536.23.

With my 40 series cards I use Franerafe Generation enabled and it is working. My displays are running at 60 hertz.

What I want it that I have MSFS running at 30 fps which is doubled by FRG.

Using 50% Vsync in MSFS + FRG works fine.

However, to eliminate small jitters happening sometimes in heavy scenery I wanted to test with : Vsync Off in MSFS and use NVCP to do this.

But it seems like NVCP has no influence on the franerate. I even set max FPS to 30 (for testing) and used Adaptive. Displays running at 60 hertz.

 Any ideas ?

 

 

 

Edited June 18, 20232 yr by GSalden

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 need to use an external FPS display for correct reporting of FPS. The internal debug framerate display doesn't show the generated frames, so your FPS will be exactly half. Example I made a few days ago, someone was having stutter issues, you can see the internal display and the RTSS overlay reports two different things; https://streamable.com/teno2l

I set Vsync - FPS cap of 90 on a 144Hz display and it feels wonderful.

And to correctly limit FG, you simply use Vsync in NCP -- Never in the game itself and then an FPS limit in the NCP as well. That's my understanding at least. Some also say you need to cap a little under if you're running at the same FPS as the refresh of your screen. Though I will say, FG under 60FPS feels awful.

Edited June 18, 20232 yr by Sethos

It used to work simply by enabling FG in sim and setting 60hz with forced vsync in control panel but this was broken in release 1.30.9.0 in early 2023. Note this relied on gsync not being enabled. 

https://forums.flightsimulator.com/t/regression-dlss3-frame-generation-with-vsync-broken-in-1-30-9/568809

It is marked as 'bug logged' so definitely reproduceable by the devs but still broken at the current beta 1.33.8.0

 

 

 

Quote

 

 

If I set Vsync to Off in NVCP , display at 60 hertz and inside MSFS I set Vsync to On I see 65-66.5 FPS. Using GF Freesryle FPS it shows 132. So double which shows that FR is working

If I set Vsync inside MSFS to 33% or even 100% nothing changes with the FPS.

The last time I checked all these was 4-5 months ago and then the FPS matched the settings and changed with 33%-100%…..

Is this the N.V. driver or an issue in MSFS ?

 

Edited June 18, 20232 yr by GSalden

Just tried with Vsync Off in both NVCP and MSFS. The same FPS.

To me it starts to look that Vsync does not work anymore.

Either because of the NV “MSFS fix” driver or the latest MSFS update.

Could you try Vsync On/Off and check if it is working for you ? 

 

If I set clear weather instead of real weather the FPS go up bij 10%.

It looks like VSync is broken .. 

 

Edited June 18, 20232 yr by GSalden

Weird that it only works for some people. I'm running the 536.23 drivers, Vsync On in NCP with the 90FPS cap and it's working just fine. Not sure if it has to do with version (Steam vs Store) or something in the Windows environment.

11 minutes ago, Sethos said:

Weird that it only works for some people. I'm running the 536.23 drivers, Vsync On in NCP with the 90FPS cap and it's working just fine. Not sure if it has to do with version (Steam vs Store) or something in the Windows environment.

If you disable Vsync does the FPS change ? Are you also using a 40 card ?

Here I use 2x MSFS Store versions. Both pc’s are showing the same issue …
 

Edited June 18, 20232 yr by GSalden

7 minutes ago, GSalden said:

If you disable Vsync does the FPS change ? Are you also using a 40 card ?

Here I use 2x MSFS Store versions. Both pc’s are showing the same issue …
 

I'm on the Steam version. If I remove Vsync from NCP, still runs at FG 90FPS, due to the FPS cap (I was under the impression you needed Vsync for smooth operation with FPS cap, guess I was wrong). If I disable the FPS cap, it goes uncapped, 150-200+

Though I seem to recall it should cap itself a few frames under the monitor's refreshrate thanks to Reflex, but it doesn't seem to do that.

5 minutes ago, Sethos said:

I'm on the Steam version. If I remove Vsync from NCP, still runs at FG 90FPS, due to the FPS cap (I was under the impression you needed Vsync for smooth operation with FPS cap, guess I was wrong). If I disable the FPS cap, it goes uncapped, 150-200+

Though I seem to recall it should cap itself a few frames under the monitor's refreshrate thanks to Reflex, but it doesn't seem to do that.

Then Vsync might also not work for you but the NVCP FPS cap does. Here  the FPS cap does also work. 

6 minutes ago, GSalden said:

Then Vsync might also not work for you but the NVCP FPS cap does. Here  the FPS cap does also work. 

Just set my monitor to 60Hz and only enabled Vsync in NCP, that seemed to cap the sim as well. It caps it at 58, something Reflex does automatically, caps it at a few frames below the Vsync limit to avoid the 'sync stutter'. In-game FPS shows 29 and Steam overlay shows 58.

Appears to be working as intended here.

Edited June 18, 20232 yr by Sethos

11 minutes ago, Sethos said:

Just set my monitor to 60Hz and only enabled Vsync in NCP, that seemed to cap the sim as well. It caps it at 58, something Reflex does automatically, caps it at a few frames below the Vsync limit to avoid the 'sync stutter'. In-game FPS shows 29 and Steam overlay shows 58.

Appears to be working as intended here.

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 ?

3 minutes 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 ?

A 4090 yes, or else FG wouldn't be available. The debug counter just doesn't see the generated frames I reckon, something about where it captures the data in the render pipeline I assume. So overlays like RTSS, Steam etc. captures the frame generated FPS.

51 minutes ago, Sethos said:

A 4090 yes, or else FG wouldn't be available. The debug counter just doesn't see the generated frames I reckon, something about where it captures the data in the render pipeline I assume. So overlays like RTSS, Steam etc. captures the frame generated FPS.

I use the N.V. Freestyle FPS country next to the in-game FPS counter.