I haven't seen this but I usually only fly the Airbus. Loving the sim right now. Shame its not working for everyone.

Sorry to hear your problems, not seen it once in 42 hours flight time. 

Just check you have no rogue key bound to avionics, I think there was a bug with honey c, yoke made heading bug move 10  deg at a time, I know you’re not the only one with the bug but try sharing more info. As if everyone had it then, it would be a major problem.

Well just for clarity, I will try to add a touch of info that may be of some use...

Remember these are only for me, and yes i have posted these to Zendesk...  I have added both here because I don't know if they may be linked.

ISSUE 1)

1)  Only happened to me since last patch and zero changes to config/settings/controls etc since last patch..

2)  For me it has happened on the 172/1000, TBM, King Air and today the M20 from carenado

3) Issue  All avionics goes dead at a random time into the flight meaning all A/P functionality, and in some cases Radio equipment goes dead.

4) In all cases, avionics can be recovered by switching the Avionics main switch off and on again and then restarting the garmin equipment..  when restarted, you can then re-engage the A/P and radio stack EXCEPT in the new M20, this recovery doesn't work and there is no recovery from that, once gone it stays gone.

5) In some cases, the failure is preceeded by the sound of a switch click in the cockpit, and the AMP meter going zero or negative.

ISSUE 2)

1) There appears to be additional issues that may be related to this since it is the Garmin equipent that handles the A/P in that since the patch it has been noticable that a number of the planes "hunt" the correct GPS line more than they used do, drifting left and right of that line. 

2) In addition, ATC responses have altered on ILS approaches..  before when you were doing an ILS approach, the ATC message to "contact tower when inbound" happened just before the last turn onto approach,  now it happens some way in front of that.. in fact it now happens before you turn onto the "downwind" leg of the approach

3) Something deffinately changed in the ILS and GPS following systems at the same time and made those worse as well since the patch.

Edited September 19, 20205 yr by Moria15

Working all fine here. I have flown over 15 hrs since last patch.

2 hours ago, Rob_Ainscough said:

What are your realism settings?

Cheers, Rob.

I laughed when I saw this and then a few seconds later thought.. surely not, really?  so i checked, but I cannot find any realism settings that might account for internal equipment failure...  Mine are set to hard for things such as stress damage, crash damage etc, but nothing in that area would indicate the possibility of internal equipment failure 🙂    But thanks for the idea 🙂  oh also checked the individual failures options on the individual aircraft and they are all set to off as well 🙂

 

Graham

Edited September 19, 20205 yr by Moria15

Yeah I get the avionics switching off at times, its happened in the G36 and the 350i. Also have an issue with the King air where if I try and start from cold and dark the right engine wont turn on. If I start from the runway it works fine.

 

Its annoying for sure, but I'm still enjoying this sim immensely.

17 minutes ago, Baber20 said:

Working all fine here. I have flown over 15 hrs since last patch.

According to my OnAir logs, I have flown 52 hours (46 flights) of 172/TBM/KingAir before the patch with no issues and 21 hours since and in those 21 hours (which was 14 flights) I have had the Avionics failure 12 times 😞

I'm thinking about full re-install as some people are saying that has cured it for them and wondering if an update file might have been corrupted...   It would be nice (and I may have missed it) if there was a check file integrity option  (I am not on steam).

Regards

 

Graham

Edited September 19, 20205 yr by Moria15

I saw someone on the flightsimulator forums that thinks with so many people reporting the same thing or similar and the pattern at which system A fails followed by System B etc. that it's almost like the failure system is turned on in the background even though a user hasn't set any to occur.

@moria15 Do you have a honeycomb yoke?
I believe there is a mention in the patch notes about a fix for the alternator in combination with that yoke, and your description about the issues you have just reminded me of that item.

1 hour ago, Moria15 said:

I'm thinking about full re-install as some people are saying that has cured it for them

No, don’t do that. All that hassle will be worthless. That won’t fix it. People that have not seen the bug either are just lucky and it is a matter of time, or perhaps their PC hardware is different. Uninstalling a bug and then reinstalling the same bug = the same result. This is a BUG, not a corrupt installation issue. In time, more and more will come to see this for themselves.

17 minutes ago, orchestra_nl said:

@moria15 Do you have a honeycomb yoke?
I believe there is a mention in the patch notes about a fix for the alternator in combination with that yoke, and your description about the issues you have just reminded me of that item.

