Looks like there is a problem now with the max frame rate setting in the sim. It seems it works now AFTER frame generation instead of BEFORE.
Can you expand on this? Are you in SU4 or SU5 beta? Where did you come across this?
I installed this latest dlss dll with dlss swapper and then started the sim. When i choose amd fsr3 fg it seems to work ok. Which by itself is strange when using a rtx 4070 ti.
Regular su4 version.
I’ve installed 310.6 dll with DLSS swapper. For what I see I’ve a lot better visual rendering quality, no stutter no ctd, very smooth. I’m using DLSS+DLAA+2xFG locked to 60 FPS (x 2 FG) on a 5090. FS2024 SU4 version
Hi everyone,
I’d appreciate some advice regarding DLSS 4.5, as I currently lack in-depth knowledge and hands-on experience with it.
Could anyone recommend optimal DLSS 4.5 settings for my PC configuration? At the moment, I’m running Microsoft Flight Simulator 2024 in 4K with Ultra settings, using DLSS in Quality mode.
Based on my setup, what DLSS configuration would you suggest? Also, within DLSS Quality mode, which preset tends to deliver the best balance between image clarity and performance?
……………………………………………
ASUS TUF GAMING X870-PLUS WIFI
AMD Ryzen 7 9800X3D
ASUS TUF Gaming LC II 360 ARGB
G.SKILL 32GB KIT DDR5 6000MHz CL30 Trident Z5
Samsung 9100 PRO 2TB PCIe 5.0 4x NVMe
GAINWARD GeForce RTX 5080 Phoenix 16G
Seasonic Focus GX-1000 ATX 3.1
Montech KING 95 PRO Black
Same for me. When I set the max frame rate to 30 in the simulator, with frame generation enabled I no longer get 60 fps, but a maximum of 30 fps.
By no stretch of the imagination am I in full knowledge of the facts. but what i read on the subject is that for the dynamic frame generation to work the game must also have the new Streamline 2.11 libs installed as well. If you read the blurb I think that it mentions that only 8 or 9 games are compatible, MSFS not being one of them.
It may be that you could manually swap over the libs, after backing up the original ones first, to see if this fixes it.
The reason for the Streamline lib backups is that every new release/beta will probably fallback to the 2.7.2 versions that are currently in use.
Unless of course that the Nvidia App also overrides the Streamline version of the game.
So anybody willing to try?
Frame Generation not working at all for me. Without setting max frame rate or using DLSS frame generation I get 60FPS. Turn on frame gen 2X and it still get 60FPS. Set max frame rate @ 30 (60mhz monitor) and I get 30 FPS. Turn on DLSS Frame generation and still get 30FPS. I set the max frame rate in both Nvidia CP and Nvidia App. no difference. RTX 4070S. Setting max frame rate results in main thread almost doubling from 15-16ms to almost 30ms. Beta 5 1.7.16.0, DLSS 310.6.0 , Nvidia driver 595.97, Don’t have any idea why??? I’m back to no Max Frame Rate, no frame generation, and 60FPS.
In Nvdia App check, DLSS Override in program configuration, not in global configuration and then frame generation: established value B.
For me, this solved the problem of frame generation using DLSS and DLSSG 310.6.0 I hope this is helpful for you too. I’m using an RTX 4070.
Thanks – that sorted the problem! 
The official NVidia guidance is to use J or K with Quality. I personally use M. L and M are “heavier” models with more compensation for the lower rendering resolutions of Balanced and Performance, but to me if you can handle it performance-wise, I’d rather have the higher visual quality. So essentially L and M compensate more for visual acuity loss than J and K, but cost you more performance. But my performance (12700K/4090) is perfectly fine with M.
Based on your setup, you should be good with DLSS Quality and Model M. In the NVIDIA app, in the profile for MSFS 2024, go to DLSS Override Model Preset > Custom tab > Super Resolution, then select Model M and apply. If you notice any performance drop, just revert to the default setting.
NVIDIA has improved the DLSS models recently, so Model M should work well on your setup.
@Helihun6378 To take full advantage of the new NVIDIA app settings and DLSS models, make sure you join the NVIDIA app beta. To do this, open the NVIDIA app and go to Settings > About. Check “Opt in to access Beta or experimental features”
then restart PC. After the restart, open the NVIDIA app again.
Sadly this didn’t solve it here. Even reverting to the previous DLSS dll’s doesn’t help. The Nvdia app gives an error: There was a problem applying the settings. Reinstalling the video driver also no luck.
Weird problem.
Switching to value B in Nvidia App didn’t solve the problem for me. However, switching to ‘recommended’ did solve it for me. I now see the increased frame rate using DLSS frame gen. However, I still get better CPU & GPU performance with no frame gen and 60FPS on my 60HZ monitor/TV.
I appreciate your solution of changing the DLSS Override in the App.
For now i changed to frame generation with the AMD FSR3.1 dll. 
I noted that sometime FG doesn’t start at all or switch off during flight. I find a workaround switching Alt-Enter to win mode than again alt-enter to go full screen. The 350.6 is a RC1 version of FG dll. I have now DLAA 48fps and FG set to x2 to the limit of 60fps (my 4K monitor is 60hz), no problem at all now.
Thanks! I actually managed to sort it out by selecting preset B for FG in the Nvidia app, as recommended above. Since then, I’ve been getting the 60 FPS I wanted when I set the maximum frame rate to 30 in the in-game settings.
Well, I finally got to test it in VR. i9-14900k 4090 64GB RAM and a Quest 2.
MSFS Quality with preset M set via DLSS swapper. Latest NVIDIA driver. I used the Fenix at DD KDCA. No VATSIM or injected aircraft.
Wow. Just wow. Clear as TAA on the glass panels. The MCDU and ND text was always a bit.. blurry? With preset K and the old DLSS file.
Now it’s clear as TAA was. Oh, spinning the com tuning knobs - zero ghosting on the digits. Same with changing altitude. Zero ghosting.
There was a very very slight ghosting/smearing effect on the altitude tape, but only in the ones and tens digits… climbing at over 2k’/min and you aren’t really looking at the ones and tens anyway and honestly they move so fast, this is pretty close to reality. Every thing else - zero ghosting/smearing. Performance seemed to not be affected, but I didn’t do a scientific test either. Just didn’t notice anything other than the usual smooth head movements. No jerkiness or stuttering.
I mean - wow. This could be a game changer.
Final test will be to try it out on VATSIM with some injected aircraft… just to see if performance really isn’t impacted.
But wow!
Thinking out of the Box: After a switch to SU5 Beta and then back to SU4 Regular the FG problem is solved.