Skip to content
  • Autopilot events in manual correct? VS Mode?

    Commander 114
    12
    0 Votes
    12 Posts
    170 Views
    F
    I'm glad to hear the autopilot scripts worked. I am still finishing my complete Commander 114 MobiFlight project, so I am not ready to share the full project file yet. However, here is a bonus for anyone using the Honeycomb Bravo Throttle Quadrant. I configured the Bravo’s left selector knob to determine what the right knob controls. MobiFlight has a guide explaining how to configure the selector variable and use it as a precondition: https://docs.mobiflight.com/guides/honeycomb-bravo-selector-knob These are the selector values I am using: ALT = 0 VS = 1 HDG = 2 CRS = 3 IAS = 4 I repurposed the Bravo’s IAS selector position for the Commander autopilot’s BAR setting. For each right-knob input, add the appropriate Selector value as a MobiFlight-variable precondition. Place the code under On Press and leave On Release blank. ALT SELECTOR Precondition: Selector = 0 The altitude control normally moves in 100-foot increments. These versions measure how quickly the right knob is being turned: Slow rotation: 100 feet per click Medium rotation: 500 feet per click Fast rotation: 1,000 feet per click Right Knob - ALT Increase (E:SIMULATION TIME, seconds) (L:MF_ALT_LastIncTime, seconds) - 0.08 < if{ 1000 (>L:MF_ALT_Step, number) } els{ (E:SIMULATION TIME, seconds) (L:MF_ALT_LastIncTime, seconds) - 0.20 < if{ 500 (>L:MF_ALT_Step, number) } els{ 100 (>L:MF_ALT_Step, number) } } (L:var_PreselectedAltitude_10000, number) 10000 * (L:var_PreselectedAltitude_1000, number) 1000 * + (L:var_PreselectedAltitude_100, number) 100 * + (L:MF_ALT_Step, number) + 99900 min (>L:MF_ALT_New, number) (L:MF_ALT_New, number) 10000 / flr (>L:var_PreselectedAltitude_10000, number) (L:MF_ALT_New, number) 10000 % 1000 / flr (>L:var_PreselectedAltitude_1000, number) (L:MF_ALT_New, number) 1000 % 100 / flr (>L:var_PreselectedAltitude_100, number) (E:SIMULATION TIME, seconds) (>L:MF_ALT_LastIncTime, seconds) Right Knob - ALT Decrease (E:SIMULATION TIME, seconds) (L:MF_ALT_LastDecTime, seconds) - 0.08 < if{ 1000 (>L:MF_ALT_Step, number) } els{ (E:SIMULATION TIME, seconds) (L:MF_ALT_LastDecTime, seconds) - 0.20 < if{ 500 (>L:MF_ALT_Step, number) } els{ 100 (>L:MF_ALT_Step, number) } } (L:var_PreselectedAltitude_10000, number) 10000 * (L:var_PreselectedAltitude_1000, number) 1000 * + (L:var_PreselectedAltitude_100, number) 100 * + (L:MF_ALT_Step, number) - 0 max (>L:MF_ALT_New, number) (L:MF_ALT_New, number) 10000 / flr (>L:var_PreselectedAltitude_10000, number) (L:MF_ALT_New, number) 10000 % 1000 / flr (>L:var_PreselectedAltitude_1000, number) (L:MF_ALT_New, number) 1000 % 100 / flr (>L:var_PreselectedAltitude_100, number) (E:SIMULATION TIME, seconds) (>L:MF_ALT_LastDecTime, seconds) This allows precise 100-foot adjustments when turning the knob slowly, while still making it practical to move from zero to normal cruising altitudes quickly. VS SELECTOR Precondition: Selector = 1 The Commander stores the selected vertical speed in hundreds of feet per minute. These commands adjust it by 200 feet per minute and limit the selection to plus or minus 1,600 feet per minute. Right Knob - VS Increase (L:var_PreselectedVerticalSpeed, number) 2 + 16 min (>L:var_PreselectedVerticalSpeed, number) Right Knob - VS Decrease (L:var_PreselectedVerticalSpeed, number) 2 - -16 max (>L:var_PreselectedVerticalSpeed, number) BAR SELECTOR I use the Bravo’s IAS selector position for the autopilot barometric setting. Precondition: Selector = 4 The Commander stores the BAR setting as three separate digits, so the following code handles carrying and borrowing between them. Right Knob - BAR Increase (L:var_AutopilotBaroCalibration_01, number) 9 < if{ (L:var_AutopilotBaroCalibration_01, number) 1 + (>L:var_AutopilotBaroCalibration_01, number) } els{ (L:var_AutopilotBaroCalibration_1, number) 9 < if{ 0 (>L:var_AutopilotBaroCalibration_01, number) (L:var_AutopilotBaroCalibration_1, number) 1 + (>L:var_AutopilotBaroCalibration_1, number) } els{ (L:var_AutopilotBaroCalibration_10, number) 9 < if{ 0 (>L:var_AutopilotBaroCalibration_01, number) 0 (>L:var_AutopilotBaroCalibration_1, number) (L:var_AutopilotBaroCalibration_10, number) 1 + (>L:var_AutopilotBaroCalibration_10, number) } } } Right Knob - BAR Decrease (L:var_AutopilotBaroCalibration_01, number) 0 > if{ (L:var_AutopilotBaroCalibration_01, number) 1 - (>L:var_AutopilotBaroCalibration_01, number) } els{ (L:var_AutopilotBaroCalibration_1, number) 0 > if{ 9 (>L:var_AutopilotBaroCalibration_01, number) (L:var_AutopilotBaroCalibration_1, number) 1 - (>L:var_AutopilotBaroCalibration_1, number) } els{ (L:var_AutopilotBaroCalibration_10, number) 0 > if{ 9 (>L:var_AutopilotBaroCalibration_01, number) 9 (>L:var_AutopilotBaroCalibration_1, number) (L:var_AutopilotBaroCalibration_10, number) 1 - (>L:var_AutopilotBaroCalibration_10, number) } } } These are working well for me in MobiFlight with the Honeycomb Bravo. The same aircraft variables should also be usable with other hardware after adapting the device inputs and preconditions.
  • trim setting: discrepency

    F70 & F100 Professional
    4
    0 Votes
    4 Posts
    73 Views
    S
    I tried to reproduce it now on sim and TO CG was approx 25 %, so more matching with 1.8, but it's not the first time and the first leg I had this issue. I'll send a ticket if it occurs again.
  • 1 Votes
    45 Posts
    1k Views
    M
    @Black-Square said in Is it maybe possible that the startup procedure is incorrect?: @Flocat89 @Rimshot @ploodovic @Esoteric @jasmits @kityatyi @mburkhard @SadBucket Hi all. After much thinking in the shower, I figured out how to implement this in about six lines of code. Must be a special kind of water supplied to your place! Thank you, well done sir, appreciate your efforts massively! I just went ahead and bought the Commander, even though I'm still waiting for that Virpil yoke that seems to take forever to arrive on the market
  • F100 - ATS and Landing behaviour

    F70 & F100 Professional
    26
    5 Votes
    26 Posts
    4k Views
    V
    Hi all! I had huge problems flying the f100/f70 in real weather. Approach speeds fluctuating wildly and incontrollable aircraft. But, I found a solution in the internet which seems to work on my pc. It’s a windows problem (!). The OS clock synchronization, didn’t work well (but check also DNS and IPv6). It caused MSFS2024 to mess up winds, particularly during last 500 feet AGL of the approach. The link is here: https://forums.flightsimulator.com/t/extreme-crosswinds-and-wind-swings-close-to-the-ground-on-final/728054 Many thanks to paulofranca89!
  • Commander Paintkit

    Commander 114
    14
    0 Votes
    14 Posts
    384 Views
    WooliesW
    @Tim-HH Cool thanks. I think 3.6 is the one I grabbed anyway after reading about the importers. Will check the tutorial, thanks!
  • 1 Votes
    1 Posts
    41 Views
    No one has replied
  • 3D model antenna modelling

    F70 & F100 Professional
    1
    0 Votes
    1 Posts
    28 Views
    No one has replied
  • Beech 1900D

    Black Square Add-Ons
    3
    2 Votes
    3 Posts
    233 Views
    EsotericE
    Hopefully an Alpine Super Freighter variant for the freight dogs))
  • Oil Check on walkaround

    Commander 114
    1
    1 Votes
    1 Posts
    56 Views
    No one has replied
  • Manual typo

    Commander 114
    4
    0 Votes
    4 Posts
    91 Views
    P
    @jmarkows Blowfigures is better. Just simply better. I wont change my mind about that lol!
  • Fuel Totalizer Label

    F70 & F100 Professional
    3
    0 Votes
    3 Posts
    126 Views
    YankeeTendy35Y
    Thanks Mark! Loving the F100
  • State Saving

    Caravan Professional
    4
    0 Votes
    4 Posts
    102 Views
    G
    @Black-Square said in State Saving: This has come up more recently, as it seems that state saving has never been the same since SU4, and it was never particularly reliable to begin with. There are some workarounds that you can read about, and possible causes. Particularly, restarting the flight before quitting to desktop, and disabling anti-virus seems to be the most commonly cited solutions. I've become increasing frustrated with this myself, which is why I have recently invested my time in creating a whole new full state saving feature, which will hopefully provide better consistency, and save nearly every variable in the aircraft. You can read about it here, if you like. Is this new system coming to the previous aircraft, from the Bonanza Professional and upwards, among the other improvements? If yes, do you have a rough time schedule for patches to come? (i.e. before the end of summer...)
  • 0 Votes
    6 Posts
    80 Views
    Z
    I observed now the ILS 400 sometimes (!) loads with saved state from last session (incl. the frequencies). Even the KLN 90B sometimes reloads with the correct on/off state, but sometimes not. Even the state of the wheels chocks. But that could be a MSFS thing (interpreting the start conditions of the session).
  • Run up magnetos check

    Commander 114
    11
    0 Votes
    11 Posts
    176 Views
    V
    @Black-Square That's awesome Nick. Thank you very much. When will the update be available?
  • Commander 114 black tablet screen

    Commander 114
    18
    1 Votes
    18 Posts
    241 Views
    K
    @Fabbi That tip actually worked for me! Thanks again. And the Commander is a great aircraft. Keep it up, Blacksquare! Greetings from EDDP, Arndt.
  • Duke Turbine acceleration issues

    Piston & Turbine Dukes
    3
    0 Votes
    3 Posts
    52 Views
    Z
    @skyseek Maybe a silly question, but are you sure that you removed throttle locks?
  • State saving issue

    F70 & F100 Professional
    6
    0 Votes
    6 Posts
    139 Views
    MarkM
    Even more interesting! We'll continue to monitor this anyway for any trends. Mark - Just Flight
  • 0 Votes
    2 Posts
    63 Views
    MarkM
    Thank you for the feedback. For any AFCAS/ATS related feedback, could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support The F70 & F100 Professional are complex products, so in order to give our support team the best chance at offering speedy assistance, and for any potential bugs to get properly logged and addressed, could you please include any screenshots/videos of the behaviour with your ticket, as well as attaching the log file generated by the product. Instructions for locating the log file can be found here: https://support.justflight.com/en/support/solutions/articles/17000152594-where-to-find-the-log-file-s- Mark - Just Flight
  • seated passengers

    F70 & F100 Professional
    2
    0 Votes
    2 Posts
    64 Views
    MarkM
    Sadly, this is not something we have any control over, and it would be up to the discretion of FSDT to implement on their end. We did contact FSDT about this and several other GSX-related items before release, but we have not yet received a response. Mark - Just Flight
  • Touchdown sound

    C152
    1
    0 Votes
    1 Posts
    16 Views
    No one has replied