Extremely few CTDs - all related to clear and identifiable causes: vfr map bug, broken runtime libraries, freezes with Version 0.2 of the NXi, etc. 

It should be noted that he had some stability problems with SU5 during the beta test.
I’ve never had a CDT since the release a year ago, the few CDT I’ve had is during the beta phase. So...

8 hours ago, Beagle12 said:

Whenever I land at an airport, I lose all control of the aircraft. ATC instructs me to taxy to general aviation parking, and my AI pilot just goes ahead and does it. I have no control on where the AI pilot goes. Too bad if I wanted to taxy to the runway threshold and depart again. This is with autopilot turned off. Anyone else experiencing this ? 

Steam version.

What is an AI Pilot, never have used that...?

9 hours ago, Tuskin38 said:

For those who have had very few issues since SU5 compared to others, are you running the Steam or MS Store version?

Store version, but ......

I was on vacation when SU5 released and followed all the horror stories here on Avsim. Decided to reinstall Win10 and MSFS when I got back. Good decision as I've had nary a problem and the sim is running better than it ever has. Reinstalling was easier than I thought.

Fingers crossed.

10 hours ago, Tuskin38 said:

For those who have had very few issues since SU5 compared to others, are you running the Steam or MS Store version?

MS Store. Need to point out that I did a 100% uninstall and removed all traces of MSFS, waited until well after the hotfixes to complete a fresh installation, and installed MSFS into a much much much shorter path, a folder off the root of a dedicated SSD.  Prior to all of that I was besieged with mostly G1000 MFD freezes (only the GPS, not the sim), MSFS freezes, and occasional CTDs.  I was only completing about 50% of my flight attempts and that had me flying more in FSX SE than in MSFS.

I have also taken other steps.  First I placed my folders for the Addons Linker into a more shallow folder tree. I append the folder name of each scenery addon, livery, and mod with a "(5)" when I see that it has been validated for SU5 or when I have flown with or near it successfully on multiple occasions.  If I experience an issue in MSFS I append the folder name for each addon I had loaded with a "(-5)" until I can later safely clear it.

Why increase the odds?

For airports and other scenery I only load what I most directly need for that specific flight.  I have no idea what parameters MSFS holds for load radius in distance. 

For instance on a flight Friday from KAVL to KPIE (Asheville, NC, USA to St Petersburg, FL, USA) my flight path was over the USA state of Georgia.  I have a number of addon freeware scenery mods for Georgia and for Florida.  In the past I would just click on Georgia within my folder organization for the Addons Linker.  For Friday's flight I did not select anything for Georgia.  I determined I was not flying close enough to, especially at 11,000 ft., any of those addons to even view them.  For Florida I only selected an addon for KPIE and one other nearby airport.  Nothing else for Florida, and I do have a significant number of Florida addons.  But my flight path was not near any of them. And why load scenery when flying above a broken or overcast layer?

No CTD's or sim freezes since I completed the fresh installation with the exception of (2) two I experienced when attempting to fly from KTTD, Troutdale, to flying around Oregon the previous weekend.  I have a number of addons for the Portland, Oregon, area and after disabling all of them my MSFS was reliable.  I do not fly that area often so have not since then attempted to identify the culprits.  And it may well be the aggregate of the addons in my Portland folders, not any one in particular.  I believe I have a PDX, a PDX taxiway fix, a set of Portland bridges, another small airport, and a Port of Portland addon.

Oh! And I have never OC'd either CPU or GPU

Edited August 22, 20214 yr by fppilot

I have had the game for about 3 months and have had just 1 CTD - and that was one related to overclocking.

I learnt fast that this game hates OC so I bought it down from 3.8 to 3.5Ghz and not a single CTD. And this is with 66 add-ons in the community folder on an ancient 14 year old i7-920 PC. 

Edited August 22, 20214 yr by ThrottleUp

9 hours ago, Tuskin38 said:

For those who have had very few issues since SU5 compared to others, are you running the Steam or MS Store version?

I have never had a CTD from Alpha 4 through the present iteration of SU5. Not a single CTD in over one year of flying MSFS on a daily basis. It is the MSFS store version. I am a beta tester for the CRJ, and sometimes have flown that particular model as much as 10 hours in one day, on multiple back-to-back flights.

My MSFS installation is on a dedicated SSD drive (D:\) and has been since day one.

That said, there are some MSFS features that I do not (and never have) used, which might be implicated in crashes for some users. I do not use the default flight planner. The only world map feature I use is to set my departure airport and starting position.

I prefer to do my own flight plan entry directly in the FMS or GNS of those aircraft that support this, which includes the Aerosoft CRJ, the WT CJ-4, the FBW A320 and (now) the new WT G-1000 NXi. I do my flight planning externally using PFPX or Simbrief.

I do not use the default MSFS ATC. I do not use AI traffic or multiplayer. I do use Live Weather on every flight except during the recent bug that arose with the original release of SU5 with the extreme temperatures at high altitude.

