1 hour ago, TacomaSailor said:

Are you saying that I should just ignore the loss of Frame Gen?

Go back and read the rest of my comment--within it contain the DEFINITIVE SOLUTION to getting DLSS4 up and running, and staying there, with any recent NV driver.  But again, if you just like tinkering, have at it.  I am loving what I've got going now!

https://www.avsim.com/forums/topic/663647-killing-three-birds-w-one-stone-batc-dlss4-performance/

 

2 minutes ago, Noel said:

Go back and read the rest of my comment--within it contain the DEFINITIVE SOLUTION to getting DLSS4 up and running, and staying there, with any recent NV driver.  But again, if you just like tinkering, have at it.  I am loving what I've got going now!

https://www.avsim.com/forums/topic/663647-killing-three-birds-w-one-stone-batc-dlss4-performance/

 

It seems you are missing what I, and many others have been writing about.  I DID setup the sim and system exactly as shown in the Definitive Guide and everything worked perfectly... for a while.  All was good and tinker time was over.

Then, as I wrote before, after several nice flying sessions using the Definitive Guide setup;  suddenly, with no apparent changes to system or sim,  Frame Gen was gone from the In Game options.  The ONLY way I could restore Frame Gen In Game was to change the enable DLSS FG override setting in Profile Inspector to the opposite (0) value from that specified in the Definitive Guide.   Getting to that decision required a lot of tinkering, swearing, and fiddling.

It is apparent to me, if not everyone, that there are many covariates in the system and their relationships are not clearly understood.  What is obvious and simple for you doesn't seem to work consistently for others.

4 hours ago, TacomaSailor said:

It is apparent to me, if not everyone, that there are many covariates in the system and their relationships are not clearly understood.  What is obvious and simple for you doesn't seem to work consistently for others.

Woah, I'm afraid you again missed the whole point of my responses.  What the Def Guide says if rife with potential issues as you and so many other have experienced.  When you simply drop the correct DSLL files into where they live you absolutely will experience everything you can possibly get out of DSLL4.  Using NV App or ProfInspector to tease the current DSLL files out of the latest NV driver is vastly more complex and therefore susceptible to those very issue you refer to:  there are many covariates in the system and their relationships are not clearly understood.  Yeah, my sys and the latest NVidia driver would not get along.

All of that disappears and you are, one last time, guaranteed to NEVER have to grapple the kinds of issues you brought up twice now.  If your goal is to make work what was intended by NV as a solution for staying on top of the latest DSLL files inserted into your sim from the driver then I understand you have a another goal which is to try to make something not 100% for all user turn-key, better.  Have at it.  If your goal is to have absolute assurance you will have the DSLL4 every single time up and never have to give it a second thought, the solution is right in front of you.  When the next significant jump in DSLL arrive you will need to DL those and insert then into your Source folder.

Well, please HEEEEELP!

Ok, no need to Panic !  It's just a GAME 🙂

I just came from that other thread which I followed to make DLSS with DLAA work in my FS 2024 install, and it worked and I used it for a while until I decided to revert back to good old TAA @ 30 FPS forced through either Nvidia App or Nvidia Control panel or even Nvidia Inspector, it doesn't matter ( I haven't used the in game VSync + 50% Refresh Rate method for a while and use the limiter from NCP, and now the App, or even through RivaTunner as I did before, and it gives me a better 30 FPS experience).

But I wanted to try 60 FPS in my RTX 3060 Ti. Well, it hammered my GPU temps more than I like to see, and l decided to revert back to TAA.

But I'm curious about what @Noel describes, and if I did understand it right what he says is that he doesn't use either the App or Nvidia Inspector and simply manually, or through the Swapper, places the DLLs in their right place ? Is it this simple afater all ?

@Noel, thanks for your post linked above. I never really tried to get BATC with FSLTL traffic injected through FSLTL injector (just used that with FSHUD) and I would like to know how is it possible to set BATC's fps to 30 fps instead of the default 60?

And, btw, what is that NVSR ?  Is it like setting VSync in game + 50% Half Refresh Rate as I do when in TAA to get 30 FPS (my monitor is 60Hz) ?

Edited February 4, 20251 yr by jcomm

6 hours ago, Noel said:

Woah, I'm afraid you again missed the whole point of my responses.  What the Def Guide says if rife with potential issues as you and so many other have experienced.  When you simply drop the correct DSLL files into where they live you absolutely will experience everything you can possibly get out of DSLL4.  Using NV App or ProfInspector to tease the current DSLL files out of the latest NV driver is vastly more complex and therefore susceptible to those very issue you refer to:  there are many covariates in the system and their relationships are not clearly understood.  Yeah, my sys and the latest NVidia driver would not get along.

