Nope. I’m using it with a 4070ti
Hmm…been using Nvidia filters for long time with the driver 531.29. No problems.
Well if that is working for you keep using it but the Freestyle bug was introduced with the Video Super Resolution driver (531.18) which has yet to be fixed. You are using the driver after (I think) and I am using the driver before. Whatever works mate
Any one else using Win 11 Dev get a Nvidia update like me. 3 days ago I had a windows update for the video driver through Windows which now shows up as Driver version 535.50 in the Nvidia control panel. I have had no more CTDs so far. I have never had a update like this from windows before.
Just got the ‘Your graphics card encountered a problem’ error with the sim freezing with this driver. Never had issues so far with previous drivers. Reverting back to 531.29. Also removing the Ge Experience stuff, which I wanted to try for the filters (didn’t use them yet).
Same here, When I take off I Just get this GPU Error and a CTD.
Please report any errors to Nvidia using the Nvidia ‘feedback’ link that I have posted above. We still like to hear about users experience in these driver threads, especially when related to MSFS…
Cheers!
Charles.
Today make test , Change my settings all , downgrade .
DX12 to DX11 TAA and all HIGH and Medio settings no more 100 .
RTX 4090 windows 10 the new driver work well and with filters .
When change the same settings only DX11 to 12 give fast error overload .
My question is the driver or the game MSFS with DX12 is one beta version !!!
DX 12 is still in beta, someone correct me if I am wrong…
Glad you fixed your shader issue and the new Nvidia driver is now working well for you!
Charles
MISTAKE
Turn back to my old driver 531.29 , with this driver i can fly ultra settings with filter.
The new one after 2 fly get the same error overlock , DX11 High settings , the error give without Geforce Experencie install.
Lets wait for the new version MSFS2020 .
I never have one ctd, only now with the last 3 driver , and the same error overlock bla bla .
Is not come from the filter is the driver not good for MSFS
Hi Hacklier,
I do think the driver is suitable with MSFS, (as with all of these situations) some people have problems and it’s difficult to put a direct finger on the cause because there are so many variables at play in the individuals PC/software operating environment . This can make a definitive diagnosis very difficult. Sometimes it’s obvious what is causing the fault based upon great numbers of people reporting the same issue. Unfortunately, at the moment I am not seeing large numbers of people reporting the same issue. In my case, there have been no issues with any Nvidia driver for quite a long time. I am using an older GPU and don’t use GFX, this is why it is important for people to take a few moments and report their issues to Nvidia, if MSFS related, to ZenDesk.
Wish you all the best.
Charles.
Blockquote
Unfortunately, at the moment I am not seeing large numbers of people reporting the same issue. In my case, there have been no issues with any Nvidia driver for quite a long time.
Blockquote
Check that ![]()
FILTERS
Hacklier,
You are not on the same page as I am, the main issue brought to the fore in this thread relates specifically to filters being applied that cause errors within MSFS. I am well aware of the other issue where a warning appears which from within MSFS that ‘Your graphics device has encountered a problem’, that’s a problem that has been reported for a long time now. I have had that very same warning and I DO NOT USE FILTERS. I say again, I do not see a large number of posts that attribute filters to CTD’s etc, this may be related to a specific model of a GPU.
Please read the forum carefully and please do not use, (select parts) my posts to quote me out of context, if you have unequivocal proof that both issues are related, (if you know more than than us) please say so and let us know why you think they are both related, otherwise report the problem to ZenDesk and use the Nvidia feedback form.
Please read the thread below, let them know if you think, (in the context of filter use, if you actually believe there is a connection) the problem is due to filters, this might help them…
THERE IS NOTHING JUMPING OUT AT ME IN THE THREAD LINKED ABOVE, THAT SUGGESTS FILTERS ARE THE CAUSE OF THE ISSUE BEING REPORTED IN THAT THREAD
All the best…
Charles.
I unistalled 531.29 using DDU. It had been running well for me. I use vSync capped at 50% of my 165Hz monitor refresh. RTX 3090 Ti, AMD 5800X3D, DX11, DLSS - Quality.
Cleared the DX Shader cache.
I installed the Game-Ready 531.68 driver from the nVidia website, and included GeForce Experience (which I’ve never done before, but I wanted to test Freestyle filters.)
Total disaster. Massive stutters, sometimes dropping to 5 FPS during menu load
And panning around the aircraft was a stutterfest as well.
I uninstalled 531.68 using DDU, then reinstalled the clean 531.29 driver. Back to normal - smooth 80 FPS. I then installed GeForce Experience separately and played around with the filters. So far no issues. Everything looks buttery smooth at 80 FPS, and my GPU load is around 20% in menu, and 70% while flying. I posted in another thread about high GPU load (95%) in menu, but I think the latest sim update resolved that. If I turned Vsync OFF and let the frame limit OFF, I was getting >100 FPS, but my GPU load was 99%. I’ll be happy with a smooth 80 FPS. Of course this is over terrain. Cities will be lower… BTW, Dev Mode is on.
We’ll see how it goes. If I start having issues I’ll look into Reshade. But I don’t think I’ll be migrating away from 531.29 for a good long while.
Just submitted.
I would have uninstalled the 531.68 and then reinstalled it for a second time. This often works for me, I have been known to install the same driver three times! When you delete shaders, you will get stuttering as the shader cache rebuilds, that’s what I have been lead to understand. I likely would have also given the driver and system a little more time. I would not have expected frame-rate drops to 5PS, I think that really does sound like a disaster for you. Pleased you found a combination that works for you. ![]()
I have just bought the Asobo ATR, WOW it’s terrific!
All the best!
Charles
Maybe I’m reading your response incorrectly, but I’m genuinley curious as how it could be a problem for “them” specifically, when so many users all appear to be having the same problem at the same time?
I’ve heard that as well. But I always delete the DX Shader Cache whenever I install a new driver. Never had a problem. Maybe a few unusual stutters here and there for a little while. But nothing like what I experienced.
Reshade also has a problem if you use it at the same time as Afterburner. I discovered this last summer when I tried it. Totally random crashes. It is why I started using the filters instead.
Apparently it doesn’t happen to everyone but it is (or was then) a known problem.
Thanks. I do have Afterburner running… ![]()