16 minutes ago, Ray Proudfoot said:

Yes. I need to prove to myself it was a corrupt file. The TdrDelay=0 setting could be preventing the message from appearing and given it’s a non-standard setting there’s no real need for it to be present. If things are fine without it there’s the proof. 👍

Don’t you find it strange there’s been virtually no discussion about these DirectX Shader files? Given the importance of clearing the standard shaders folder with a driver update I’m perplexed why something that seems associated with DX12 doesn’t get a mention including no mention of it in the LM FAQ.

in addition, if this is really the cause, why has it not come up before, so many people have the issue.  By the way Ray, Speedbird is on the ramp at EGLL, setting up for departure.  I should be in the air shortly.  Will report in a few hours.....

9 minutes ago, MarkW said:

in addition, if this is really the cause, why has it not come up before, so many people have the issue. 

It took me quite a bit of googling to find an association with DirectX Shaders. That seemed the crucial link. Hard to say Mark.

On some of my flights the problem occurred within 15 mins. On others it was over 30 mins. I’d love to know what triggers it because it’s not location-based. A  reload of a saved flight proves that.

I find it strange that there has been almost no discussion about the registry trick that you found on the FSL forum and also about the DX shader files. I find the lack of a statement by LM on the DXGI error disappointing. If you check out all threads on the official forum related to this error, you will hardly find any responses by LM employees. On the other hand, LM can only address errors that are reproducible, which in case of the DXGI error is hard to do. Some users experience this error with high GPU load, some (like you did) get it during cruise altitude with low GPU load. Add to this the observation that this error happens more frequently with PMDG planes than with default ones. (And LM may argue that they cannot be blamed if such error doesn't pop up with their default airplanes).

Personally, when I had this error, it was with PMDG 777 (and just once with Majestic Dash-8) at detailed airports after having landed and parked. I rolled back an older driver from fall 2020 recently (with which I can't remember having experienced this error - it's the driver 452.06), and I also deleted the DX cache, as you did (while leaving "Max Performance" in NCP). So far no errors.

1 hour ago, Afterburner said:

I find it strange that there has been almost no discussion about the registry trick that you found on the FSL forum and also about the DX shader files. I find the lack of a statement by LM on the DXGI error disappointing. If you check out all threads on the official forum related to this error, you will hardly find any responses by LM employees.

There are times when the lack of response from LM staff disgusts me and I don’t use words like that often. I asked them a few days ago about the DX Shaders contents and they can’t be bothered to reply.

They'd better be careful because even loyal customers have a limit. They provide a forum for discussion but rarely help customers preferring to leave it to a few volunteers who are not LM employees. And there is no formal process to raise a ticket should the volunteers be unable to help.

1 hour ago, Afterburner said:

On the other hand, LM can only address errors that are reproducible, which in case of the DXGI error is hard to do

Agreed but only they know what the purpose of the Dx Shaders folder is and the info that is written to it. They trap the Windows error and display their own “useless” message. I say useless because the Continue option doesn’t work so you’re left with Hobson’s Choice - exit.

They could be a lot more proactive with us especially when so much effort has gone in to identifying the issue. I get the impression they don’t really care.

No news from Mark is good news. Fingers crossed.

....back to the drawing board.  I got the error 1 hour and 45 min into the flight.  Just to review what was done in preparation for this flight.

1) Updated Nvidia driver (actually a new one came out this week, its the one before that).  Ran and clean install.

2) NVI on Prefer High Performance in the General tab, nothing in the game specific tab and no other options selected.

3) Cleared out the P3D shaders

4) Checked Directx was up to date.

5) Updated all drivers on my computer and installed all windows updates and other Microsoft product updates.

6) removed the Directx temp flies and restarted the computer (several times) and checked the Appdata location to ensure clear.

I am out of ideas, I will say I had a lot of issues when updating to P3D 5.2.  Lots of sim errors and I ended up deleting the Generated Files.  Only last option is to try and completely uninstall P3D and reinstall the full download rather than component installers.  Is there a guide on how to do this and still save my addons...they are all in another folder linked using XML.

@MarkW, that’s disappointing. I had high hopes it would be fine for you.

If you’re running 471.96 they’re the same as mine. I haven’t bothered with the latest.

Not sure what you mean by checked DirectX was up to date.

I agree a full reinstall of v5.2HF1 sounds wise. The executable should be available in your LM account.

I’d make copies of add-on.xml in appdata\roaming\LM\P3Dv5 as well as the one in ProgramData\LM\P3Dv5.

Also copy Prepar3D.cfg, Scenery.cfg. I’m struggling to remember any other files.

If you have Lorby’s Addon Organizer that can backup all critical files so they can be restored easily.

If you’ve had many issues then another install should fix them. Annoying I know but it’s probably your last option. Good luck.

1 hour ago, MarkW said:

....back to the drawing board.  I got the error 1 hour and 45 min into the flight.  Just to review what was done in preparation for this flight.

1) Updated Nvidia driver (actually a new one came out this week, its the one before that).  Ran and clean install.

2) NVI on Prefer High Performance in the General tab, nothing in the game specific tab and no other options selected.

