3 hours ago, cobalt said:

I use an Nvidia GPU, and DX11. The fact that in 2 1/2 years of MSFS I never saw this graphics error until SU12, and now I see it repeatedly regardless of settings, add-ons, drivers, or anything else, is what convinces me that SU12 is the culprit.

As I said several days ago:  I had this problem frequently in early fall 2022.  Tried all the suggestions found here and the problem continued intermittently.  I finally gave up fixing it and accepted the CTDs at which time the problem stopped and I have not had a CTD/graphics error in the last three months.  I fly several hours a day about 25-days a month.

Edited April 6, 20233 yr by TacomaSailor

I am happy for you, but the fact is that for many of us the problem, which started with SU12, persists and seems unlikely to go away until a fix is provided by Asobo.

30 minutes ago, cobalt said:

I am happy for you, but the fact is that for many of us the problem, which started with SU12, persists and seems unlikely to go away until a fix is provided by Asobo.

Fix....

Just like the texture bleed in DX12 when switching view ?
Bandwidth errors ?
etc.

They don't care

Edited April 6, 20233 yr by altenae

3 hours ago, altenae said:

Fix....

Just like the texture bleed in DX12 when switching view ?
Bandwidth errors ?
etc.

They don't care

It could be that fixing something broken for users who already paid for the product has a lower priority than adding new features and bling for would-be buyers.

4 hours ago, cobalt said:

I am happy for you, but the fact is that for many of us the problem, which started with SU12, persists and seems unlikely to go away until a fix is provided by Asobo.

My point is that the problem started, at least for me, prior to SU 12 so looking for a cause in SU12 may be counterproductive to finding a solution.

2 minutes ago, TacomaSailor said:

My point is that the problem started, at least for me, prior to SU 12 so looking for a cause in SU12 may be counterproductive to finding a solution.

But how would one explain why many others (example: me) are experiencing graphics errors for the first time after SU 12?

Su12 has been plagued with issues for me 

Scenery textures not being sharp washed out 

even with the user.cfg post processing film grain and a few other settings been set to 0.

stutters on approach also which I did not have in su11.

 

mike

I got this crash for the first time ever yesterday, about 10 minutes in the Black Square Baron flight.

There is a new NVIDIA Gforce Driver release 531.61 
Did this resolve your problems? I just downloaded it and will try...

latest 531.61 driver didn't fixed the problem, this is a Sim issue since 09/2022 till now ...

https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/2467?page=16

in my case , reverted 531.29 driver and works fine..(finger crossed), its a very strange bug...

I have the 531.29 driver installed and still get occasional "graphics error" crashes. I really don't think this is a driver issue.

On 3/31/2023 at 5:30 AM, polosim said:

“ …. 

Hello everyone,

In talking with Asobo, they have informed us that this message is triggered when memory consumption is too high for your particular system. Before, you would just get a CTD or freeze with no error message. Suggested solutions if you are regularly getting this message are one or more of the following:

Reduce graphical quality settings (e.g. from High to Medium)

Reduce LOD sliders

Remove addons that could be causing this error

We agree that the message is a bit vague and unclear. We have submitted feedback to the devs to change the text of this error message so it better describes the cause.

Thanks,
MSFS Team

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

This message is only triggered when you use  the Nvidia .31 drivers (from a a couple of weeks ago) or higher. Just a heads up. Revert to the .29 driver and the message will not appear.

7 hours ago, techman said:

Just a heads up. Revert to the .29 driver

thanks for heads up, 

On 4/6/2023 at 6:29 PM, bofhlusr said:

But how would one explain why many others (example: me) are experiencing graphics errors for the first time after SU 12?

Same here.  I never had this issue until SU12, and I use MSFS heavily almost on a daily basis.

Dennis

13 hours ago, techman said:

This message is only triggered when you use  the Nvidia .31 drivers (from a a couple of weeks ago) or higher. Just a heads up. Revert to the .29 driver and the message will not appear.

Sorry, just not true. I reverted to 531.29 and still get this error message.