DLSS "update"

[diamond26]

50 minutes ago, sleighzy said:

What Nvidia driver version you on?

566.36

[Rufuz64]

 

[sleighzy]

6 hours ago, Rufuz64 said:

 

Check to make sure you're using version v1.1.2 released yesterday as this may have been fixed. It's updating the dlls in bin and bin-mt for me.

[slughead]

Release DLSSTweaks 0.310.0.0 (transformers) · emoose/DLSSTweaks

[diamond26]

I don't know what happened but after installing the latest Nvidia drivers 572.16, I lost eye tracking and I don't see the option for it in DCS VR Settings!!! Also DCS crashes if I use new dll and new drivers

[slughead]

2 minutes ago, diamond26 said:

I don't know what happened but after installing the latest Nvidia drivers 572.16, I lost eye tracking and I don't see the option for it in DCS VR Settings!!! Also DCS crashes if I use new dll and new drivers

See my post above.

[Mustang]

I get a crash upon launching DCS World when using the above DLSSTweaks that slughead linked, if I remove the dxgi.dll from folder DCS launches fine.

[sleighzy]

17 minutes ago, Mustang said:

I get a crash upon launching DCS World when using the above DLSSTweaks that slughead linked, if I remove the dxgi.dll from folder DCS launches fine.

I don't have an answer to that as I don't use the dxgi.dll approach, you can just use the force global override option in DLSSTweaks config app to set the preset without needing the dxgi.dll file.

[slughead]

I used the dxgi approach and it works ok.

[slughead]

26 minutes ago, sleighzy said:

I don't have an answer to that as I don't use the dxgi.dll approach, you can just use the force global override option in DLSSTweaks config app to set the preset without needing the dxgi.dll file.

I think you can use the override option in the nvidia settings as well.

[sleighzy]

7 minutes ago, slughead said:

I think you can use the override option in the nvidia settings as well.

Yup, had been using that more recently (bit of hoop jumping still, e.g. another version of NVPI and custom settings file updates etc.) but switched back since the latest release. Trying to keep the number of tools down

Edited January 30 by sleighzy

[Tazer83]

I tried this for the first time today and it's blown my mind with the level of detail and performance. It's just a real shame we can't use it online, I dont want to take the risk.

 

Edited February 1 by Tazer83

[Esac_mirmidon]

Is working ok online.

Tested with my Squad mates

[St4rgun]

Dear @BIGNEWY it seems that DLSS 4 Preset "J" is the second best thing after sliced bread, its quality is exceptional.

Unfortunately right now we can only "hack" this version into DCS by DLL changing and for another yuestion you replied that the devs will work on DLSS 4 only AFTER deploying Vulkan.

As it seems that the performance and quality of DLSS 4 even in its unofficial state is so massive, that it needs URGENT attention may I ask if this timing has been changed?

If your statement means that we're just mere weeks away from Vulkan, then it's OK, but if not, then IMHO the devs should really prioritize the full integration of DLSS 4 before anything else, it's so revolutional.

[Fiztex]

8 минут назад, St4rgun сказал:

Dear @BIGNEWY it seems that DLSS 4 Preset "J" is the second best thing after sliced bread, its quality is exceptional.

Unfortunately right now we can only "hack" this version into DCS by DLL changing and for another yuestion you replied that the devs will work on DLSS 4 only AFTER deploying Vulkan.

As it seems that the performance and quality of DLSS 4 even in its unofficial state is so massive, that it needs URGENT attention may I ask if this timing has been changed?

If your statement means that we're just mere weeks away from Vulkan, then it's OK, but if not, then IMHO the devs should really prioritize the full integration of DLSS 4 before anything else, it's so revolutional.

I'd be happy if ED just whitelisted all Nvidia signed dlls - no cheating like that possible and it's not like the game is super secured anyway.

[Silver_]

If you had to stay with a preset with which one would you stay with the J or K? Personally I keep the J, it seems to give me more contrast and focus although I was also going well with the E but with more ghosting.

Edited February 1 by Silver_

[Beirut]

If you're not that bright with the tech stuff and registry edits and whatever- and that would be me - is there any real advantage to going through the rigamarole of getting DLSS 4 working?

 

 

[Apache 64]

vor einer Stunde schrieb Silver_:

If you had to stay with a preset with which one would you stay with the J or K? Personally I keep the J, it seems to give me more contrast and focus although I was also going well with the E but with more ghosting.

I also prefer the J preset. Under certain circumstances, this gives me slightly better quality and less smear than the K preset. With K, e.g. rotor blades sometimes disappear when fly by far.

Edited February 1 by Apache 64

[johnbowzer]

Been following this thread and another one about DLSS4 and presets, like K. Might be worth checking this info I found on enabling it, which I did it. Waiting for comments on the other thread to see what others might find. Sure appears to make it much simpler.

 

[sleighzy]

1 hour ago, johnbowzer said:

Been following this thread and another one about DLSS4 and presets, like K. Might be worth checking this info I found on enabling it, which I did it. Waiting for comments on the other thread to see what others might find. Sure appears to make it much simpler.

 

Works fine for me, that is all that is needed. Don’t think some of that was known at the time…and also wouldn’t have been possible when people were testing this prior to the official driver release.

I still use DLSS Tweaks for the debug hud overlay as I already have installed so is more convenient and means less chance of messing stuff up when you start playing with registry keys. 

Edited February 1 by sleighzy

[slughead]

I just use DLSS tweaks. No registry mucking about. K.I.S.S.

[Mustang]

Found this interesting reddit post while doing a search, has some nice tech info (most we already know but still)

https://github.com/NVIDIAGameWorks/rtx-remix/issues/324

 

[5ephir0th]

11 hours ago, Mustang said:

Found this interesting reddit post while doing a search, has some nice tech info (most we already know but still)

https://github.com/NVIDIAGameWorks/rtx-remix/issues/324

 

You can do all thad (customize DLSS profiles multipliers, change the preset, enable the auto exposure, etc) with DLSStweaks

[slughead]

1 minute ago, 5ephir0th said:

You can do all thad (customize DLSS profiles multipliers, change the preset, enable the auto exposure, etc) with DLSStweaks

Exactly. There's no need to use anything else other than DLSSTWeaks. As I said above, K.I.S.S. (keep it simple, stupid).

[diamond26]

One thing that needs attention when using the Global preset option from DLSSTweaks is that it's also set the percentage for DLSS quality levels (I believe it defaults to Quality setting 0.666). That means you cannot then change it in DCS settings to anything else.

So either you also set the preset and the quality level up front or use the old method of adding the dxgi.dll in bin folder so you can make the changes of DLSS quality levels at DCS level.

In my use case (Qpro and QV, 3080 12GB) I ended up using preset J and performance in DCS with full resolution in Quest and focus resolution 1.8 and peripheral 0.2 in QV settings. Unbelievable how the system manages clarity and performance with no obvious artifacts! It's like a got a new GPU