I just don't get it, good performance on take off but every time I go to land, the scenery doesn't load and then as I get close to the ground this word not allowed again.

Settings don't seem to matter.  I don't know if this is a GSX or AIG or just too much stuff loaded and graphics settings too high with a complex airplane.

I think I will wait and see if things improve with SU11.  Any one found the real solution to this?

I have not run into this particular message.  However, I suspect that others have and likely the first set of questions you'll get are:

1. What CPU?

2. What graphics card?

3. What video driver?

4. What scenery?

5. What volume of injected aircraft from AIG are you using?

6. Or are you on Vatsim?

7. Does the same thing with vanilla settings (i.e. community folder is empty).

8. If settings don't matter, what settings have you tried?

Errors like these may have many culprits.  

Finally, see post #11 in this thread.  https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/11

Edit .. deleted ... 

Edited November 3, 20223 yr by Maxis

I hate that message. I saw it a couple of times in SU10 beta and then the release version... for a little while. Then it went away. I saw it twice last week in Su11 (both times in the menus before starting the flight), and it hasn't come back since.

Whatever the problem really is, it has nothing at all to do with a problem with your HW.

There's another one saying that a breakpoint was reached and that memory could not be read with a target address of all zeros. There shouldn't be break points in a release build as they are for debugging, and trying to read memory at address zero is usually the result of accessing memory via pointer that has been initialized,  but never assigned a proper value. These just went away on their own, too.

Growing pains.

Edited November 3, 20223 yr by MDFlier

Yeah, I have tried everything.. the only thing that works is to revert to an old 471.XX driver but that has consequences with other games.  I just don't understand how they have so many new drivers but the only ones that work are 471.XX.

What really does not make sense is sometimes it works fine and sometimes it doesn't.  I really think a lot of these issues have to do with server loads.  The HAGS fix help a little.

I only had it happen once about 2 weeks ago. I just restarted PC, and it never happened again.

\

Try running the same flight without AI traffic. 

It's a known bug. I think it's listed as a bug in the Nvidia drivers that still hasn't been fixed.

I've had it twice after I installed SU10, then it went away. I didn't change anything.

I had it a few times in succession about a month ago.  I haven't seen it in ages and I am switching between DX11 and DX12 in SU11 beta.  I am on the latest Nvidia drivers (522.25).

Edit:  I just found out there are newer drivers, but I am sticking with these as there is no mention of MSFS in the newer version release notes, and my current set are stable.

Aniiran, you should consider yourself lucky.  At least you can take off and have some sort of flight.  I can't do anything.  

Prior to SU10 I had that message two or three times.  When you consider how often I flew in MSFS (most days) it was a very low percentage of flights.  Back in Sept, I downloaded SU10, opened the flight sim and all was good. However, the next day when I opened the sim I got that message and have ever since.  I get it every time, either during the loading stages, or on the opening screen.  I haven't flown in MSFS since I downloaded and installed SU10.  I'm certainly going through withdrawals.  I'm living in hope that SU11, which is due in a week or so, will fix this problem. 

Yes, my computer is all up to date and I've done all the checks with the community folder and other addons, but none appear to cause this message.        

 

Bruce R

i9-9900K @ 3.6GHz, 32 RAM, GeForce RTX 2028Ti

8 minutes ago, Meeko said:

...

Yes, my computer is all up to date and I've done all the checks with the community folder and other addons, but none appear to cause this message.        

Bruce R

i9-9900K @ 3.6GHz, 32 RAM, GeForce RTX 2028Ti

Frustrating I know.  It definitely isn't any addons. 

It is either MSFS or the drivers or an interaction between the two.  Like I say, my issue has disappeared now in SU11 beta, so maybe try SU11 when it downloads next week with the 522.25 drivers I am using, or the even newer ones. 

They have been fixing lots of bugs as they go in the beta. 

I have had to stick with DX 11 and TAA or I get CTDs and all sorts of random errors but I am not sure I ever got that particular message (RTX 3070).

2 minutes ago, bobcat999 said:

so maybe try SU11

 

Yes, I have my fingers crossed for this update. 

Delete the shader cache in Windows, and all other cache files in all MSFS directories (google for a list of MSFS cache directories). Reset your page file, you can set it to zero, let it delete, then recreate it. Reboot, try again.

You can also try switching back and forth between DX 11 and 12 a few times, see if that helps...

If didn't work, DDU and reinstall the video driver. If still not working, reinstall MSFS. If that doesn't work, no idea.

I do not think breakpoints are compiled in C++, it does insert an opcode but this is reversed in modern compilers once the output is compiled, unless you explicitly change the compilation style to use a non-standard parameter. That said, if the code you are debugging needs to access very large memory sets, the rules can change and sometimes I believe there are a few situations you could accidentally alter the compiled code (but still not with a standard breakpoint). It is however possible they accidentally deployed a debug version of something, but even that isn't likely to cause this problem.
 

Edited November 4, 20223 yr by Alpine Scenery

Thank you "AS" for your import.  Hope this will be of interest to Aniiran as well.  

I have already rolled back to previous video drivers with no luck and reinstalled the latest version.  Cache directories have already been cleaned with the exception of the scenery cache within MSFS.  I'm not able to get into MSFS to do that.  The resetting of the page file is a bit daunting, so I don't have the confidence to go there.  Lastly, reinstalling MSFS doesn't appear to make any difference.  MSFS forum indicates here's a huge number of MSFS pilots who have the same problem.  A lot of these pilots have reinstalled MSFS but it doesn't fix the problem.    

I think I'm doomed to wait another week or so for SU11 and hope that's going to be the magic cure.  In the meantime, it's back to YouTube videos.

Regards.