Maybe it's time for me to give up on MSFS.  Since the last patch, two out of the three aircraft I most enjoyed flying no longer work properly for me.  I'm almost ready to give up.

😠 😠 😠

I think they need to have some kind of an optional utility that hashes or verifies the integrity of all the critical game files.  Looking at the widely varied problems people are having, either files are getting corrupted, or people are making mods to the core game files instead of in the Community folder and forgetting about them (note - I'm not saying you've done this, just that it could have the same impact as corrupt files).

Silent bit flips of data stored on hard disks is a thing that happens, the more data in a game the more likely it could happen due to bad RAM, etc.  There needs to be a way for people to verify their install is 100% as part of getting support.

13 minutes ago, marsman2020 said:

I think they need to have some kind of an optional utility that hashes or verifies the integrity of all the critical game files.  Looking at the widely varied problems people are having, either files are getting corrupted, or people are making mods to the core game files instead of in the Community folder and forgetting about them (note - I'm not saying you've done this, just that it could have the same impact as corrupt files).

Silent bit flips of data stored on hard disks is a thing that happens, the more data in a game the more likely it could happen due to bad RAM, etc.  There needs to be a way for people to verify their install is 100% as part of getting support.

In the OP's case though this is probably not the issue as I'm guessing he's talking about the A320 and 787 (or maybe the 747) all of which have had a large amount of reports of the exact same new bugs since the patch.  Maybe Asobo needs to be scanning for corruption on their end 😉

Actually,  I use the Cessna Longitude and the Grand Caravan a lot, and now I have tons of trouble getting them to hold a constant vertical speed or altitude.

The vast majority of issues have nothing to do with the integrity of an individuals installation. I have played the optimism card on here all the way but the latest update really did break more than it fixed. Avionics turning off randomly, even in the C152 and steam gauge C172, meaning no radios, no nav. Some people may not care too much about that because the Plane “still flies”. 

Seems Asobo has force switched on several simulated failures. The bits are flipped yes, but with them, not because of dodgy RAM. Last night in the C172, first the AP went dead after about 20 minutes and then, 10 minutes later the Garmin went dead. That’s not an accident. That is the aircraft systems failures setting working, even when it is set OFF in the sim.

Those that don’t notice the issues either don’t spend much time in the sim or are not bothered with flying an ILS procedure, keeping up radio comms. Incredibly frustrating and I too am losing interest in the sim when I can’t do a simple 30 minute flight without losing AP or radios or nav systems. And that’s just the GA aircraft. Asobo is one step behind the curve.
The rule in aviation - never take your aircraft where your mind has not been 5 minutes before. Asobo needs to apply  that thinking to their sim development.... and issue a hot fix already for all the stuff they broke!

 

Personally, I’d like the option to be able to roll back to the previous version with future updates. I understand it is to be expected that patches will break things for certain people (some people say this is the norm, though I can’t believe a lot of the issues this patch caused couldn’t have been identified before release with the most rudimentary of testing), but if we could go back until the new bugs are fixed, it wouldn’t be such a huge deal.