44 minutes ago, Noel said:

Or are you just say it ought to be a simple enable in-sim with no need to use Inspector or what have you?

that would be one option, as I showed in the CyberPunk setup screen above but then this forum would be pretty quiet. and we all would be gone flying instead 🤣. others might argue there is no fun in that and prefer the open heart operation method using profile inspector with 0xFFFF and 0x0001

Edited February 4, 20251 yr by turbomax

Well, it was either the filters (Alt F3) in the NV app, or the app itself which caused MSFS 2020 to essentially freeze up after getting to the Welcome screen such that I never could test the transformer models.  I updated to the latest hotfix driver from NV, and this also did not solve the crash issue.  Of course clean installs, reboots, yada yada.  I finally uninstalled the NV app, and voila, now how Profile K operative as verified by the reg file thanks Cpt.  I was already set at NVSR + DLAA so stayed there.

So I had a chance to get off the ground in the PMDG 738 and here is unequivocally what I witnessed:

1. GC ghosting/smearing was NO BETTER than straight DLSS4 CNN model.  I did notice an improvement over DLSS3 w/ and it's essentially identical to this transformer model.
2. Since I no longer had access to GFE/NV App filters, image quality absolutely went down for me.  Perhaps if one looked really closely at fine detail, like the swinging palm fronds shown in the video, deeply scrutinizing for improvement, it presumably would be there.   But without my prized Details Filter out of GFE now NV app it was a serios downturn in image quality.
3. Performance I believe should be better but haven't really verified that yet.

So what I need is either a copy of older GFE to see of I can get back to the Details filter, or move on to ReShade I believe that is another option but never used it.  I searched for a GFE installer to no avail.  Right now no way I would use the transformer model over CNN w/ Details Filter.

I could revert back to the prior NV driver, reinstall GFE, reinstall the latest driver/hotfix but not reinstall the NV app.  So here goes...

It worked and now can compare apples to apples, that would be CNN + Details, and Transformer + Details.  I'm assuming the only confirmation is what I see here.  I see 'Autoexposure' was ON, whereas for Cpt_Piett was OFF I think:

 

 

 

 

 

Edited February 4, 20251 yr by Noel

Cpt_Piett and Noel

I am sure that what you write is accurate and correct for your systems.

For my system (Win 11 23H2, None Beta, RTX 3060 Ti) I have to change Enable DLSS-FG override to 0 not 1 to make Frame Gen available in MSFS 2024.  Making that one change turns Frame Gen on or off.  I change nothing between sim sessions except for that one parameter and Frame Gen comes or goes.

The In Game display at the lower left about DLSS status is identical to what is shown by Cpt_Piett. 

I have verified there is NO custom name.xml in the folder.   When 

 

I am not arguing what is right or wrong - I am just pointing out that what works for one system/sim may not work in another.  

 

Slightly stunned at this point and I have to think perhaps 2024 might manifest what can come out of Profile K.  Right now with only one flight halfway done but enough to see a variety of weather and clouds, scenery detail, as well as GC ghosting/smearing, I can unequivocally state the real joy here came from DLSS4 CNN, not Profile K.  I say that because the entire image including in PMDG 738's VC CNN image is better, more stable and weird as heck I got some subtle but repeatable artifact of an entire glass display when panning fairly rapidly and that does not happen w/ CNN.  And the strobing/flickering I get on most tarmac in most high contrast lighting was actually WORSE.   I am so used to crisp I assume secondary to using several sharpening algorithms including as mentioned the Details Filter.  If you ever go there be aware it has its own sliders to config and I have its Sharpness and Clarity filters both maxed.   PrimaryScaling I thought was to be overridden when going from TAA to NVSR but then I see in the regedit display ON it shows 5160,2160 which is what my 1.5 setting on PrimaryScaling is supposed to generate.  Image quality and performance now is absolutely best I've ever seen and not sure how it could be improved further quite frankly.

So we're out of Profile F by virtue only of resetting Inspector back to NV defaults then Apply.  It now shows Profile C.  I have no idea what that is but it looks and acts like what I had before enabling Profile K.  Is Profile C just another 'transformer model' that perhaps is better for MSFS 2020?  Or is it back to CNN?

Ultimately this quest to have a real look at Profile K turned out to be, for MSFS 2020, a net loser here and again the real pearl came from installing the DSLL4 files.

Cheers

Edited February 4, 20251 yr by Noel

What is CNN? Except of the obvious 🤣

" DLSS from its very beginning relied on AI to reconstruct details in Super Resolution, and with DLSS 4, NVIDIA is introducing a new Transformer-based AI model to succeed the Convolutional Neural Networks previously used—for double the parameters, four times the compute performance, and significantly improved image quality."

https://wccftech.com/nvidia-dlss-transformer-model-takes-over-cnn-all-geforce-rtx-gpus-improved-visual-quality/

https://www.techpowerup.com/review/nvidia-dlss-4-transformers-image-quality/

 

Edited February 4, 20251 yr by turbomax

How is it that Profile K seems to be what is being sought here?  Why not Profile J, or even C as apparently I'm now using.  I searched Google to no avail on this particular question.

19 minutes ago, Noel said:

How is it that Profile K seems to be what is being sought here?  Why not Profile J, or even C as apparently I'm now using.  I searched Google to no avail on this particular question.

It's supposed to be the preferred preset for DLSS4 and the latest driver. Sorry, don't have a reference.

I figured it was preferred but haven't a clue why.  I tell you on no uncertain terms whatever Profile C is it beats Profile K is on this machine.

I found this: https://www.destructoid.com/nvidia-dlss-presets-what-do-they-mean-and-which-one-should-you-choose/

But no idea how accurate it is. 

3 hours ago, AnkH said:

I found this: https://www.destructoid.com/nvidia-dlss-presets-what-do-they-mean-and-which-one-should-you-choose/

But no idea how accurate it is. 

Great article! 

Quote

• DLSS Preset A: The basic, default choice for the more mainstream DLSS modes (i.e. Performance, Balance, and Quality). Preset A has been around for a long while, and it’s a good choice if you want to deal with excessive ghosting, especially if you’re using it in a game that doesn’t have all the DLSS inputs, like motion vectors for example.
• DLSS Preset B: A special variant of Preset A that’s purpose-built specifically to improve upon the Ultra Performance DLSS tier.
• DLSS Preset C: A modified variant of Preset A designed for fast-paced games that prefer current frame meta-data over anything else. You get a less temporally stable image, but the flip side is that you don’t get much ghosting in turn.
• DLSS Preset D: A modified variant of Preset A designed for slower-paced games that take more temporal data into account than Preset C. It’s the flipped version of Preset C, effectively, deliveingr improved image stability at the risk of extra ghosting.
• DLSS Preset E: A generally improved sub-variant of Preset D, and it should be used over D in most cases.
• DLSS Preset F: The default DLSS Preset version used for Ultra-Performance and DLAA levels of supersampling. Very minor ghosting present if used at its targeted DLSS quality levels.
• DLSS Preset G: Currently unused, from the look of it.
• DLSS Preset J: The baseline Transformer-based DLSS, delivering a substantial improvement in image quality compared to the other Presets’ CCN-based model.
• DLSS Preset K: A further improvement upon Preset J, which seems to reduce vegetation shimmering (though it’s still present in affected games).

 

Edited February 5, 20251 yr by Cpt_Piett