4 minutes ago, mpo910 said:

But go to LM site and post over there. That should bring more attention at it. 

...but that's the problem some of us are trying to point out... LM has mostly stopped communicating on the public section of their forum. I can post Event Logs all day and I have no idea if it matters.

10 minutes ago, johncott said:

in this case is LM the problem or your computer?

 

You must have missed the memo that all issues with everything in life are now LM's fault post V5 release....no way it could be a faulty add on, mismatched hardware, the random cocktail of programs or the infinite variety of setups....it is always someone else's fault...😉 

Besides, as a lazy person I feel I have been maligned and disenfranchised on this thread. How about some tolerance and understanding for the lazy. We have feelings too you know.🙅

4 hours ago, JoeFackel said:

Oh boy ... we will see MANY which will still have CTDs after installing HF2 i'm afraid.

That's because, no matter how many times those people are told to not use oppressive settings (and that includes OCing) on an obviously overtaxed system (partially the user's fault and partially LM's), those same people will suffer CTDs.

35 minutes ago, jabloomf1230 said:

That's because, no matter how many times those people are told to not use oppressive settings (and that includes OCing) on an obviously overtaxed system (partially the user's fault and partially LM's), those same people will suffer CTDs.

Sounds like you’re unaware that the sim has CTD issues even if you do everything right: stock settings, compatible add-ons, adequate hardware, etc. But now you’ve learned something new today! Glad I could help. 

Edited June 11, 20205 yr by Chapstick

28 minutes ago, Chapstick said:

Sounds like you’re unaware that the sim has CTD issues even if you do everything right: stock settings, compatible add-ons, adequate hardware, etc. But now you’ve learned something new today! Glad I could help. 

i don't agree with this statement in any way.  Like I said earlier.  I had a handful of CTD's that were all related to not having the right distributables to go along with gsx.  So i would request a pushback and maybe 1 out of 10 or 1 out of 15 would immediately CTD.  Other than that I NEVER get CTD's with V5.  I'm flying the 787, 767, 747, A330,MD80.  Around 50 addon sceneries.  I don't have stock settings, but I also don't max everything out.  I'm running with a resolution locked to 30hz when I use V5 which probably helps alot with that.  9700k and 1080ti.  I get that many are having problems but I fly airline flights very often.  Very often.  If I was having even occasional CTD's there is no way I would continue using V5 exclusively like I am.  That would be infuriating.  

5 hours ago, Chapstick said:

...but that's the problem some of us are trying to point out... LM has mostly stopped communicating on the public section of their forum. I can post Event Logs all day and I have no idea if it matters.

O come on. They did communicate (HF2 couple of weeks). But they did not state want you obviously wanted to hear (Fix release date). 

The fact we now do have a 64 bit, new rendering engine and volumetric clouds AND multicore sim does prove enough they know what they are doing. 

Reduce your expectations about YOUR need to chat with them and do what you HAVE to do if you want your problems become addressed: Post your detailed issues with appropriate mediums and outcome on their SUPPORT forum. They DO read them. Be sure of that.

 

Like I wrote it several times :

The stability of your hardware in combination with the stability of your software makes the stability of your system.

That is why some have issues and others don’t...

Being able to run good benchmarktests and other games without issues, may be not good enough to run Fs without issues.

- - - 

Example : two days ago I updated my Nvidia drivers from 442.92 ( studio driver ) to 446.14 ( game ready driver ) on both pc’s.

Yesterday I wanted to do a flight. When adding Live Traffic I got the DXGI Device Hung error on my left view client (2080).

I tried lower settings, dialed back the OC a little but the error returned when adding Live Traffic.

So I went back to 442.92 and everything is working fine again like before ....

Edited June 11, 20205 yr by GSalden

4 hours ago, micstatic said:

