23 minutes ago, 1st fltsimguy said:

Hey Gerard, I had to look it up, had never heard of it before, are you referring to Prosim-Ar the FMS trainer thing?  Interesting.

Hi Brian,

The FMS trainer is a standalone app that is a FMS only.

The Prosim cockpit suite (both 737 and 320) features detailed modelled aircraft systems (all af systems) a sophisticated and realistic flightmodel characteristics and broad simulator hardware compatibility. And it has an extensive operator functionality.

NeilHewitt - Hear you there - experienced all of what  you report as well on a high level system. Curious thing the sim was rock solid until.......updates from MS (many times) and not so sure but possibly NVIDIA as well. Sim Director wont load, the pilot log is useless and no longer records but worse is unexplained mouse and window and now sound behaviour - which actually will cause an unexplained CTD with no obvious indications - i.e Sim is running smoothly, mouse move or something similar and poof the whole sim just shuts down faster than anything if have ever seen almost like the code has gone into a null zone! I have sent the PC back to the supplier for a complete overhaul (its only 2 months old and the power supply just failed) so maybe it was faulty hardware or not we will see when it returns. 

10 hours ago, Anxu00 said:

Since this is a "rant" hmm therapeutic thread, here is mine: I gave up on MSFS2020 and VR. The latest Oculus software was supposed to give me smooth performance, which it did, once.  All subsequent setup still gave me the slide show.  May be I will try again in year.  Yes MSFS2020 eye candies are amazing, but since I only fly in VR, it's useless.  I still have P3D4.5 and XP11.52 they work fine, and that's what/where I spent time flying. Oh I did not add anything new at all. It helps 🤕

I’m going to join you on this one. I was excited about MSFS, but it performs like a dog. I can kind of fly it in a cub in VR, if i’m very careful with the sliders - to the point that it looks like FS9. And the complex airliners are a joke, and not a funny joke.

To get over my stress and existential despair, i boot up p3d v5, turn on EA and fly my pmdg jet in VR through some beautiful non-sprite clouds. And suddenly, all is well in the world.

6 hours ago, masino said:

The only time I ever had issues with DXGI_ERROR_DEVICE was in connection with TrueGlass. I remove it from every aircraft that uses it and never had issues again since I started doing it. QW 787 was the first that caused that issue, after moving the file out of the aircraft folder it stopped.
 

In case you haven’t gone that route, it might be worth a shot.

It’s a very rare error on a well setup system. 

Here’s a good (serious) question: with a good video card (2080TI+) and a complete default p3d install, are there ANY documented instances of this crash in 5.1?

I use lorby’s app to just load the scenery and packages that i need. No couatl. No v4 programs. Only quality planes (maddog, a2a, pmdg). No fsl bus (changes too many things). no SODE. Don’t even think of using a shader mod!

At times, i will turn on some of the above, and just accept that my sim may be less stable.

I’m confident the base platform is solid, however most of us do push our luck with the addons we choose to use.

1 hour ago, OzWhitey said:

It’s a very rare error on a well setup system. 

In my specific case here, I think it's an overheating issue causing the GPU to thermal throttle and momentarily fault against DX12, which has less protection against this kind of thing. There was a sound blip at the same time indicating a hardware-level fail of some kind. I have 2 high-end GPUs in this box and an OC'd CPU and while it has a good AIO cooler it probably doesn't have the best possible airflow. So I'll be clocking the CPU down a bit and adding a couple more fans. Of course, the main GPU (2080 SUPER) may be failing - it's had nasty coil whine but that usually means nothing. If it fails my sim will be dead in the water until the GPU market calms down and that probably won't be until 2022. 

I'm far less concerned about that one error (frustrating though it was) than about the frequent random CTDs with no error. But really I just wanted to vent. It's good seeing others take the opportunity to do so as well 🙂.

