They are never ever ever ever ever ever ever going to put themselves into a position where they have to admit THEIR software is at fault. 

It's an American Company in the land of liability which deals with multi million dollar contracts. 

You think they are going to put their neck on the line and admit something is wrong. There not that stupid.

Sure they'll admit the bridge in EHAM on W10 is one thing, but the inner coding of the software creating dxgi errors is something they will NEVER  admit too. 

It baffles me as to why guys can't understand this.  

Edited September 24, 20214 yr by fluffyflops

9 minutes ago, fluffyflops said:

They are never ever ever ever ever ever ever going to put themselves into a position where they have to admit THEIR software is at fault. ...  Sure they'll admit the bridge in EHAM on W10 is one thing, but the inner coding of the software creating dxgi errors is something they will NEVER  admit too. 

Has anyone actually figured out whether it's code (and if it is, is it the app, the driver, or the OS) or an interaction with the hardware or power supply?

Cheers!

56 minutes ago, Afterburner said:

Good for you that you have found a fix! 

Well it seems I spoke too soon. I setup a flight from Bordeaux to Madrid and at 6,000ft paused the sim to have some lunch. When I returned 40 mins later the dreaded DXGI_HUNG message greeted me. Looking at my moving map software on a WideFS PC it froze at 10,000ft so just a minute or two after being paused.

Looking in Event Viewer I'm seeing a new warning message:-

Error 4109. Application Prepar3D.exe has been blocked from accessing Graphics hardware. But that message is timed at 13:12 - some 30 mins after paused the sim so seems strange.

I've reloaded the flight and expect it to continue without issue.

For those interested try pausing the sim and see what happens. If it does it consistently it should be helpful to LM.

I have multiple games installed running on DX12 and never, ever, had similar issues. LM´s lack of support here is evident and quite troubling. 

2 minutes ago, GCBraun said:

I have multiple games installed running on DX12 and never, ever, had similar issues. LM´s lack of support here is evident and quite troubling. 

All the more frustrating because according to the Ts&Cs we’re not entitled to support. The same applies to the Professional licence. That is pretty poor from a company with plenty of resources.

A few weeks back I reported taxiway signs on a taxiway at a default airport. Hardly crucial but it was responded to in a couple of hours.

But nothing from them when we need help.

1 hour ago, GCBraun said:

I have multiple games installed running on DX12 and never, ever, had similar issues.

That, of course, means there are no problems with other games and DX12.

The license clearly states P3D is NOT meant for entertainment purposes. This may be LM’s way of underscoring that fact.

 

Sherm

1 hour ago, Ray Proudfoot said:

All the more frustrating because according to the Ts&Cs we’re not entitled to support. The same applies to the Professional licence. That is pretty poor from a company with plenty of resources.

Given how consumer PCs have a variety of uncontrolled hardware and software combinations, usually assembled and updated by untrained amateurs, this is entirely understandable. I'm sure LM supports their commercial clients quite well, but the restrictions on hardware, software and change control would mean that 99.9999% of all consumers wouldn't qualify.

Cheers!

9 minutes ago, Luke said:

Given how consumer PCs have a variety of uncontrolled hardware and software combinations, usually assembled and updated by untrained amateurs, this is entirely understandable. I'm sure LM supports their commercial clients quite well, but the restrictions on hardware, software and change control would mean that 99.9999% of all consumers wouldn't qualify.

Cheers!

But I never had this problem until v5 and DX12. There must still be bugs in some software either in DX, NVidia drivers or P3Dv5. Some reported DXGI problems in v4 but not me.

Windows runs just fine and so did v4 with my flights around the world. God help those using MSFS when that goes to 12.

Anyway, I’ve installed the latest Nvidia - 472.12 Studio drivers. I’ve not had a DXGI issue in normal flight with the Registry hack so will leave that in and not pause any flights.

If I get problems I’ll start a new topic as this one is no longer appropriate given my driver update.

