A peculiar problem indeed. Reading all these accounts of the avionics shutting down, lights flickering on and off, and fuel valves turning off by themselves is quite the horror mystery that's even scarier than most horror mystery movies! 😂

Jokes aside, I've flown 11 flights since updating to patch #2 and I have yet to encounter these problems myself. Now post-patch I have only flown in the Cirrus SR22, Diamond DA40 (both TDI and NG), and the Diamond DA62 and I've only flown within Australia in both daytime and night time. I hand flew the TDI since it doesn't have AP and used the AP on the rest. Not only did the avionics and AP stay on and fully operational during the entire flight, the AP even tracked quite precisely to my VFR flight plan even in winds up to 20+ knots (Melbourne has been quite windy these few days!). No zig-zagging and no severe unexpected pitching up or down. I even switched from my usual south-east Asia server to one of the US servers today to see if I might encounter these problems but so far nothing. Granted my flights have all been short flights within 30 minutes, some 10-15 minutes some 20+ minutes but from what some people have reported, they even encountered the problem shortly into their flight, some even soon after taking off. So yeah, not sure what the common denominator is to this problem. Could it be a location thing that only affects certain parts of the world like the 225/3 wind issue? (I was getting winds other than 225/3 even before patch #2 flying in Australia) I'll fly in other parts of the world and on different planes and servers to see if I can encounter this problem, but otherwise can't be of much help sorry. 😕

18 hours ago, RW1 said:

I tried a flight with the Carenado Ovation tonight. Loaded a flight plan and the Instruments went dead instantly. This bug seems to be caused by loading a flight plan. I exited and restarted a flight again this time with no flight plan loaded and it worked fine. Can anyone replicate this. 

I can confirm that it has nothing to do with flight plans.  Most of my flying is done without one as I tend to fly around a local area and return to the same field from which I departed.   In my case I have witnessed the issue in the Caravan, G56, C172 classic and in the new Carenado M20J, which seems to be particularly susceptible to to the issue.   The clicking noise I hear prior to the shut down is actually the panel lighting being adjusted.   Flying during the day with panel lights out, hear the clicking, avionics and AP go out, and the lights on the panel have been turned on.

Hey guys. OP here for those who forgot.

1. I ducked out shortly after starting this thread not letting my emotions take the best of me, I was pretty fired up at the time and then the thread took a predictable turn for the worse with the typical detractor/passive aggressive style posting. Which is beyond frustrating. I don't just post threads like this without doing my research of others and my own experiences so to see that initial reaction from a vocal minority was infuriating. But.. I vowed to be the better man and take two days off.

2. Thanks to the mod team for reading the room and situation and keeping the thread open with a stern warning to knock off the B.S. and seeing that this is obviously legit and not just another random unsubstantiated rant.

3. I'm still fired up about this bug. I paid $120 straight out of pocket. It's a Flight Simulator/Game Of Flight/Whatever Of Flight software application. Fact is.. There are two things we need at THE BASIC level to remotely enjoy this game..   Planes, and avionics and right now for all of us suffering from this bug, the avionics pretty much do not exist.  It's maddening and I feel I was taken for a ride I didn't sign up for. 

So please.. Continue reporting this on the official channels, upvote the thread at the official forums and do not stop letting your voice be heard..   In the end this is poor QA and I stand by my statement. The entire QA team needs to be revamped. Enough is enough..

I have seen other posts where pilots had problems or just did not like the sim for whatever reason and got a $$ refund.

 

1 hour ago, vonmar said:

 

I have seen other posts where pilots had problems or just did not like the sim for whatever reason and got a $$ refund.

 

That my friend is not a solution. It’s not even helpful. I do not want a refund. I want what I paid for. That is the solution. Like others, I have reported to ZenDesk. If every person that had purchased this sim and had issues with it asked for a refund, this MSFS “project” would be shut down tomorrow by MS as a massive financial loss. 

22 minutes ago, RaptyrOne said:

That my friend is not a solution. It’s not even helpful. I do not want a refund. I want what I paid for. That is the solution. Like others, I have reported to ZenDesk. If every person that had purchased this sim and had issues with it asked for a refund, this MSFS “project” would be shut down tomorrow by MS as a massive financial loss. 

That depends on how long it will take to get the base running without issues.

If he wants a refund after trying for a month and it doesn’t live up to his expectations then  that is the best thing he could do. He chooses to not be a paying beta tester.

And to be honest : would you have bought it if you knew what you know now ? 

If you had bought a new car and it had all kind of software issues would you want to wait X months or do you go back and demand a solution?
 

Edited September 20, 20205 yr by GSalden

2 hours ago, styckx said:

So please.. Continue reporting this on the official channels, upvote the thread at the official forums and do not stop letting your voice be heard..   In the end this is poor QA and I stand by my statement. The entire QA team needs to be revamped. Enough is enough..

The problem is that when you're making large changes in a patch (meaning probably large changes to the code), there's a corresponding increase in the chances that something broke something.  Doing thorough QA on a 15GB patch would probably take weeks, but they clearly want to get this stuff fixed quickly.  They probably did a little more than the amount necessary for it to pass cert, and then pushed it out.

I agree with you 300% that we paid money for a finished product, and shouldn't have to be beta testers.  My recommendation is to just come to terms with the fact that it's basically what we are right now.  Simulators are crazy-complex software, and there were inevitably going to be early teething episodes like this, unless they kept it in beta for at least a year - let alone two WEEKS.

