1 hour ago, flyingpauls said:

I, like probably many others, get the error message below. CDT.

I updated the drivers already to my Geforce 1080 (516.94). I don't overclock, nor is it overheating. I also applied all available updates of MSFS. The plane was the default Cessna 172SP. In the graphics settings, I tried DX12 (Beta), which was set by default, and DX11. 

Any other ideas?

The driver that fixes the corrupt images in DX 12 is the newest NVidia Studio Driver.  The Game Ready driver from NVidia with the same fix for DX 12 has not been released yet.

You should probably use DX 11 (I am guessing you are on the Game Ready Driver).

Edited September 21, 20223 yr by abrams_tank

Yeah. Same here without changing any settings from before.

Great.

Also, VFR map isn't working: window appears but is never filled with anything.

it's the beta testers' fault!!

This is why the beta test forums need to be kept publicly visible - so when anyone complains that a bug wasn't found by testers the testers can post a link to the specific thread/post where they raise that exact bug.

Edited September 21, 20223 yr by Matchstick

4 minutes ago, abrams_tank said:

The driver that fixes the corrupt images in DX 12 is the newest NVidia Studio Driver.  The Game Ready driver from NVidia with the same fix for DX 12 has not been released yet.

You should probably use DX 11 (I am guessing you are on the Game Ready Driver).

So are we saying that if you are using DX11, your original driver, that bug pops up when you open MSFS?

Just now, Bobsk8 said:

So are we saying that if you are using DX11, your original driver, that bug pops up when you open MSFS?

It didn't pop up for me. I did a 30 minute flight though with a Cessna 172 G1000, at 1080p, on DX 11.  I will report back if I encounter this bug.

1 minute ago, Bobsk8 said:

So are we saying that if you are using DX11, your original driver, that bug pops up when you open MSFS?

Not when you open MSFS in my case. It happened about the time I reached the runway while flying the C172 Steam gage version.

Just now, RichieFly said:

Not when you open MSFS in my case. It happened about the time I reached the runway while flying the C172 Steam gage version.

Are you on DX11 or DX12?

 

11

Just now, RichieFly said:

11

Bummer, that means that could affect everyone. They have had weeks to get this SU out, why did they release it with a known bug?

1 minute ago, Bobsk8 said:

Bummer, that means that could affect everyone. They have had weeks to get this SU out, why did they release it with a known bug?

Yeah. This is quite disappointing. I've been holding off flying, waiting for this update and I get this. LOL

I've rebooted and now I'm installing the new Windows update and I've installed the new Nvidia Studio driver.

After a nap and some more coffee, I'll try it again...maybe.

Here is the thread over in the Microsoft forums discussing this error message:

https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem-again/543820/13

Here is a similar thread from the SU10 Beta discussing the same error:

https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/10

55 minutes ago, Bobsk8 said:

I guess the beta testers missed this.

Nope, I’ve had this issue right through the beta and reported it. I get this error when I try and pop out the atc menu in DX12. Doesn’t matter  which driver I use. 

4 minutes ago, Ianrivaldosmith said:

Nope, I’ve had this issue right through the beta and reported it. I get this error when I try and pop out the atc menu in DX12. Doesn’t matter  which driver I use. 

I just checked on the MSFS forum and there are over 300 posts on this issue. 

29 minutes ago, RichieFly said:

it's the beta testers' fault!!

It’s really a mess. Told them endless times like guys, RichieFly will have an empty VFR map so go fix it and guess what. Nothing. It’s a real pity.

1 minute ago, DAD said:

It’s really a mess. Told them endless times like guys, RichieFly will have an empty VFR map so go fix it and guess what. Nothing. It’s a real pity.

I think they are trying to do a good job, but when multiple testers report the same issue, and they just ignore it, that is just arrogance on their part. 

Edited September 21, 20223 yr by Bobsk8