I have the WT G3000 and CJ4 mods, 3 payware airport sceneries (KPWK, KTEB and KSDF), and the latest version of the free “toolbar pushback” utility. Two payware aircraft (the Aerosoft CRJ and the PMDG DC-6) and one freeware aircraft (Rob Young’s turbo Bonanza). I use Navigraph MSFS nav data, and have been since it first became available last year.

My GPU is a GTX1080Ti - I run the latest driver. I have a dedicated SoundBlaster-Z sound card (the default motherboard sound system lost the left channel two years ago), and have a wired 1GB Ethernet connection to a top-end Netgear RAXE500 router. I am fortunate in that my ISP (Spectum cable) has a very short path between their backbone network and the MSFS East server. There are typically only two or three intermediate network hops between Spectrum’s external network gateway and the MSFS server.

Probably for this reason, I have never had a problem with file looping during updates, or slow download speeds.

While I have never (yet) had a CTD in normal operation of MSFS, I have had one or two while doing airport scenery modification using the dev mode editor. They seem to be spurred by trying to make too many changes in one session before running a recompile of the scenery. When they occur, they are always immediately preceded by a loss of sound a few seconds before the crash.

 

Using MS Store version.   I had one CTD that was the VFR map bug.  I tend to fly low and slow and the longest flight Ive done is about 150nm.

The program works well enough for me.

9 minutes ago, JRBarrett said:

That said, there are some MSFS features that I do not (and never have) used, which might be implicated in crashes for some users. I do not use the default flight planner. The only world map feature I use is to set my departure airport and starting position.

Most of the flights I had issues during were flights where I created the flight plan say at Skyvector, pasted the route line into LittleNavMap to create an MSFS flight plan, and then loaded that plan into MSFS at the World Map.  I long suspected that perhaps MSFS had trouble either with some of the waypoints, or the quantity of waypoints, or such.  I am not faulting LNM or Skyvector here.  The flight plans look flawless to me.  I believe if it were an issue with what I was experiencing that it was within MSFS.

In addition to the steps I take as described in my earlier message in this topic, I now manually enter my flight plans into MSFS, either with the MSFS flight planner, or now in the GXi once a flight with just Origin and Destination has loaded.  i.e no more "loading" a flight plan from any external source.

Dedicated  machine, Steam, virtually zero issues. Specs below.

4 minutes ago, fppilot said:

Most of the flights I had issues during were flights where I created the flight plan say at Skyvector, pasted the route line into LittleNavMap to create an MSFS flight plan, and then loaded that plan into MSFS at the World Map.  I long suspected that perhaps MSFS had trouble either with some of the waypoints, or the quantity of waypoints, or such.  I am not faulting LNM or Skyvector here.  The flight plans look flawless to me.  I believe if it were an issue with what I was experiencing that it was within MSFS.

In addition to the steps I take as described in my earlier message in this topic, I now manually enter my flight plans into MSFS, either with the MSFS flight planner, or now in the GXi once a flight with just Origin and Destination has loaded.  i.e no more "loading" a flight plan from any external source.

I have loaded external plans created with LNM specifically for the DC-6. Trying to enter FPs directly in the GNS430 is tedious (as it is in the real unit!)

It works, as long as I chose my starting position from the drop down list, rather than by clicking on a starting position on the map, which blows away my imported plan, and substitutes MSFS’s own auto-routing. Once the WT developers now working for Asobo complete their overhaul of the default MSFS flight planner (which is supposed to be coming later this year), I might be more inclined to use the default.

The new NXi is very easy to use for FP entry with the option to enable the keyboard to enter airport and waypoint names. 

I have had very few ctd's, and the ones that I have had, I have eventually been able to trace back to errors on my part.

9 minutes ago, JRBarrett said:

I have loaded external plans created with LNM specifically for the DC-6. Trying to enter FPs directly in the GNS430 is tedious (as it is in the real unit!)

It works, as long as I chose my starting position from the drop down list, rather than by clicking on a starting position on the map, which blows away my imported plan, and substitutes MSFS’s own auto-routing. Once the WT developers now working for Asobo complete their overhaul of the default MSFS flight planner (which is supposed to be coming later this year), I might be more inclined to use the default.

The new NXi is very easy to use for FP entry with the option to enable the keyboard to enter airport and waypoint names. 

I use simbrief and the simbrief downloader. Make FP in simbrief, run the downloader and it installs it into MSFS and whatever GPS your aircraft uses with one click. 

46 minutes ago, ThrottleUp said:

I have had the game for about 3 months and have had just 1 CTD - and that was one related to overclocking.

I learnt fast that this game hates OC so I bought it down from 3.8 to 3.5Ghz and not a single CTD. And this is with 66 add-ons in the community folder on an ancient 14 year old i7-920 PC. 

Which is interesting to hear, and goes back to how our experiences with the SIM vary so widely. As a general rule, I run my processor with an overclock at 5 gigahertz, and so far have had no issues I can trace back to overclocking.

11 minutes ago, HiFlyer said:

I have eventually been able to trace back to errors on my part.

Please share....  We all learn from errors, whether our own or of others.