Leaderboard

The speed brake not complete down thus trigger the TO config warning is quite common IRL on a 737....

Exactly. IXEG733 has a problem (bug) with resetting the parameter: "sim / flightmodel2 / controls / speedbrake_ratio" even with the Speedbrake lever fully retracted. It is also very annoying when using the XPRealistic add-on - if onces you use the speedbrake, the cockpit will never stop shaking again ;-) My simple and tiny lua script eliminates this inconvenience: TB_IXEG_Speedbrake_off.zip I think it will also solve HeliMaf's problem

Thank you all for helping out! As soon as I have time I will test all of your suggestions and give a feedback.

Hi and thanks for the kind words! I suspect - and this is just a hunch - that the speedbrake does not registers as "completely down", or the flaps are not "exactly" in 1 or 5 - this sometimes happens with hardware "axis" assigned to those functions, instead of buttons or keyboard presses. To "test" this you could a.) display the values for flaps and spoilers using the "data out" function - it will show you the exact values for those flight controls in green numbers on screeen and/or b.) unassign thoses axis (temporarily) in the setup of your Honeycomb hardware and operate those controls with buttons or key presses (or the mouse in the virtual cockpit) and see if that makes a difference? Another thing to test is pushing the thrust levers forward really quick during taxi-out before your second take-off - just to test for the takeoff warning - it beats finding out about the problem earlier than in the middle of your take-off run ;-) Let me know how that works? Cheers, Jan

There is no way to know this for certain. So far the plane loads and flys in v12. But, Austin has made engine model changes that we do not have yet. I am hoping that any changes will be minor and be part of a free update if necessary.