zildac

I couldn't get it to work with DLSS tweaks only, by setting J in the .ini. I had to also set the NVPI preset too, then set the DLSSTweaks .ini preset to DEFAULT.

I have applied it only to the DCS profile, I am also running DLSSTweaks and with the profile in DLSSTweaks set to default and Preset J set in the DCS NVPI profile the DLSSTweaks HUD confirms preset J is in use. I ONLY used DLSSTweaks previously to set profile F instead of the default E used by DCS and of course the HUD function.

OK, so DLSS probably not going to do much for you tbh. Can still use DLAA far better than MSAA especially in VR

No, it will use preset J regardless the "levels" are particular variations to how it does its "stuff". Odd, re the FPS display usually just click the down arrow and it expands the graph and at the top of the graph it should tell you in coloured text what the limiting factor is.

You still need to select what "level" or DLSS you want to use in the DCS UI. With a 4090 and a Varjo Aero I only use DLAA, do you need DLSS with your setup? What does the DCS in game FPS counter say is "limiting" you.

For me (I am also DLAA only) there is less ghosting, I am using Preset J

Use DLSSTweaks and use the hook method for dxgi

You've downloaded this version: https://github.com/neatchee/nvidiaProfileInspectorForkAIO/releases/ nullEdit the XML file overwrite Profile G so it looks like the picture in my first post null

Apologies, no, this is the NVPI version I used, you may need to update .NET framework: https://github.com/neatchee/nvidiaProfileInspectorForkAIO/releases/ The XML is part of the archive, just edit it as per my screenshot, save and then select Profile J. In fairness you could call the profile "SuperDuperDLSS" as long as the hex value is: <HexValue>0x0000000A</HexValue>

Profile "J" is the new transformer preset. You need to force it via NVPI and you will also have to add it to the config XML file in order for it to be selectable in the GUI. CustomSettingNames.xml - the highlighted line needs to be added and selected in the DCS profile in NVPI and it will NOT persist a driver update, so you'll need to reapply. null

Exactly the process I followed, thanks for summarising it well.

They were bundled with the latest cyberpunk patch. Theres three of them, you only need one of them for DCS. I'm not going to link them here but they are easy to find with a little Google Fu.

I've just tried the DLSS 4 DLL and forced the profile to J, I can't really see any difference positive or negative using DLAA over the old V3 DLSS DLL. I did try DLSS briefly and noticed no ghosting, but I'm CPU limited so DLSS isn't going to be doing much if anything I guess.

Limewire... that's a blast from the past!

Be very interested to hear of any uplift in performance you get as a result of the 9800X3D

I'm CPU limited with a 4090 and 14900KS, I can't see a 5090 having anything other than a negative impact on my bank balance in the context of DCS.

Seems to work without issue, although very limited testing on my part.

It was an observation, not a judgement on the legality or morality of it.

From around 1:45, take a look. The smoke and the explosions look different, but again, perhaps it's just post-processing "magic"

I get that, my point was that the smoke is not the same, however it was "made"

Bit cheeky really, I mean the smoke effects in the video were absolutely not the same effects we see in game at present.

Fantastic...much appreciated and anticipated!

Can we do the blue fox radar now and get on with the Harrier variants?!

MSAA in VR produces awful shimmering, it's blatantly obvious and easy to spot. DLAA is my current go to.