Nvidia Driver 536.99

[jimcarrel 688]

9 hours ago, Virtual-Chris said:

I don’t know if it’s the driver the new beta sim build or both, but I don’t seem to be taking a hit on FPS when using a pop out panel on a second display.

I also set G-Sync to both Full Screen and Windowed (vs Full Screen only) so maybe that was the difference? Popping out a panel on a G-sync display definitely seems to create some issues with G-Sync, but moving it to my 2nd display seems to resolve any issues. 

Well, that must have been a welcome surprise! Those don't come along too often

[DANgerousFlyer 9]

My MSFS crashes with a DX12 error (says something like GPU overclocked, or a bug, or many other possibilities!) as soon as I get to the "fly now" screen. I tried with DX11 as well, same thing. I was able to reproduce the error every time by opening the same aiport at the same stand, using the Fenix A320.

I am on the beta build, and using the Fenix A320 with the latest v1.5 update. As soon as the Fenix app launches, or very shortly after, MSFS CTDs. I rolled back to 536.67 and I don't have the issue at all (again with latest Fenix update).

Admittedly I did not try it without using Fenix so I'm not sure if it's an incompatibility with Fenix or other addons. I didn't want to mess about so rolled back to last known good. YMMV of course.

[pmplayer 9,609]

536.99 works very well for me, better as my last driver ( not shure a 100% but i think it was 531.29 ? )

A couple more FPS, 3 or 4 now with a good smoothnes, to say i am NOT on the Beta !

cheers 😉

[Ixoye 1,837]

Driver 536.99 works just as good as the version before, I don't notice any difference at all.

[outermarker 237]

7 hours ago, DANgerousFlyer said:

My MSFS crashes with a DX12 error (says something like GPU overclocked, or a bug, or many other possibilities!) as soon as I get to the "fly now" screen. I tried with DX11 as well, same thing. I was able to reproduce the error every time by opening the same aiport at the same stand, using the Fenix A320.

I am on the beta build, and using the Fenix A320 with the latest v1.5 update. As soon as the Fenix app launches, or very shortly after, MSFS CTDs. I rolled back to 536.67 and I don't have the issue at all (again with latest Fenix update).

Admittedly I did not try it without using Fenix so I'm not sure if it's an incompatibility with Fenix or other addons. I didn't want to mess about so rolled back to last known good. YMMV of course.

I had lots of these crashes as well (not immediately but within a couple of minutes or when opening settings in flight) with the Fenix in DX12, SU13 beta. Now opted out of SU13b, switched to DX11 and have no issues anymore on 536.99.

Edited August 13, 2023 by OuterMarker

[Mets737 201]

No more issues with this driver!

I can finally run DX12 with FG on AND NVIDIA Game Filters!

Super stoked!

[Swe_Richard 1,175]

Had to go with this driver to play BG3. 
 

MSFS seems to be working perfectly fine, though. 

[DANgerousFlyer 9]

Maybe beta is the culprit for me... but if I opt out of it then I fear having to do a full re-install. Eek. Will stay as I am, it works well enough!

 

(sorry i tried to quote @OuterMarker above and failed, user error!)

Edited August 16, 2023 by DANgerousFlyer
Made a mistake

[rob0203 697]

I also had CTD with this driver, not on BETA 13. Also when flying Fenix. Now reverted back to earlier driver

[ndflieger 55]

The new drivers seem to be working fine for me. Not using Beta 13 and a 3080ti GPU. Have done flights in the Fenix A320 and Kuro B788, using the GeForce filters and haven't had any issues. 

Scott

[MrFuzzy 2,124]

Same here, smooth as silk since I opted out of SU13 beta.

[Alvega 2,125]

Just completed a 1 hour flight in the Comanche with this driver in DX12 and SU13 beta, not even one stutter.

[FlyIce 354]

Haven't flew for a while and just updated both MSFS2020 and Nvidia driver to 536.99 last night. Now every flight crashes within 10-20 minutes. Sometime I got the error "DGXI_ERROR_DEVICE_HUNG (0x887a0006)". 

Before I got CTD occasionally, but now it's a certainty for every flight. Really puzzling. I checked CPU and GPU and there were no over-heatings. Very frustrating. I flew only in VR with HP G2 goggle. 

[Sonosusto 696]

43 minutes ago, FlyIce said:

Haven't flew for a while and just updated both MSFS2020 and Nvidia driver to 536.99 last night. Now every flight crashes within 10-20 minutes. Sometime I got the error "DGXI_ERROR_DEVICE_HUNG (0x887a0006)". 

Before I got CTD occasionally, but now it's a certainty for every flight. Really puzzling. I checked CPU and GPU and there were no over-heatings. Very frustrating. I flew only in VR with HP G2 goggle. 

That sounds like GPU error. Maybe revert back to a previous/earlier driver.

[FlyIce 354]

I'll give rolling back driver a try. Apparently it's acknowledged by MSFS too on their website: 

https://flightsimulator.zendesk.com/hc/en-us/articles/6422969348508

They suggest version 531.29. Hopefully that'll solve the problem for the moment.