All of that disappears and you are, one last time, guaranteed to NEVER have to grapple the kinds of issues you brought up twice now.  If your goal is to make work what was intended by NV as a solution for staying on top of the latest DSLL files inserted into your sim from the driver then I understand you have a another goal which is to try to make something not 100% for all user turn-key, better.  Have at it.  If your goal is to have absolute assurance you will have the DSLL4 every single time up and never have to give it a second thought, the solution is right in front of you.  When the next significant jump in DSLL arrive you will need to DL those and insert then into your Source folder.

Are you a software developer?, I've never heard anyone involved in the industry make such assertive guarantees

 

12 hours ago, TacomaSailor said:

It seems you are missing what I, and many others have been writing about.  I DID setup the sim and system exactly as shown in the Definitive Guide and everything worked perfectly... for a while.  All was good and tinker time was over.

Then, as I wrote before, after several nice flying sessions using the Definitive Guide setup;  suddenly, with no apparent changes to system or sim,  Frame Gen was gone from the In Game options.  The ONLY way I could restore Frame Gen In Game was to change the enable DLSS FG override setting in Profile Inspector to the opposite (0) value from that specified in the Definitive Guide.   Getting to that decision required a lot of tinkering, swearing, and fiddling.

It is apparent to me, if not everyone, that there are many covariates in the system and their relationships are not clearly understood.  What is obvious and simple for you doesn't seem to work consistently for others.

Indeed, One of the weird ones that I get from time to time is the changing of some options in the sim without my intervention, I'm not talking about the settings resets that sometimes happen with a sim update but simply between shut downs and re opening.

Latest one I have noticed during some troubleshooting is the sim insists on setting the AA to DLSS even though I manuaLly set it to TAA, its done it 3 times in a row now.

Edited February 4, 20251 yr by Rusty Spanner

8 hours ago, Noel said:

When you simply drop the correct DSLL files into where they live you absolutely will experience everything you can possibly get out of DSLL4.

