I stick with older drivers and 100-150MHZ lower via NVI for my GTX1080TI FTW3 and it holds now even with FSL and shadows enabled and LOD maxed out

Michael Moe

Edited September 23, 20214 yr by Michael Moe

@MarkW, well done and I’m very pleased for you. I’m also very relieved as that was your last option really.

Now whilst you took the nuclear option I only updated the Client so it does suggest that route should also be safe. Who knows what went wrong.

Do you still have the TdrDelay setting in the Registry? What are your plans for that if it’s still present? I’m going to fly a 2-3hr flight today without that setting. I’ll report back in due course.

My first flight with TdrDelay deleted resulted in a DXGI_DEVICE_HUNG 40nm NW of Zurich on a flight from Manchester to Athens. The previous 10 or more with that Registry entry were fine.

I reinstated TdrDelay, rebooted and then reloaded the flight. I have every confidence in the flight being completed.

Conclusion? Problems remain with DX12 and only that setting prevents a DXGI error. I trust LM are working on this.

3 hours ago, Ray Proudfoot said:

@MarkW, well done and I’m very pleased for you. I’m also very relieved as that was your last option really.

Now whilst you took the nuclear option I only updated the Client so it does suggest that route should also be safe. Who knows what went wrong.

Do you still have the TdrDelay setting in the Registry? What are your plans for that if it’s still present? I’m going to fly a 2-3hr flight today without that setting. I’ll report back in due course.

Ray, yes I plan to keep the TdrDelay in place.  Looking at your issue once you deleted it, I suspect this is a wise choice.

Just to confirm, do you have TdrDelay = 0 @Ray Proudfoot?

3 hours ago, Ray Proudfoot said:

My first flight with TdrDelay deleted resulted in a DXGI_DEVICE_HUNG 40nm NW of Zurich on a flight from Manchester to Athens. The previous 10 or more with that Registry entry were fine.

I reinstated TdrDelay, rebooted and then reloaded the flight. I have every confidence in the flight being completed.

Conclusion? Problems remain with DX12 and only that setting prevents a DXGI error. I trust LM are working on this.

Very interesting! Do you think it is a combination of DX12 / Individual PC specs? I only have a lowly 1080 and after just one DXGI error after the update, I have had nothing.

When I put the Registry entry into my PC to see what would happen, it seemed to create more stutters. (Maybe coincidence).

On removing it, I have completed 4 flights of 11,8,4 and 12 hours duration without any problems.

Computers eh?

23 minutes ago, mobiel said:

Just to confirm, do you have TdrDelay = 0 @Ray Proudfoot?

Confirmed.

11 minutes ago, IanHarrison said:

Very interesting! Do you think it is a combination of DX12 / Individual PC specs? I only have a lowly 1080 and after just one DXGI error after the update, I have had nothing.

When I put the Registry entry into my PC to see what would happen, it seemed to create more stutters. (Maybe coincidence).

On removing it, I have completed 4 flights of 11,8,4 and 12 hours duration without any problems.

Computers eh?

Dunno Ian. Definitely DX12. Earlier DXGI errors were down to a bad Nvidia drivers later corrected. Yes, they drive you mad don't they?

4 hours ago, Ray Proudfoot said:

Conclusion? Problems remain with DX12 and only that setting prevents a DXGI error. I trust LM are working on this.

And I don't trust LM are working on this given their silence on the official forum. But I sure hope they do.

15 minutes ago, Afterburner said:

And I don't trust LM are working on this given their silence on the official forum. But I sure hope they do.

The thing is that there is a HUGE group of people who don't have this problem and have never had. And yes, clean reinstall solves most of the mysteries - I have learned it since V3. Moreover, nowadays with addone.xml method full reinstall doesn't consume massive amount of time as it used to. 

Edited September 23, 20214 yr by G-YMML1

1 hour ago, Afterburner said:

And I don't trust LM are working on this given their silence on the official forum. But I sure hope they do.

DirectX is a Microsoft package and Nvidia, AMD and LM attempt to make their software/  hardware compatible with it. How much LM can do is debatable.

1 hour ago, G-YMML1 said:

The thing is that there is a HUGE group of people who don't have this problem and have never had. And yes, clean reinstall solves most of the mysteries - I have learned it since V3. Moreover, nowadays with addone.xml method full reinstall doesn't consume massive amount of time as it used to. 

But the official advice from LM for updates is to install Client.msi. If they advised a full uninstall and reinstall for point updates you could understand if people had problems if they cut corners with just the client.msi. But I and others followed the official advice.

The trouble is they’re so uncommunicative it’s hard to get good advice.

11 minutes ago, Ray Proudfoot said:

But the official advice from LM for updates is to install Client.msi.

It's a legal nada-yada. It assumes that you have P3D installed without add-ones. LM has never officially endorsed any of the add-ones, so their conscience is clear in this situation.

12 minutes ago, G-YMML1 said:

It's a legal nada-yada. It assumes that you have P3D installed without add-ones. LM has never officially endorsed any of the add-ones, so their conscience is clear in this situation.

You know this for a fact do you? Or are you making an assumption too?

I’m curious how you know “there is a HUGE group of people who don't have this problem and have never had.”

Given the number who have ditched P3D for the other sim where would you get this info from?

After today’s DXGI “crash” it confirmed to me that the Registry fix to suppress the “false” DEVICE_HUNG message is mandatory until such time as the problem is fixed by whoever. Microsoft, Nvidia or LM.

I say false because there’s no indication of a problem with the graphics card. The very fact I can read the message displayed by a device that has apparently “hung” is both illogical and frustrating.

In all other respects P3Dv5.2 HF1 is stable and highly enjoyable. Nothing more to add really. An interesting exercise and at least there’s a fix. I shall continue my flights and keep my graphics drivers up to date.

Good for you that you have found a fix!  However, a working solution should not require digging into the depths of Windows registry and changing parameters that Windows itself doesn't recommend to do. This must be confusing especially for newcomers if they experience such error.

Neither Microsoft nor Nvidia tell us what actually happens "behind the scene" when the DXGI error occurs. As far as LM, there was a time during the v2, v3 and v4 era when they were actually more responsive (especially when Wesley Bard and Adam Breed worked there). Right now it feels like no one has an idea what they are working at - the weather with EA on is still bugged, and they leave those affected by the DXGI error totally in the cold. Nvidia doesn't seem to care either when you look at their forums (and that error happens with some other games as well).

32 minutes ago, Afterburner said:

Neither Microsoft nor Nvidia tell us what actually happens "behind the scene" when the DXGI error occurs.

Right now it feels like no one has an idea what they are working at - the weather with EA on is still bugged, and they leave those affected by the DXGI error totally in the cold.

Nvidia doesn't seem to care either when you look at their forums.

It’s certainly tempting to suggest that worthies like Ray, who are prepared to invest the time and effort on behalf of our community, are exposing gaps in their respective corporate armour. Customer Support is sorely lacking and they (Microsoft, Nvidia, LM) should be called out whenever such issues are identified.

Mike

Edited September 24, 20214 yr by Cruachan