Skip to content
  • Commander Paintkit

    Commander 114
    16
    0 Votes
    16 Posts
    726 Views
    T
    @Woolies That looks excellent! Great work
  • 3D model antenna modelling

    F70 & F100 Professional
    5
    0 Votes
    5 Posts
    229 Views
    MarkM
    Thank you for the feedback. We have forwarded that to our artists for further investigation. Mark - Just Flight
  • Fly the Line - Airline Edition

    Pinned Locked Fly the Line
    1
    0 Votes
    1 Posts
    87 Views
    No one has replied
  • Extreme RIse in Cabin Temperature

    Commander 114
    4
    0 Votes
    4 Posts
    239 Views
    R
    Thanks both of you. @Zacke I did observe an extreme version of my issue in a SoCal flight where the OAT was around 100F and of course sunny -- I wasn't surprised by the temp skyrocketing in the afternoon sunlight. But I also do a lot of early morning and early evening flying in places where there's not really a lot of sunlight -- cloudy Southeast Alaska, for example -- that's what made me question it. @Black-Square thanks for confirming it wasn't my imagination. To be honest, cabin temp control flummoxes me in a number of aircraft, and I might fixate on it a bit too much as a result -- probably the main reason I even noticed this, because it put me behind the curve right from the start lol
  • saving/loading wear and tear of the whole aircraft

    Bonanza Professional
    1
    0 Votes
    1 Posts
    53 Views
    No one has replied
  • Help request

    Just Chat
    2
    0 Votes
    2 Posts
    132 Views
    DerekD
    We don't do support via email. However, Black Square do frequent these forums. Otherwise, you can contact Just Flight Support and they will be only too happy to resolve any questions you may have. I think the @ symbol is accepted in common usage on forums and social media to tag other users.
  • Cabin temp indicators

    Black Square Add-Ons
    1
    0 Votes
    1 Posts
    79 Views
    No one has replied
  • Installation Bug?

    Commander 114
    4
    0 Votes
    4 Posts
    221 Views
    S
    @Derek was on the ball - that solved the problem.
  • EDM LOP Leaning is wrong (still)

    Commander 114
    16
    0 Votes
    16 Posts
    700 Views
    D
    Just to tag onto the LOP discussion, leaning LOP really pushes the CHTs up, which is the opposite of what I'd expect-- I'm having to crack Cowl flaps pretty frequently to stay below a conservative 380-- having not flown a 114, I don't know how normal that is. If I lean more LOP, they seem to go even higher and you can lean pretty (probably a bit too?) aggressively before the engine starts complaining. In reality I'd expect CHT to fall off pretty hard anywhere leaner than best power, and the engine should falter sooner once you get past 50F LOP, imo. I'd imagine a lot of this is MSFS being MSFS, but thought I'd share my thoughts anyway. (Edit: I'm in the TN version)
  • AUTHZ_005: Access Denied

    F70 & F100 Professional
    14
    0 Votes
    14 Posts
    678 Views
    S
    Above issue was via EFB. Uninstalling and installing from fresh, inputting the code via the installer fixed this...
  • Closing the doors via the EFB is not working correctly

    TBM 850
    2
    1 Votes
    2 Posts
    177 Views
    Black SquareB
    I can't reproduce being able to close the pilot door on the ladder. There's only one clickspot on the exterior for the pilot's door, and the code is simple, so I don't think there's anything wrong there. It's possible I fixed this a while back and forgot to document the change for myself. I've also now made the tablet buttons first stow the ladders if they are deployed. Then a second press will close the door.
  • Crz alt invalid

    F70 & F100 Professional
    6
    1 Votes
    6 Posts
    260 Views
    G
    The problem had started happening when i joined the SU6 beta, it also gave me issues with the sovereign, switching back to SU5 fixed the sovereign but not the F100, I did a fresh install of MSFS 24 on SU5 today and managed to do a F100 without the issue.
  • Altitude Programmer: Baro setting issue and a question

    Commander 114
    9
    0 Votes
    9 Posts
    357 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
  • Missing LVARS for EDM800 Engine Monitors

    Commander 114
    5
    0 Votes
    5 Posts
    187 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]
  • Expansion of failure configuration page

    Commander 114
    2
    0 Votes
    2 Posts
    123 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.
  • Noise Cancelling Headphones - Clickspot missing

    Commander 114
    7
    0 Votes
    7 Posts
    331 Views
    Black SquareB
    @Raller That's handled on the Asobo end of things, so nothing we can do about it, I'm afraid.
  • Impatient Pilot Waiting for the Next Update

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

    Commander 114
    12
    0 Votes
    12 Posts
    390 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
    164 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
    1 Posts
    81 Views
    No one has replied