no, not everything. because only copying the 3 DLLs does not change/apply the new DLSS4 TransformerModel "Profile", not a bit. if it were that simple (to only copy 2 files wouldn't require an extra batch file) 🤣 we wouldn't have this 24 page long thread.

"DLSS transformer models improve image quality with improved temporal stability, less ghosting, and higher detail in motion."

 

On 2/2/2025 at 9:39 PM, TacomaSailor said:

Why did the nVidia App DLSS Override FG option line change - the in game Frame Gen option/row in Graphics settings had vanished

I think the NVidiaApp is a bit misleading/not obvious enough at first glance in that this OVERRIDE - Frame Generation applies only to the new, RTX50 exclusive MultiFrameGen. if you try to apply this to a NON-RTX50 card, it might have disabled your RTX40 single-FrameGen altogether. Could be the same issue that John Fields has reported further up in this thread. if you click the tiny "i" information icon in NvidiaApp icon next to "DLSS Override - Frame Generation" it will show this more detailed:

 

time for Asobo, to implement the new DLSS 4 option directly in game settings. just like CyberPunk77 does it. and we wouldn't need all this KungFuzius about DLSS 4.

Edited February 4, 20251 yr by turbomax

1 hour ago, turbomax said:

I think the NVidiaApp is a bit misleading/not obvious enough at first glance in that this OVERRIDE - Frame Generation applies only to the new, RTX50 exclusive MultiFrameGen. if you try to apply this to a NON-RTX50 card, it might have disabled your RTX40 single-FrameGen altogether. Could be the same issue that John Fields has reported further up in this thread. if you click the tiny "i" information icon in NvidiaApp icon next to "DLSS Override - Frame Generation" it will show this more detailed:

Ah! So, since I am on RTX 3060 Ti this surely applies, and there i sat least one of the entries when using Nvidia Profile Inspector (NPI) that I shouldn't change to "00000001" I guess ?

That's probably what is causing "Frame generation" not showing up as an option at the ingame settings of FS 2024...

I can "only" choose DLSS and DLAA for the AA type, but I remember being able to actually see the FG option with some tweaks back in my FS 2020 times, when I did use the DLSS Swapper app.

@turbomax, can you please remind me of the exact process you've followed to profit from DLSS4 in FS 2024? Thx !!!

57 minutes ago, jcomm said:

@turbomax, can you please remind me of the exact process you've followed to profit from DLSS4 in FS 2024? Thx !!!

I'm obviously not turbomax, but I think they'll agree that in order for everything to work correctly:

• the DLSS .dll files need to be present in the MSFS2024 content folder, either by copying these manually or by using DLSS Swapper
• some settings need to be changed in nvidia profile inspector for DLSS4 to work correctly (with preset K) - see below for step by step instructions

If not using DLSS Swapper, the latest DLSS4 .dll files are available from my Google Drive here. 

Download the latest version of nvidia profile inspector here. Make sure that there is no file named CustomSettingNames.xml present in the nvidia profile inspector folder. 

Run Nvidia Profile Inspector as an administrator and, in the Global Profile, set 0x00000001 for the following settings:

• Enable DLSS-FG override

• Enable DLSS-SR override

• Enable DLSS-RR override

Set 0x00FFFFFF for the following settings:

• Override DLSS-RR preset

• Override DLSS-SR presets

Click Apply changes in the top right corner to confirm the changes.

To verify that everything has worked correctly, use these two regedit files here to quickly turn DLSS indicator on/off. It should look like this:

---

Btw I just saw that there's an nvidia hotfix driver out 

 

Edited February 4, 20251 yr by Cpt_Piett

3 hours ago, turbomax said:

(to only copy 2 files wouldn't require an extra batch file) 🤣

The batch file I created was only to simplify replacing whatever DLSS files would import into MSFS 2020 when an MSFS update happens since I read that would override whatever DLSS file was currently installed.

Thanks for the clarification.  So what the video states is that while I am using DLSS4 now, it's the "CNN" method being employed.  Got it thanks.

I'm still stoked at just how good everything is even w/ the CNN model and I see best ever IQ and *some* reduction in ghosting already which is great.  But this begs another question:  if DLSS4 files are installed can I still go back and implement the transformer methods even though I'm using an older driver?  After multiple tries at getting the new NV driver installed I was never able to get it to even work without using any of the transformer methods using the app nor Inspector.  Also is there a need for installing the 3rd DLSS4 file relating to MFG if I'm using a 4090?

 

Edited February 4, 20251 yr by Noel

28 minutes ago, Cpt_Piett said:

I'm obviously not turbomax, but I think they'll agree that in order for everything to work correctly:

• the DLSS .dll files need to be present in the MSFS2024 content folder, either by copying these manually or by using DLSS Swapper
• some settings need to be changed in nvidia profile inspector for DLSS4 to work correctly (with preset K) - see below for step by step instructions

If not using DLSS Swapper, the latest DLSS4 .dll files are available from my Google Drive here. 

Download the latest version of nvidia profile inspector here. Make sure that there is no file named CustomSettingNames.xml present in the nvidia profile inspector folder. 

Run Nvidia Profile Inspector as an administrator and, in the Global Profile, set 0x00000001 for the following settings:

• Enable DLSS-FG override

• Enable DLSS-SR override

• Enable DLSS-RR override

Set 0x00FFFFFF for the following settings:

• Override DLSS-RR preset

• Override DLSS-SR presets

Click Apply changes in the top right corner to confirm the changes.

To verify that everything has worked correctly, use these two regedit files here to quickly turn DLSS indicator on/off. It should look like this:

---

Btw I just saw that there's an nvidia hotfix driver out 

 

DX11? 

Looks like you must be up and running now with the transformer methods.  Tell me, how much improved are the areas these methods are impacting?  Here, ghosting/smearing is better than with previous DLSS CNN methods but is still there.  How about raw performance using DLAA?

1 hour ago, Noel said:

DX11? 

Looks like you must be up and running now with the transformer methods.  Tell me, how much improved are the areas these methods are impacting?  Here, ghosting/smearing is better than with previous DLSS CNN methods but is still there.  How about raw performance using DLAA?

DX12. I think there's less ghosting on glass cockpits with DLSS4. Performance is good with DLAA, especially with latest driver. 

after all is said and done re. DLSS4, the $ 1.000.000 question remains:

will Asobo support DLSS4 , if not on day one, hopefully on day 60 or so, in the next update/hotfix ? so we can close our MSFS body and repair shops and go flying again?

9 minutes ago, turbomax said:

after all is said and done re. DLSS4, the $ 1.000.000 question remains:

will Asobo support DLSS4 , if not on day one, hopefully on day 60 or so, in the next update/hotfix ? so we can close our MSFS body and repair shops and go flying again?

So is it not solid/stable even when going thru steps to enable transformer methods?  Or are you just say it ought to be a simple enable in-sim with no need to use Inspector or what have you?

I was able to get to Profile K indicated on the screen in MSFS 2020 but once again, it essentially freezes while on the welcome screen so I never get a chance to see this.  I was going to try DDU which I've never used and never needed to but wasn't sure what to check and uncheck and didn't want to create any issues.  I always do NV's clean install option which does clear the DXcache folder of the current driver-specific files but maybe some DDU does might help.  I just want to see this for myself because as mentioned I already have really good IQ with DSLL4 CNN and all of my sharpening algorithms.