1 hour ago, fppilot said:

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

Well, for instance in the last few days I've had several crashes with the new experimental version of the A320. The Sim would freeze, or completely crash to desktop very soon after I got into the air or even just upon loading.

Despite years of simming, I've never ever been even remotely interested in the big jets, and it's only msfs that finally tempted me to begin learning in the last few months

So there are some things that are still new to me, and one of those is that apparently I've been entering the simbrief flight plans into the SIM incorrectly and in such a way as to cause interference from the default flight planner.

Apparently that was no big thing in the development version, and it all worked out, but not so much with the new planner in this new experimental version.......

Edit: and shortly after Su5 came out, I had a few crashes or ctds here and there, but it turned out to be either liveries that were incompatible with Su5, or scenery / airports that were not compatible.

Edited August 22, 20214 yr by HiFlyer

1 hour ago, HiFlyer said:

Apparently that was no big thing in the development version, and it all worked out, but not so much with the new planner in this new experimental version.......

Developmental and experiential versions of ??????  The MSFS sim?  Simbrief?  or the A320?  I'm guessing the A320.

Just now, fppilot said:

Developmental and experiential versions of ??????  The MSFS sim?  Simbrief?  or the A320?  I'm guessing the A320.

A320

I thought I'd throw in my 3 cents worth...

Point of Reference:  Since I first downloaded MSFS 2020, I have not uninstalled it, nor have I reloaded Windows (I am using the same Windows 10 software I originally installed when I built my gaming computer some 4-5 years ago - and I have installed every Windows 10 update)

I have only had 2 CTDs that I can remember since I first installed MSFS 2020.  The reasons for the CTDs were due to overclocking my CPU.  I have had a couple of hangs due to add-ons being out of date; otherwise, I do not see CTDs.

First, for pre-built systems - these are not always created equally.  I choose to build my own dedicated system for two main reasons: 1) I am an experienced system builder and I have built hundreds of systems and servers for many uses and 2) I know when I build a system, every component I install, I know is compatible to work together.  That being said, when it comes to leading edge hardware or even any hardware upgrade for that matter, it is imperative we do our own research into components we're upgrading.  As an example, when I built my pc, I verified every piece of hardware, from the power supply, case, memory, video, SSDs, hybrid drives, cpu, etc, etc.

So, when I hear of CTDs, I naturally think hardware first.  This obviously isn't always the case as there is such a thing as buggy software, but when CTDs are not happening with consistency throughout the hobby, I would say that the CTD is hardware related in the majority of cases.

~Robert

8 minutes ago, SmokeDiddy said:

Point of Reference:  Since I first downloaded MSFS 2020, I have not uninstalled it, nor have I reloaded Windows (I am using the same Windows 10 software I originally installed when I built my gaming computer some 4-5 years ago - and I have installed every Windows 10 update)

Interesting point, and I’m in the same boat, with no CTDs.

I think a contributing factor for crashes and issues, in addition to possible hardware problems, is people who don’t install updates and drivers as they get released, and install/uninstall/install again.

I know the old adage “don’t install a patch if you don’t have the problem” but that’s really obsolete thinking. With cloud based updates, and the kinds of cyber threats now in the wild, it’s more prudent to update and rollback should an issue actually happen. Personally, I’ve only had to roll back an update or driver a handful of times over the last decade.

When the OS, drivers, and hardware are all working well together, the chance for crashes is much less. 

MS Store version. I’ve been fortunate. I’ve had maybe 2-3 actual CTDs over the past year. I have had a few instances where the sim would simply stop loading when starting a flight. Those were all fixed by clearing the rolling cache. I don’t, however, have many addons. Just the WT stuff and a couple of freeware sceneries. 
 

I do sympathize with those that are experiencing CTDs. That would be extremely frustrating and it is certainly not your “fault”. I don’t envy Asobo trying to track down all of the root causes with so many configurations and potential external sources for issues. 
 

But for the record, SU5 has been extremely positive for me.

17 minutes ago, SmokeDiddy said:

So, when I hear of CTDs, I naturally think hardware first.  This obviously isn't always the case as there is such a thing as buggy software, but when CTDs are not happening with consistency throughout the hobby, I would say that the CTD is hardware related in the majority of cases.

 

I hear what you are saying.  I handpicked each component of my three most-recent systems, including this one, and had MicroCenter build them.  Now. That said. And I understand your focus on hardware.  I made zero hardware component changes from my previous MSFS installation to this new fresh one.  I did not reinstall Windows 10.  My CTDs and freezes in MSFS appear to be history (I hope I don't suffer now from having said that).  

I did make a couple of BIOS changes.  I found I did not have HT enabled and enabled it.  I made one other change but do not recall its nature.  And I changed my Windows power settings from balanced to high performance.  There is a good video tutorial at:  https://www.youtube.com/watch?v=sH2FCmBg7VA&ab_channel=50Fifty

Edited August 22, 20214 yr by fppilot

16 hours ago, PilotPete99 said:

That’s problematic considering you can’t do anything to alter a console or it’s operating system.

Cheers, Pete

The problem is in the software so there really shouldn't be anything you should need to alter in the hardware nor operating system--IOW this is 100% in the domain of the developer to address.

SU5 and the hotfix has been absolutely abysmal for me with almost all flights ending in CTDs. However, a rather surprising find has the sim now performing rather stable for me. Hope it'll last. 

27 minutes ago, Noel said:

this is 100% in the domain of the developer to address.

It’s obviously specific configurations or use cases that cause issues. If the software was just borked, then everyone would have issues, and those issues would be consistent across the board.

That’s demonstrably not the case. But hopefully they can isolate the combination of hardware and software (including add ons) that tend to cause issues.

14 minutes ago, Swe_Richard said:

SU5 and the hotfix has been absolutely abysmal for me with almost all flights ending in CTDs.

Quote

However, a rather surprising find has the sim now performing rather stable for me. Hope it'll last. 

Would you be further able to enlighten us?

8 hours ago, RALF9636 said:

MS Store version.

Just one CTD in dozens of sessions (and suspecting the FBW A320 as cause for that one CTD).

 

MS Store version, no CTDs (yet).

1 minute ago, fppilot said:

Would you be further able to enlighten us?

I made a thread about it a number of days ago. It got kind of heated. Think I called it "The light in the tunnel - the sequel" or something like that. 

Suffice it to say; my CTDs have all but vanished (knock on wood). 

 

10 minutes ago, neil0311 said:

It’s obviously specific configurations or use cases that cause issues.

I have a virgin install of MSFS and SU5 brought on CTD issues for me.  Prior to SU5 I had maybe 2.  Since, probably 6 or 7 now.  Clearly something IN SU5 created this.  Just because all users didn't have the same frequency of manifestations of this does not imply the software isn't borked, it likely means the changes in SU5 did not consider all of the same potential factors that obviously weren't coming into play pre SU5.

3 hours ago, HiFlyer said:

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.

True, theres an almost infinite variety of configurations of PCs out there, affects us all differently. 

I plan on building a new rig and look forward to enjoying MSFS to its fullest. Right now on this old one I can only fly GA low and slow out over the boonies or very small villages. Forest density does not affect me at all, I have trees maxed out and can get upto 45FPS.

But  cannot fly airliners and cannot fly near any cities. FPS drops to single digits.