No worries here and to be honest with any of the previous drivers and Nvidia Freestyle. I´m using just color and brightness/contrast. And DX11.
3060 Ti / 5600 X / Win 10
I have much lower fps, and more stutter (even with ok fps).
Did do the easy over-installation, but with the “clean” option.
Not sure if this really makes a difference…
Seems that CTD due to using freestyle filters is still not fixed then. Bummer…
I confirm that the new driver crashes the game with the Nvidia filter which is not really corrected, DX12 RTX4080
I have a suspicion. This worked for me in DX12. I wonder if the factor is… 3090? Or the use of TAA? Are all of you crashing with DLSS3? If so, then yes. It does work in DX12 just fine. It’s DLSS3 that doesn’t jive.
I find This is also possible without freestyle filter
For this purpose i use Nvidia Cpl desktop colouring, from here you can control brightness, contrast saturation and also tint colour and digital vibrance
With this last one u can really reach natural looks.
Also there is possible to use monitor own settings where many of these can be adjusted.
So in conjunction with these alternatives a lot can be done without use of freestyle.
Just sayin, If I timed this better that the menu wasn’t in the 1st pic, and you hadn’t seen the sim before… Hmmm. More reds, and orange coming out in the sunset vs purple. It would be enough for me to say bye bye fake frames, hello Filters
PS, if you set up resizable bar properly, and reflex + boost properly in dx11, that is a 10fps uplift for me. How many frames do you need? Mind you, my theory could be wrong. But, I don’t think so. With a few exceptions, no one is using DX12 except chasing DLSS3.
Doesn’t work, CTD,
DX12, RTX 4090, Nvidia Filetrs ON, HAGS ON:
Faulting application name: FlightSimulator.exe, version: 1.33.8.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx.dll, version: 31.0.15.3667, time stamp: 0x64af4006
Exception code: 0xc0000005
Fault offset: 0x000000000174cc77
Faulting process id: 0x0x519C
Faulting application start time: 0x0x1D9BA2ABEBC8934
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\system32\DriverStore\FileRepository\nvmdi.inf_amd64_6444f5939bb26330\nvwgf2umx.dll
Report Id: 596505b0-bfbb-41fb-b963-a7a5663314b6
Hags on, DLSS3 on I bet. I proved it works in DX12. Again, I’d bet DLSS3 is the culprit. It helps to narrow it down if you guys want it fixed. You’d know what to send a ticket against at Nvidia, if you so choose. This would involve testing with framegeneration off in dx12
EDIT: Try replacing your DLSS3 dll with the more recently updated one. Might be a fix, I can’t test. It certainly won’t hurt. I use the newest DLSS2 dll also at version 3.1.13, and have almost no ghosting in DLSS DLAA on glass cockpits. Keep a back-up of your old DLL’s.
DLSS3 blurry like always no mater wich version they update
Thank goodness, they are actually nailing this one with DLSS2. It keeps getting better. I’m trying to hold out for the rumoured 4090ti. I will for sure, be brute strength fps in DX11, even if I can’t wait and it becomes 4090
Well, just had a crash here a couple minutes after turning on filters, was working fine until then. DX12/RTX4080
You can use this on 30 series cards that don’t have FG, i.e. it will change DLSS 2 also even though it is called DLSS 3?
No sir, you can not. You can use this version of DLSS2 however. They did mess up a bit and make things difficult with their naming convention.
EDIT: This version of DLSS2 is by far the best to date. Very minimal ghosting on speedtapes in DLSS DLAA. Night and day to any previous release
Brilliant thank you, yes the naming is not ideal!
So…is HAGS rec’d to use again? Ive found that GameMode acutally is kind of good (especially when recording or streaming), try it yourself. =) But HAGS?
Thank you; so def not fixed. ARGH.
This is working great in VR with both my Quest Pro with Air Link and my wired OG Vive Pro1. HAGS and Game Mode both off and msfs with dx11 are working best for me (I did try them both on with dx12 btw). Very nice, smooth PCVR with my i913900k/rtx4090 thank you very much!
HAGS has to be on if you want to use frame generation. If this is no option, simply test if you get better results with HAGS on or off.
DX12 TAA + FG + Filters – CTD – nvwgf2umx.dll
DX12 TAA + Filters – all good
DX12 TAA + FG – all good
DX11 TAA + Filters – all good
Turn off frame generation.