I have posted similar thoughts here and on other flight sim boards. In short, it all depends upon settings. I do not have a SotA rig...my only upgrade since setting up my current computer some three plus years ago has been installation of  Nividia GTX 1660ti video card. I realized after buying it I really should have a card with 8 GB memory instead of the 6 on this card. But, I watch my settings, I do use EA most of the time, except for the ugly dawn and dusk colors, and have been flying without any dx errors with usually around 4GB of my 5.1GB available with my GPU.

So, if you must have all settings to the max, you will need the max...if you can live with compromise, things work out well.

Sherm

1 hour ago, shermank said:

So, if you must have all settings to the max, you will need the max...if you can live with compromise, things work out well.

My settings are very much a compromise. But take complex scenery and a complex aircraft and you won't get much change out of a top-end machine even with relatively conservative sliders. P3Dv5 gives me more FPS in the same situation as v4 did, but it still stretches the hardware all the way, with Core 0 pinned to 100% continuously. I've only run out of VRAM once that I know of, even with 8GB on the GPU in this PC (my other PC, the 'image generator' machine, has a 1080Ti with 11GB). Once I can upgrade to a 10GB+ card in the host PC I will, but 2nd hand GPU prices are ridiculous and retail prices more so, even when there is availability. Which is never 🙂 

15 hours ago, SAX702 said:

For (a) it can't be the P3D because if that was the case, every other P3D user would be experiencing the same.

As a software author and user, I always have a challenge with this reasoning. It would imply that it's not really a bug unless 100% of the user base encounters it.

Those kinds of bugs almost never make it past rudimentary testing and QA. Almost all that make it into the wild require a specific state or set of events of happen, which means that the vast majority of users are not encountering them.

Cheers!

I no longer have any stress. I've gone back to FSX...where everything works!

4 hours ago, OzWhitey said:

No couatl. No v4 programs. Only quality planes (maddog, a2a, pmdg). No fsl bus (changes too many things). no SODE. Don’t even think of using a shader mod!

I run all these things and got the DXGI crash early on in v5, but since I toned down the overclock on my 1080Ti, I haven't seen it a single time. My card is one of those gaming ones that is overclocked from the factory. I had no idea about this overclock until someone mentioned it in one of the forums.

Here's your GSX SODE fix
https://sode.12bpilot.ch/?topic=p3d-v5-1-and-sode-1-7-1#post-4992

The DXGI crash is many times caused by overheating ; on my left view pc I leave the left side open so heat can escape which the 3090 is blowing in the case.

If I close the case I am getting a DXGI within an hour.

Bottomline : make sure your case is ventilated well enough and check the temps from your GPU and CPU if you experience any DXGI errors.

1 hour ago, GSalden said:

Bottomline : make sure your case is ventilated well enough and check the temps from your GPU and CPU if you experience any DXGI errors.

nice, but I also just brought mine into the garage and ran it through an air compressor cleaning, you'd be surprised what comes out of there, even on the vid card.

1 hour ago, GSalden said:

The DXGI crash is many times caused by overheating ; on my left view pc I leave the left side open so heat can escape which the 3090 is blowing in the case.

If I close the case I am getting a DXGI within an hour.

Bottomline : make sure your case is ventilated well enough and check the temps from your GPU and CPU if you experience any DXGI errors.

Nothing wrong with my temps.

My DXGI errors come from changing one aircraft to another after initial load or if changing too many world settings in the menu.

5 hours ago, neilhewitt said:

In my specific case here, I think it's an overheating issue causing the GPU to thermal throttle and momentarily fault against DX12, which has less protection against this kind of thing.

Have you looked into the TDRDelay registry entry?  There are some recent threads on here.  Also a suggestion to use a slightly older nvidia driver (460.something) was in one of those threads.  Since I added the TDR registry entries and the 460.xx driver I have no DXGI errors.  I can even run vsync in the rain again.  It's nice.

Now MSFS is CTD'ing more (rarely) than P3D (not at all).  Yeah, it's frustrating.  I know you didn't want advice so I'll just be quiet after the above paragraph.  But I have gotten frustrated from time to time, and in those situations I go and do something else.  When I feel like flying again, I fly.