30 minutes ago, Ray Proudfoot said:

God help those using MSFS when that goes to 12.

Not sure the invocation of a Deity will be called for when we can be certain that Microsoft/Asobo will be all over this should their sacred cow be under threat...lol! All that is needed is sufficient incentive to divert resources and currently this issue does not qualify.

Mike

 

Just to conclude in this topic. I ran SFC yesterday and it did report corrupted file(s). Those were successfully repaired. Maybe that was a factor in the paused DXGI crash.

So for anyone having this issue run SFC /scannow.

18 hours ago, GCBraun said:

I have multiple games installed running on DX12 and never, ever, had similar issues. LM´s lack of support here is evident and quite troubling. 

 

19 hours ago, Luke said:

Has anyone actually figured out whether it's code (and if it is, is it the app, the driver, or the OS) or an interaction with the hardware or power supply?

Cheers!

remember when trueglass, real light came out,  it caused a DXGI ERROR.  it was patched and fixed,  so software error with that software and P3D

remember when the 747 first came out.  it caused a DXGI ERROR.  it was patched and fixed,  so software error with that software and P3D

remember with LGKO wiuth dyanmic lighting on in v5.0 + v5.1 it caused a DXGI ERROR.  it was patched and fixed,  so software error with that software and P3D

once again, it still baffles me as to why people think this is an ndviva issue and people are scanning driver files.  

once again let me remind you about the GSX northern canada issue that caused CTDs with bad BGL data,  2+ years to fix, and LM never once got involved, and it was proven their BGL data had empty entries which was causing it.

Heaven forbid them ever for putting their necks on the line and admitting it. 

LM im afriad, are not the white knights you lot think they are and unless you are one of their big military customers, it makes no business sense for them to help.  Bitter Pill im afriad, thats how it works.

 

Edited September 25, 20214 yr by fluffyflops

@fluffyflops your points are well made. However, in each case cited by you we have not been told what exactly was ‘patched and fixed’. Do we have actual evidence of code changes other than possible workarounds to circumvent this issue? It seems to me that the common factor is either embedded in the NVidia drivers or their interaction with Microsoft’s DX12. Unfortunately for us, action is unlikely as our combined voices are not loud enough to penetrate their respective support models.

Also, our relationship with LM seems very one-sided. They appear happy to ‘allow’ us to use their software knowing that gratuitous feedback from our community often helps them identify and troubleshoot issues which otherwise would hold back future development, and consequently threaten to undermine the all-important relationship with their military customers. Can this be regarded as being justifiable exploitation of those with little power or influence to push for policy changes? Or, should we simply button our lips and be thankful for what we are given...warts and all?

Mike

Edited September 25, 20214 yr by Cruachan

fluffyflops, you make the assumption that just because something was worked around means that the component that was modified was at fault.

Over the years in software, I've learned that if you want something resolved, you raise hell not with the source of the problem, but with the team most likely to fix it. In some cases that's the original team, but when they are unresponsive you find the people smart enough and positioned properly to work around the original problem.

Ironically that means that this second team can get blamed for the problem because people assume that since they were the only ones to change something and the problem went away, it was their component that had the issue in the first place.

Cheers!

On 9/13/2021 at 4:33 AM, Ray Proudfoot said:

The GPU isn't overclocked but the mobo is using Asus AI Suite III as recommended by @Pete Dowson. CPU running at 5.2 on 3 cores and 5.0 on the rest. Would that impact on the GPU?

Just had a second DXGI hang on my LAX-CYVR flight. 😞 I only seem to get them away from Europe. Australia and now USA.

That's your problem AI suite, It pretty much hosed my FS installs. I ended up dumping everything and reinstalling win10, then my simulators again. Have not had any issue since. I use AI overclock in the BIOS to over clock my system. Also been using 471.96 since release. No issues. I see there's a new release 472.12 but I think I'll stick with what's working.

Edited September 25, 20214 yr by Bigmack