nope 🙂  saw that, but thank you..  now here is something interesting....   I borrowed a friends Saitek (sp) autopilot panel last night and was flying my Cessna, and when all the avionics went off..  the Saitek stayed on and the AP was still controllable from the Saitek panel but NOT in the actual aircraft...    switching off the Avionics and back on in the aircraft killed the saitek but on restarting the in-plane garmin, the saitek also came back on and things were fine again.

Have checked all the failure screens, both in the sim and in the individual aircraft and also ensured that there are zero key options and settings that could cause unwarranted problems.. in fact, I un-assigned every single option on keyboard, mouse and joystick for any of the avionics or A/P functions.

I have to believe that because of other issues as well, somewhere behind the scenes something was done to the A/P because of the changes in when and where the ATC commands are now issued on approach and that something is resetting the avionics in the aircraft even though in the sim it still operates, as shown by the Saitek panel.. orrrr and this would be my first guess...  the change to update frequency of the glass panels has introduced a bug that affects the battery and avionics orrrr  the change they did for the honycomb has stuffed it for everyone else  🙂

PS  yeah, I have changed my frequency of update for the glass panels  from low to mid to high and still get the same issue 🙂

Graham

Edited September 19, 20205 yr by Moria15

16 minutes ago, Moria15 said:

nope 🙂  saw that, but thank you..  now here is something interesting....   I borrowed a friends Saitek (sp) autopilot panel last night and was flying my Cessna, and when all the avionics went off..  the Saitek stayed on and the AP was still controllable from the Saitek panel but NOT in the actual aircraft...    switching off the Avionics and back on in the aircraft killed the saitek but on restarting the in-plane garmin, the saitek also came back on and things were fine again.

Have checked all the failure screens, both in the sim and in the individual aircraft and also ensured that there are zero key options and settings that could cause unwarranted problems.. in fact, I un-assigned every single option on keyboard, mouse and joystick for any of the avionics or A/P functions.

I have to believe that because of other issues as well, somewhere behind the scenes something was done to the A/P because of the changes in when and where the ATC commands are now issued on approach and that something is resetting the avionics in the aircraft even though in the sim it still operates, as shown by the Saitek panel.. orrrr and this would be my first guess...  the change to update frequency of the glass panels has introduced a bug that affects the battery and avionics orrrr  the change they did for the honycomb has stuffed it for everyone else  🙂

PS  yeah, I have changed my frequency of update for the glass panels  from low to mid to high and still get the same issue 🙂

Graham

Pretty sure I was using a vrinsight panel to control the autopilot last night with Linda and fsuipc running, was controlling the c172 autopilot with the vrinsight when it happened. I have just done a test for 5 hours just using the c172 autopilot on a flight and it's been flawless, I will do the same flight tomorrow using the vrinsight hardware, I have even been switching to the c172 glass via Dev mode and doing some autopilot diversions off and back to track and just perfect

It might be an idea for you guys with the problem to list your controllers see they if there are any common denominators.

So far...nothing TM HOTAS Warthhog and TM TPR, both recognized out the box by MFS.

Also don't forget to check you rudders also for assignments. P3D added all sorts of strange thing to TPR, gear up!, so don't forget rudders just to make sure.

If you really want to test it, start a flight in the air put on AP and don't have any joystick/rudders connected, nothing. Turn off dev mode,Then see. 

Sorry to hear your problems guys.

Edited September 19, 20205 yr by Nyxx

3 hours ago, styckx said:

Steps to reproduce:

1. Fly any airplane

2. Just wait

End of steps...

Pretty sure my video, this thread and the official forum thread of countless complaints of this same exact  is enough..

I paid $120 for a simulator to fly planes, not to be a freelance debugger.. 

Like someone else said, I do not have this problem.  I have flown many hours since the second patch without Issues.

1 minute ago, Jetman67 said:

Pretty sure I was using a vrinsight panel to control the autopilot last night with Linda and fsuipc running, was controlling the c172 autopilot with the vrinsight when it happened. I have just done a test for 5 hours just using the c172 autopilot on a flight and it's been flawless, I will do the same flight tomorrow using the vrinsight hardware, I have even been switching to the c172 glass via Dev mode and doing some autopilot diversions off and back to track and just perfect

This is the crazy thing with programs as complex as this..  it's way to easy to just get odd things happening on one system rather than all which makes tracing things really difficult..  it's also very difficult to determine if a change has relly affected something, or you think you see something different from what you were expecting and read that as a new problem or improvement 🙂

I will go and try fly today and see what my incidence of failure is (if any) and try a few more things, but it is also possible that something like this may be corrected without even a download, so who knows 🙂

Graham