Warning: Your graphics device has encountered a problem

Indeed, it would!

I certainly can’t, nor would I even try!
But I do assume and hope, at least, that there are development computers (AI) that have been fed most if not all the configuration possibilities and are hard at this task.

You’re a master of understatement!
:wink:
There are some folks who have lower thresholds of pain regarding the complexities of today’s technology. They see it as either it works or it’s broken, it’s on or off, black or white, or now or never.

I truly believe that despite all of our theories and testing based on our myopic personal experiences, we’re all just basically floundering around here trying to find that gold nugget.

For many of us, much of the fun is in the challenge and the hunt, so to speak. For others, not so much…

Patience is the key, though.

Had this error come up on DX11 for every flight post SU10 (no CTDs before SU10).

Changed to DX12, had about two weeks of smooth sailing but it just occurred again.

This is a serious bug which which kills any hope of flying (and wastes our time).

Switching to DX12 seemed to have helped but now the mouse scroll wheel stops working from time to time. And the view-look issue still hasn’t been fixed in over a YEAR AND A HALF.

I use to fly every SINGLE day, but I haven’t in about a week. It’s no longer enjoyable fighting thru these issues. This whole thing is turning into more of a mess than it’s worth.

pla

Sorry, haven’t been here in a while and I don’t think I answered you, but I did check that and that file is in that folder. Thanks for the suggestion!

I turned anti-aliasing back to TAA with otherwise optimized driver settings and have not gotten this error in a while (knocking on wood).

It’s one of like 37.2 fixes, I hate to keep broken record repeating but this is a catch all message with nothing or everything to do with what the words on the pop up say.

It might have been a video error a memory error a program error or operating system or internet, Ethernet or CPU but the program felt a little wuz zat?? and throws that up.

It’s truly frustrating as it’s none all and some causes always never and sometimes.

I did the same and also switched back to DX11 and it’s working much better. Not sure for how long but I’ll take what I can get at the moment and hope SU11 has a more permanent solution for us.

I am gettting this error now also, when i try to start the game. I dont get to the main menu, just the logo screens, and then the Safe Mode/Normal Mode option buttons. Neither works, it just CTD.
I just started the game an hour ago - i hadn’t started the game for about 4-5 months.
I did have custom 3D settings for the program as i have Oculus Quest2 VR, so had all the previous tweaks to optimize for that.
MSFS2020 (Steam) On Win10 Pro, GTX 3070, latest Nvidia drivers, DX12, no DLSS
Any quick fixes i should try? thx

I had this similar error today.

I switched to a new monitor (a 27" from a 24") and thought the native resolution was too high.
So reduced it, and MSFS was encountering such an error.
Going back to the native resolution eradicated the error.

Cheers,
Nish

So for you it seems to be the fps speed the “issue” (each machine have a different way to workaround this “moving” bug). Possibly try to lower your resolution like you wished first, and add some load on GPU like raising step by step Render Scale in MSFS settings.

Do you have the same issue if you follow the OP’s steps to reproduce it?

yes

Provide extra information to complete the original description of the issue:

Are you using DX12?

Are you using DLSS?

If relevant, provide additional screenshots/video:

I’m getting this problem every single time I fly with the Fenix at the moment. All my other aircraft work fine. PMDG, Aerosoft etc.

I’m on windows 11, running dx11 and nvdia studio drivers.

Spec is cpu 19 11900
Gpu rtx 3080 10gb
32gb ram.

for me it happens with PMDG too. in fact it happens with all airplanes. And at all flights. The only difference is the time for this error to occure. Sometimes in the menus, sometimes after 1h, sometimes after 10 mins… it’s really random on my PC. And it’s only appeared from SU10. I have not changed anything before that and the sim was running for hours before… i have tried all suggestions and workarounds. any works… I ca’nt fly from about 3 weeks

Do you have the same issue if you follow the OP’s steps to reproduce it?

yes

Provide extra information to complete the original description of the issue:

Are you using DX12?

no

Are you using DLSS?

no

If relevant, provide additional screenshots/video:

I’m worried that major bugs like this have still not been fixed in the current beta, and we’re two days away from release of SU11. If fears should come true on friday, it will give the impression that they are (once again) not interested enough in bugfixing. All you ever hear is "we’re adding this and that feature and look, even helicopters and gliders are included.
Can’t fly for weeks now and it starts to be annoying - not least because of the lack of communication.

Just for the records: Old driver 516.40 and switching back to DX11 and TAA doesn’t fix it.

Hello @snowrider349,

SU11 contains dozens of bug fixes, with many of them being requested by the community. You can see the beta patch notes (which do not include everything in the final SU11 release) linked below. Note that items marked with a :speech_balloon: icon are bug fixes or new features that were included specifically because of player feedback.

https://forums.flightsimulator.com/t/sim-update-11-beta-release-notes-1-29-22-0/548906

Thanks,
MSFS Team

2 Likes

@SeedyL3205 Thanks Seedy, that’s quite a lot of fixes :slight_smile:
However, we certainly agree that this is a showstopper bug that may have been introduced with SU10 and should be fixed as soon as possible, since a lot of users are affected.
I let myself be surprised and look forward to Friday.

I played on beta 11 for 15 days, and the bug is still there.
Another question: do you think that this bug - I only encounter it with MSFS - can damage our hardware?

Just a comment, “if you cannot find the bug then how do you know if it will affect hardware”. Asobo will fix the bug first and then we will, maybe, know.

My bug frequency was 1 in about 6 flights.
I switched back to driver 496.76 (quite ancient) and could do about 20 flights without the bug appearing.

Until today.
So 496.76 is not the perfect solution but it might be a good remedy.
I’ve now updated to the very latest Nvidia driver to see what happens.
It’s a very misterious bug and really really frustrating as it just terminates your flight.