I doubt it's incompetent QA staff, and more that there's a lot of people at Asobo (and Microsoft for that matter) completing tasks under immense pressure and deadlines right now, trying to fix the major issues.

My own zen take has been to acknowledge that even if this was a paid early access beta, I still very likely would've bought it to play right away.  So they can call it whatever they want, but as a "hardcore" flight simulator, it's clearly in beta.  And given that tiny beta cycle before release, I doubt it was Asobo's choice to release in August.

But still, none of that invalidates your frustration of course.  Hopefully in a few months we'll be able to make threads reminiscing about how rockey those first few months were. 😄

...and hopefully there's a hotfix incoming for some of the new things the patch broke, haha.

 

32 minutes ago, GSalden said:

If you had bought a new car and it had all kind of software issues would you want to wait X months or do you go back and demand a solution?

A car isn't software, but they do get recalls for flaws all the time.

personally, between me and a small group of friends who have this product, we believe that it has to do with if the developer mode was active during the last flight you had and closed out of prior to install of the patch.  We believe this is why some have issues and some do not.  Unfortunately, do have this issue.  Basically, we feel it is connected with the status of the sim prior to patch.

This might not help:

Spoiler

 

Thanks to everyone for this thread. I thought I was the only one with this issue.

The issue became unbearable earlier today after purchasing the Carenado Mooney. No avionics what so ever. I had intermittent problems before with the C172 and TBM, but I chalked that up to the most recent patch being buggy since the problems seemed to coincide with that update.. Pretty much the same intermittent behavior everyone here has reported. I'm a patient person. I get this is a large, evolving product. But after throwing down $30 for the Mooney, I was plenty displeased with no avionics at all. Flight plan or not, didn't matter. AI controlled start-up or manual. Cold and dark, or started on the runway. None of it mattered. No radios, no GPS - nada..

I've been running what I thought was a pretty plain install of MSFS. No real mods or fixes. But I did have two LIVERY packs I downloaded from FlighSim.com. They were for the TBM and the Savage Cub and they were installed by me into the Community folder. Decided to delete them to make the install as virgin a state as possible.

And voila! I got all the systems back for the Carenado Mooney. I have not tested it further, but it seems to be something to look into. How this impacts things like publicly developed liveries and such will be part of the process, for sure. We all need liveries and other items for the community to work without affecting the program base.

Again, this may not work for everyone, but it worked for me. Good luck...

Edited September 20, 20205 yr by zbuzz123

1 hour ago, RaptyrOne said:

That my friend is not a solution. It’s not even helpful. I do not want a refund. I want what I paid for. That is the solution. Like others, I have reported to ZenDesk. If every person that had purchased this sim and had issues with it asked for a refund, this MSFS “project” would be shut down tomorrow by MS as a massive financial loss. 

Hello all,

I agree with this in that it is not the solution.  I think reporting to ZenDesk is the right thing to do as well. However, the rest is a little over the top in my view.

Unfortunately, it is nowhere near a majority of people who are experiencing this and other problems.  Look at the sales-complaints ratio. I am not trying to downplay the problems however.

Despite the "nobody is suffering/it is only a game/I am not experiencing this problem/get a grip" responses, this is VERY real to the people who have spent the money for a simulator experience and not just as a gamer, although it appears both groups are in the mix.

It is time to get away from the debate outline above, and to try to find a solution. We still have not even isolated self-infliction or Developer software problems mainly because this is not affecting everybody. That should probably be a first priority and once determined and demonstrably proven, the community and the Dev can get on with a fix.

Unfortunately, my one suggestion has been ruled out and I do not have the ability to analyze, detect and solve much else.  There are people in this forum who do have those abilities though and I have confidence that they are behind the scenes trying to work it out. I hope the solution to this and other problems are forthcoming sooner rather than later.

For those experiencing this and other problems, you have my hopes and sympathies.

Oh, by the way, I am not having any problems with MSFS and I am sure that will make you all feel so much better. (Yu know what I mean)

Tony

Emptying out the Community folder (move the contents to a Backup folder on the same drive) is not a bad strategy... it may just help 🙂

This thing is an absolute joke, never have I seen anything like this in gaming.  I've been waiting for the update to repeat this flight from KDTW to KORD and compare to my past issues.  Well, 12 miles out at 4000 ft  stall stall stall, went down like a dart and nothing I could do.  Really MS and Asobo? Really?  There is zero threat to LM and Laminar for at least 2 years and maybe never, and by that time they will be on their next better version, mark my words.  I'm not even bothering reporting this on Zendesk, their todo list must have 1000 items if not more.  Buyer beware, do not buy this. Can't believe I spent $180 CDN on this.  

4 minutes ago, canuk_22 said:

This thing is an absolute joke, never have I seen anything like this in gaming.  I've been waiting for the update to repeat this flight from KDTW to KORD and compare to my past issues.  Well, 12 miles out at 4000 ft  stall stall stall, went down like a dart and nothing I could do.  Really MS and Asobo? Really?  There is zero threat to LM and Laminar for at least 2 years and maybe never, and by that time they will be on their next better version, mark my words.  I'm not even bothering reporting this on Zendesk, their todo list must have 1000 items if not more.  Buyer beware, do not buy this. Can't believe I spent $180 CDN on this.  

This is my hometown / favorite flight:

was going to try :
KAYLN2 SMUUV WYNDE1

Which aircraft failed on your flight?

I may be able to do a test.

So far I have not had problems.