Engine degradation

touchdown42

Hi,

after a long time i had a long flight with the analog Bonanza today, lots of shorter hops with landings on several smaller strips and i lost ~8% engine during the trip. I tried hard to not abuse the engine so i think it is related to the bug described in the older thread.
Question: is a patch on the horizon?

Another glitch i noticed is that the first press of AUTOPILOT DISENGAGE SET disables the autopilot but the second press doesn't disable the FD.
It works if i press the button on the stick with the mouse.

thx

kakugo

Does it work if you use AP_MASTER?

touchdown42

No, then the second press simple reengages the auto pilot.
I had another flight this weekend, through heavy weather, mostly in the clouds.
Probably completely unrealistic but i lost about 10% engine health during the 1hr flight, perhaps due to quick altitude changes

GunStrauss

Any news on this issue?

Black Square

The engine degradation was likely caused by a bug that could cause severe turbulence or pitch changes to rapidly cool the cylinders. I fixed this for the Baron, but have not pushed an update for the Bonanza that contains this fix yet. I apologize that it's taken me so long. I keep creating new features for my newer aircraft that I want to bring back into the older ones, so I rarely have a good milestone from which to to release an update.

The flight director will only disable on the second press with the in-cockpit autopilot disconnect button. Overriding the behavior of default events, such as AUTOPILOT DISENGAGE SET is a tenuous feature in MSFS, as it will often break the behavior for people who use the default bindings that ship with many commercial peripherals, particularly the Honeycomb series. If you would like to program this yourself in SPAD, or FSUIPC, you could use the following expression:

(A:AUTOPILOT MASTER, bool) ! (A:AUTOPILOT FLIGHT DIRECTOR ACTIVE, Bool) and if{
(>K:TOGGLE_FLIGHT_DIRECTOR)
}

Randolf

@Black-Square thank you, I was also wondering about that. But I think the expression is missing the part to turn off the autopilot with the first click. I changed it to

(A:AUTOPILOT MASTER, bool) if{
  (>K:AUTOPILOT_OFF)
} els{
  (A:AUTOPILOT FLIGHT DIRECTOR ACTIVE, Bool) if{
    (>K:TOGGLE_FLIGHT_DIRECTOR)
  }
}

Black Square

Yes, that is exactly what you will need to implement the autopilot disconnect button. Sorry, I just gave you the code for the second press.