3) Cleared out the P3D shaders

4) Checked Directx was up to date.

5) Updated all drivers on my computer and installed all windows updates and other Microsoft product updates.

6) removed the Directx temp flies and restarted the computer (several times) and checked the Appdata location to ensure clear.

I am out of ideas, I will say I had a lot of issues when updating to P3D 5.2.  Lots of sim errors and I ended up deleting the Generated Files.  Only last option is to try and completely uninstall P3D and reinstall the full download rather than component installers.  Is there a guide on how to do this and still save my addons...they are all in another folder linked using XML.

I get the evil Hung when set to High Performance.  Try optimum.

6 hours ago, Dreamflight767 said:

I get the evil Hung when set to High Performance.  Try optimum.

If the solution was as simple as that it would be easily solvable. I have Prefer Max Performance and no issues.

Thanks Ray, I will backup those files and go through a full re-install.  As for Directx, I just checked that it was up to date using dxdiag command, in the old days I think the update was manual but now part of Windows updates so all good.

Good luck Mark. There must be a problem somewhere because that Registry setting should disable the DXGI warning and it didn’t.

All your scenery can remain where it is outside of the core install and restoring the add-on.xml should bring it back just fine.

14 hours ago, Ray Proudfoot said:

There are times when the lack of response from LM staff disgusts me and I don’t use words like that often. I asked them a few days ago about the DX Shaders contents and they can’t be bothered to reply.

They could be a lot more proactive with us especially when so much effort has gone in to identifying the issue. I get the impression they don’t really care.

 

ive been saying this for years, yet people on here seem to think they walk on water.   

why people seem to have so much love for a defense contractor (amongst many others) that has caused misery to countless peoples lives in the world over the last 30+ years is beyond me.  its too bitter a pill for most people to swallow I guess.

like alot of companies in this flightsim game, they simply coudlnt give a toss.

I did some flights yesterday out of aerosofts geneva yesterday, still to this day 2+ years on from the release of GVA they cant be bother to fix the afcad for the correct ils or even runway... its a 5 minute job at most

today Im flying the a330, which to this day they still havent touched the connected flightdeck and it still wont work with EA clouds on properly.

They recently released Olbia for xp11,  they have air italy static a/c sitting on the stands.  Ait Italy, went bust last year.

a simple job of removing them from the xml placements file.  once again a 5 minute job.  To a trained eye they would of seen that before just hasitily releasing it.

If any of those products,  GVA, A330, OLB  had of been "my work"  I wouldnt be able to sleep at night knowing that a quick little polish up was all that was needed.

An hours work at most,I just couldnt, and wouldnt be able to put out some work which was shoddy like aerosoft and a load of orbxs products are.

It would drive me nuts, Id feel embrassed to pass it off as mine

its a cancer that is rife in this community,  half baked products that get passed off as finished.   yet people dont mention it, nor complain.

you reep what you sow in life,  if you think LM are suddenly going to stop what they are focusing on to fixed issues for simmers, you are very wrong.  we are chicken feed to what they are upto in the world

 

 

 

 

Edited September 22, 20214 yr by fluffyflops

@fluffyflops, 3rd party airport support is down to the developer. I’ve learned through experience some are better than others at keeping their products up to date. Aerosoft are a shop, not a developer. I’ve shown them a problem with an AFD for EGLL and it was never fixed. I sorted it myself.

I don’t want this discussion going off topic. If LM won’t respond so be it. I suspect for those having this DXGI problem a reinstall should fix things. I have proved the problem can be fixed with another flight this morning. That’s around 10 now without any issues.

And a pre-dawn departure from SAN Diego up to Las Vegas was a rare nighttime flight for me. No issues and I left the DirectX Shaders cache alone.

Tomorrow I’m going to remove TdrDelay from the Registry.

Success!!!

So I uninstalled P3D completely, deactivated it and deleted all of the folders (Program Data, AppData and the main P3D folder).  Before I did this I also uninstalled all of my Orbx products (Base, Vector, LC, regions and airports).  I did this because I had moved Orbx files from within P3D to the Addons directory just before the 5.2 update and thought maybe something got corrupted during this process.  I also uninstalled the FSL Airbus completely as this was the aircraft I was flying during all of the DXGI errors.

After reinstall, I reactivated all of the scenery that P3D found, which was most of my addon airports..I did not replace my backed up add-ons cfg file.  I reinstalled Orbx into the Addons directory and reinstalled the FSL airbus.

Flew EGLL - LSGA (4 hours 5 min flight) in the A320 and landed without the error (first time in about 10 tries).  As you can imagine I am quite relieved and hopefully this is now permanently fixed.  I really had a terrible update to 5.2 with many errors and issues.  Probably something was corrupted during the component update (something that had never occurred to me before.... all the way back to P3D v3) and it required a full reinstall to fix it.  

Thanks to all on this thread (especially Ray) for trying to help me sort this out.

3 hours ago, MarkW said:

Success!!!

This is encouraging news!  A fresh installation after having deleted all of the folders and generated files can be really helpful in driving out the gremlins inside the computer system that are responsible for different kinds of odd errors. I am pulling my thumbs that the success will last for you!