Skip to content
  • Altitude Programmer: Baro setting issue and a question

    Commander 114
    9
    0 Votes
    9 Posts
    125 Views
    SadBucketS
    @Black-Square I'm happy to make little tweaks like this on my own, I just always assume it's way harder to do lol
  • Trouble with S-TEC altitude/vs select programmer

    Commander 114
    5
    0 Votes
    5 Posts
    31 Views
    R
    Thanks for the clarification, didn't realize the BARO was only 3 units, that probably explains what was going wrong for me. I put in 30.17 and 3.5 for example thinking that was 3500 feet, but I was actually specifying 73,500 ft!
  • Missing LVARS for EDM800 Engine Monitors

    Commander 114
    5
    0 Votes
    5 Posts
    78 Views
    S
    Argh, I don't know how I missed the "H:" in front instead of "L:". Expectation bias?! Anyways, in Spad, you simply create "Client Events" For HTML events that aren't already present. The SPad team will often add HTML events upon request for planes, but this is very easy to do. Screen shot below for anyone else wanting to do this, ignore the first entry. Nothing to configure, just paste the event names from the manual as shown. These work fine, though the buttons don't move (maybe I'll dig in the developer tools someday to see if that's possible). Thanks as always, Nick! [image: f98ac399-a133-4abc-ad26-19e57c019d48.png]
  • 1 Votes
    5 Posts
    46 Views
    S
    Yes, my observation is based on the horsepower indicator. As far as I can tell, the indicated power decreases progressively by several percent as altitude increases, even below the critical altitude, rather than merely fluctuating by 10–15 hp during the climb. I’ll verify this in stabilized level flight at several altitudes, using the same manifold pressure, RPM and full-rich mixture, and report the exact values.
  • Expansion of failure configuration page

    Commander 114
    2
    0 Votes
    2 Posts
    53 Views
    Black SquareB
    Hey, there! What a wonderful project! I might recall your suggestion a while back. I'm sure there were a few with that idea, because it's a good one. It's really interesting to see what can be done with AI now too, and always amusing to see that someone has been earning my code, just as I've learned from others my whole life too. Excellent work! I hope you don't misinterpret my delay in responding to mean anything other than that I've been busy. In reality, I've been trying to think of how to respond most appropriately. It's quite difficult as a developer when something this good comes up, because it seems like a poor choice not to add it for everyone who would enjoy it; however, it also might be a little daunting for less than the top ~1% most experienced users. Of course, then there is also the technical challenges of adapting it to all my aircraft, documenting, and maintaining it. Ideally, I would love to offer something like this as a free download for those who are interested, because it would allow me to maintain it separately from the aircraft (every aircraft updated is several days of work for me and the Just Flight team, adding up to about two weeks of work to update my entire fleet), and also because I think it would allow others to treat it as an "experimental" feature, whereas anything included with the aircraft is expected to approach perfection, at least in my eyes. Would you have any interest in creating this as a mod that could be added to the aircraft? Clearly, it would be best if it was modular, since updating the entire tablet every time the aircraft is updated is a recipe for support tickets. Ideally, it would be a new set of files that are dropped in the same place in the virtual file system, and then probably a modification to the main HTML to add the JS, which is okay, because the HTML shouldn't really change after an aircraft is released. I know that would be a lot of work, but it would be a lot less work than it would be for me to maintain with official support, which is why I recommend it. If I don't have the bandwidth to support this feature, it might never happen, but it would be sad to never see it happen because of it! I hope you understand and that this doesn't sound like a dismissal! I'm very impressed, and would love to see what we could do together, on this, or any other part of my aircraft you take an interest in! I'm just doing my very best to manage expectations.
  • Invisible Copilot

    Bonanza Professional
    3
    0 Votes
    3 Posts
    34 Views
    Black SquareB
    @2LOW That option was left in by mistake in the MSFS 2024 version. However, it will have no effect on inserting your own 2024 characters using navigation_graph.cfg. @toby23 Did you try using the same interactiveObject and ANIMATION_SIT as the pilot?
  • Commander Screenshots

    Commander 114
    4
    0 Votes
    4 Posts
    41 Views
    EsotericE
    @MatzeH84 said in Commander Screenshots: I took my Commander from Germany around the French Alps down to Italy, currently overnight near Florence. I'll have to remind myself to do some Screenshots as well. Turin area is magnificently photogenic.. Looking forward to seeing that!
  • Noise Cancelling Headphones - Clickspot missing

    Commander 114
    7
    0 Votes
    7 Posts
    182 Views
    Black SquareB
    @Raller That's handled on the Asobo end of things, so nothing we can do about it, I'm afraid.
  • Turbo - No Fuel Flow

    Commander 114
    25
    0 Votes
    25 Posts
    436 Views
    Black SquareB
    @Voxen Send a video, if you could.
  • Impatient Pilot Waiting for the Next Update

    Commander 114
    1
    0 Votes
    1 Posts
    32 Views
    No one has replied
  • Autopilot events in manual correct? VS Mode?

    Commander 114
    12
    0 Votes
    12 Posts
    153 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
    66 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
    947 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
    368 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
    32 Views
    No one has replied
  • 3D model antenna modelling

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

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

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

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