The new FrameLimiter setting in usercfg.opt  is a miracle!
I always had frame limit set in nvidia control panel to 90fps with g-sync (350hz monitor) and DLSS Frame generation On (Ultra/High).
It was working ok but always had some micro stutters, it was not smoooth.

Now, I turned off frame limit in NV CP, and set frame limiter in user.cfg to 45. DLSS Frame generation is on, gsync on.
I never had such stable and smooth 90fps! Its wonderfull! (At Brussels in ini 350) Frame generated picture quality is somehow better also. And the gpu is now only at around 50-60% utilization and stays at around 55 celsius.  

Working fine on my end. This sim is a GA flyer's nirvana.

(XC with the COWS DA40)

 

RTSS is the best to limit frames. The nvidia one has slightly higher overheads that can cause micro stutters. In-fact I believe over at blur busters they recommend RTSS over in-game frame locks. And, on this subject if you have G-Sync, use it! I always recommend leaving your HZ the highest it can go, and just use g-sync to adapt the frames to the monitor. No need to reduce your hz. 
 

PS those using lossless scaling instead of native frame gen, don’t produce more frames than your screen has hz, you’ll get a skipping effect, as it’s out of sync. That’s why native frame gen has ultra latency mode built in. Stops your frames exceeding your screens maximum hz. 

Edited April 17, 20251 yr by Ianrivaldosmith

11 minutes ago, Ianrivaldosmith said:

RTSS is the best to limit frames. The nvidia one has slightly higher overheads that can cause micro stutters. In-fact I believe over at blur busters they recommend RTSS over in-game frame locks. And, on this subject if you have G-Sync, use it! I always recommend leaving your HZ the highest it can go, and just use g-sync to adapt the frames to the monitor. No need to reduce your hz. 
 

PS those using lossless scaling instead of native frame gen, don’t produce more frames than your screen has hz, you’ll get a skipping effect, as it’s out of sync. That’s why native frame gen has ultra latency mode built in. Stops your frames exceeding your screens maximum hz. 

I think that this new setting is totaly diferent thing. RTSS and NV CP are limiting final output. That means that sim will utilise gpu to render as much frames as it can, generated frames will bi inserted and then this tools will cut at set max output.
This new setting will limit rendering frames at sim level. gpu will be utilised only to reach that limit. and then it will insert generated frames. 
So set it to half of your monitor refresh rate (or wanted final fps, something reasonable if it is high performance monitor)    

 

2 hours ago, GSalden said:

Up to now you would use FG without a limited to get the most benefit out of it.

Nope, probably some did, others didn't. I always used my frames capped at 60 in Afterburner with FG ON because I have my monitor refresh rate set to 120Hz and the sim (MSFS 2024) is completely fluid. This is nothing new. And instead of 240w it is consuming 80 to 110w and is silent. Many people have always been using FG like this. There is no benefit letting it run unlimited (unless maybe if you are playing an FPS game), your electricity bill will increase a lot and you will probably have stutters.

1 hour ago, SAS443 said:

Working fine on my end. This sim is a GA flyer's nirvana.

(XC with the COWS DA40)

 

Hope is that we Tube-liner drivers will benefit by the time SU3 releases….

4 hours ago, flyingscampi said:

Both the frame limiting and frame generation are handled by the sim, not by external drivers/apps.

Because one can select NV or AMD FG in the sim you're calling it 'being handled by the sim', correct?  Does MS/A actually modify something to create NV FG as an option in the sim or is MS/A just accessing a block of NV code that does the FG?  Just curious as I have no idea myself.

51 minutes ago, Alvega said:

Nope, probably some did, others didn't. I always used my frames capped at 60 in Afterburner with FG ON because I have my monitor refresh rate set to 120Hz and the sim (MSFS 2024) is completely fluid. This is nothing new. And instead of 240w it is consuming 80 to 110w and is silent. Many people have always been using FG like this. There is no benefit letting it run unlimited (unless maybe if you are playing an FPS game), your electricity bill will increase a lot and you will probably have stutters.

Absolutely for me this has been the case.  I haven't yet moved to AutoFPS now just using DynamicLOD Reset but in any case my practice with my current sim graphics settings is to set the frame lock at least 10% under the wide open rate in any one moment.  Using RTSS' HotkeyHandler.dll or whatever it's called you can change your frame lock while flying simply by hitting a key combination you configure.  While 60+ FPS is a decent goal I'm still fine on down to 50FPS-native, so even when the sim can deliver 80FPS-native which it most certainly does I'll still lock it at 50 or sometimes 60 but again need that 10%+ buffer to cope with transient increases in demand that can nail the main thread and produce a stutter.  I have nearly stutter-free flights now though spots like EHAM can drive the native rate to as low as 42 in spots at which point I will have to eat the 10% headroom to have a tolerable frame rate, that is w/ the usual add'l loads like BATC, FSLTL, SLC etc.  I've traded in FG doubling to avoid artifacts and 2nd screen judder and am also able to use TAA now which eliminates GC character blurring/smearing.  So for me sacrificing that doubled frame rate which I did play with in 2020 for many months I get really excellent and stable image quality, no artifacts of any kind save some distant aberration from the TAA but it's so far off in infrequent and at that range it's very short on detail anyway so not an issue that troubles me.  And one does acclimate to the lower frame rate, say dropping from 120FPS-fg to 60FPS-native but as I say even 50FPS-native is quite good for how I use 2020 or 2024 now.

Weird, I have frame limiter set in the config file at 48, but when I load the sim and Im sitting at the gate its showing 60 some frames, its ignoring what I set.

33 minutes ago, Bill A said:

Weird, I have frame limiter set in the config file at 48, but when I load the sim and Im sitting at the gate its showing 60 some frames, its ignoring what I set.

FG on? It cant distinguish and will show double...

Ahh yes  FG is on

4 hours ago, cchiozza said:

FG on? It cant distinguish and will show double...

But then it should show 96 Frames. At least if his system can generate 48 normal frames all the time.

I do more testing, I did not notice it was not very smooth...now if I place 48 in Niva Tuner, its alot smoother in performance compared to havig it set in the config file. And both set wtih FG on. Now Rivia Tuner will display the frame counter even if I dont have it used to cap frames and even with FG on if I cap at 48 or 40 or whatever # i place it will display the capped # of course if the sim can reach it. But even when capping via the config and using riva tuner to only display the frame rate, it would still show #s over 48 like its not capped at all., Ill test and turne off FG and see if I do get a solid 48.

On 4/16/2025 at 1:35 PM, Mike_CFII_MEL said:

The last few sets of drivers from Nvidia have big time issues, last real stable version is 566.36.
 

 

{'m still using 533.36 ndivia drivers and not experiencing any issues

3 minutes ago, Bigmack said:

{'m still using 533.36 ndivia drivers and not experiencing any issues

That's what I'm using, I haven't tried the 576.02 drivers that were released on the 16th. as of yet.