i don't agree with this statement in any way.  Like I said earlier.  I had a handful of CTD's that were all related to not having the right distributables to go along with gsx.  So i would request a pushback and maybe 1 out of 10 or 1 out of 15 would immediately CTD.  Other than that I NEVER get CTD's with V5.  I'm flying the 787, 767, 747, A330,MD80.  Around 50 addon sceneries.  I don't have stock settings, but I also don't max everything out.  I'm running with a resolution locked to 30hz when I use V5 which probably helps alot with that.  9700k and 1080ti.  I get that many are having problems but I fly airline flights very often.  Very often.  If I was having even occasional CTD's there is no way I would continue using V5 exclusively like I am.  That would be infuriating.  

Congrats 

1 hour ago, GSalden said:

Example : two days ago I updated my Nvidia drivers from 442.92 ( studio driver ) to 446.14 ( game ready driver ) on both pc’s.

Yesterday I wanted to do a flight. When adding Live Traffic I got the DXGI Device Hung error on my left view client (2080).

I tried lower settings, dialed back the OC a little but the error returned when adding Live Traffic.

So I went back to 442.92 and everything is working fine again like before ....

What’s this suppose to prove? That sounds like the crappy experience many of us are having. LM tells users to use the latest drivers, but they don’t work correctly? Looks like they’ve got some work to do.

19 minutes ago, Chapstick said:

What’s this suppose to prove? That sounds like the crappy experience many of us are having. LM tells users to use the latest drivers, but they don’t work correctly? Looks like they’ve got some work to do.

Indeed they do . Buggy it is , 

Stock settings with EVGA GTX1080TI -reduced factory OC by 100MHZ on normal settings in the Maddogx with win 10 2004 , resulted in a "DXGI error"  at EGLL yesterday with 1024 textures.

Fslabs Beta tester quote "Currently just hell so it's halfway there." (regarding "hell of a sim :read:potentiel)

 

Michael Moe

3 hours ago, GSalden said:

Like I wrote it several times :

The stability of your hardware in combination with the stability of your software makes the stability of your system.

That is why some have issues and others don’t...

Being able to run good benchmarktests and other games without issues, may be not good enough to run Fs without issues.

- - - 

Example : two days ago I updated my Nvidia drivers from 442.92 ( studio driver ) to 446.14 ( game ready driver ) on both pc’s.

Yesterday I wanted to do a flight. When adding Live Traffic I got the DXGI Device Hung error on my left view client (2080).

I tried lower settings, dialed back the OC a little but the error returned when adding Live Traffic.

So I went back to 442.92 and everything is working fine again like before ....

Thanks for sharing your experience with P3D V5.

This is exactly the experience I do not want to have and why I happily stay with P3D 4.5 for the time being. I never had a CTD with 4.5 and I don't see any thread an avsim about widespread CTD-issues of users of 4.5. So apparently it is possible to have a stable P3D even with all the different software-hardware-combinations. Just P3D V5 seemingly is not, so far.

Edited June 11, 20205 yr by RALF9636

What you need to do when you have updated the driver is Restore/Apply in NCP, even if you did nothing before. So the new driver can hang but going back is OK because it matches the NCP. I've seen  the hang on my PCs.

With CTDs just in case of a particular addon with a problem moving to v5, the thing to do is disable DLLs temporarily by renaming dll.xml for a test. If that stops the CTD, next look at what attaches via DLL and work through those.

 

1 hour ago, Chapstick said:

What’s this suppose to prove? That sounds like the crappy experience many of us are having. LM tells users to use the latest drivers, but they don’t work correctly? Looks like they’ve got some work to do.

And why should that be LM problem? Obviously Nvidia changed something. You really don't seem to get the point Gerard is making. 

With device hung error, some things to try, by restore/Apply I am talking about the 'Manage 3D Settings' page:

Global Settings press Restore button, then Apply.

Also on the Program Settings page, choose the Prepar3D.exe profile, change something, apply it, then Restore/Apply that as well.

Another thing to try on the Adjust image settings page, choose the 'Let the 3D app decide' item: