toby23

For anyone else looking for the Script code for the Honeycomb Throttle far right axis lever using the Flight Sim Factory E-Jet detent insert, here you go. Assign the axis to 'Select Event' and choose the script. I saved this Script as 'FlapsScriptRange'. (L:Fenix-FlapsScriptRange)·s0· l0·0·>·l0·5·<·and·if{·1·(>K:FLAPS_UP)·} l0·7·>·l0·15·<·and·if{·1·(>K:FLAPS_1)·} l0·20·>·l0·25·<·and·if{·1·(>K:FLAPS_2)·} l0·30·>·l0·35·<·and·if{·1·(>K:FLAPS_3)·} l0·40·>·l0·45·<·and·if{·1·(>K:FLAPS_DOWN)·}

Thank you for your help.

In the Fenix A320, the assignment, "Flap Handle" does not work, at least I have not got it to work. I need to use "Axis_Flaps_Set" for it to move the lever in the sim. All I am trying to do is set an axis lever on the Honeycomb with custom detents to match the position of the flap lever in the sim. How can I do that?

Lorby, I am now trying to set up an axis for flaps with detents in the Fenix A320. I have a custom plastic insert from Flight Sim Factory for the Honeycomb yoke with detent markings. I would like to set each detent for the Flaps Axis. The detents are in custom positions and I do not need the whole range of the axis either. While trying to set up the axis in AAO, I have just spotted what you thought was '163 flap detents' in my earlier message, it's actually an entry for the value 16384. The only way I can find to edit this value is by right-clicing on the grey value box in the AAO axis assignment. (2 grey boxes at the bottom of each axis with -16384/16384). Q. How do I set up an axis with custom detent positions if I don't want to use the whole axis range on the Honeycomb Throttle? Thank you

Great idea, thank you for showing me how to do this. It works well.

Would you mind showing me a screenshot of how you entered the code in Stream Deck, or did you test directly in AAO?

I'll give that a try, thank you. Below is a screenshot of part of my conversation with the developer from Black Square, that hopefully helps explain this in more detail.

I don't understand what you mean by "others"? If I enter this script in the "Read" field, it should test which mode is active and return either a 0 or 1, This is the script: Can you see why it wouldn't work?

In the Black Square Starship, there are 4 vertical speed modes: IAS, IASP, DES and V/S. The developer kindly shared their RPN code used on the buttons in the aircraft. I have V/S working but not IAS (IASP) and DES. I am making a Stream Deck profile for the Starship and have created working dials for Airspeed and V/S but cannot figure out how to read the 'situation' to turn a button on or off. Using AUTOPILOT FLIGHT LEVEL CHANGE, bool (for example), turns on both buttons as there is no 'check' as per script above. I normally read the SimVars such as A:AUTOPILOT VERTICAL HOLD, Bool to get a response but this doesn't work in the Starship for IAS and DES mode. I have tried adding the code above as an S: Script to the entry field but it doesn't work and I cannot figure out why and kindly ask for your help. Finally, when rotating the dials, sometimes the numbers changes (they always change in the aircraft) but they often 'stick' on the Stream Deck and don't update, any idea why? Example:

I found out that the Throttle Cut assignment, assigned to Button 24 will set the Throttle to GND FINE (0.0), so that's one thing solved.

I have the Honeycomb Throttle and I would like to set Button 24 (at bottom of axis) to 'set throttle 1 axis to 0.0' to activate GND FINE mode in the Black Square Starship. The throttle is programmed by the developer so that: 0.0 to 0.15 = GND FINE only 0.15 to 1.0 = IDLE - 100 (starts at 15%) -0.1 to 0.0 = Reverser Q1. How can I achieve the following two options? Option A: Set Button 24 to Set Throttle Axis to 0.0 to activate GND FINE mode? Option B: Set Button 24 to Set Full Reverse Thrust? Q2. If I adjust 'Input ranges: Center:' to 1%, I activate the full range of throttle axis from full reverse to full forward, why? Thank you Throttle Range GND FINE to 100 Throttle Range IDLE -100 Throttle Range Full Reverse to 100

Appreciate you are trying to help but why is it so complicated to send a series of keyboard inputs? I could do this easily with the Thrustmaster Target software 15 years ago. All that I am trying to do is this... Press Button = Pause Track-IR > View Custom Camera Press Button again = Unpause Track-IR > View a different Custom Camera Surely something that simple can be accomplished with AAO easily?

Ok, as I find RPN really difficult to understand, could you please give me an example based on my chain? So that I can learn how to use RPN? I don't understand how to send keyboard commands in an RPN script. I have read this doc at the SDK page but it has not answered my question. https://docs.flightsimulator.com/html/Additional_Information/Reverse_Polish_Notation.htm thank you

I am trying to work out how to chain multiple commands together. For example, when I press button 1, I want it to send CTL+F12, followed by Numpad 6. When I press the same button again, I want it to send CTl+F11, followed by Numpad 5. How do I achieve this?

Ok, I shouldn't do this kind of thing late at night... I found it in the Community folder inside the other supplied folder...

I have just installed this addon for the FFX P180 (thank you) and pressing the buttons does have an effect on the in-game FMC but I cannot see anything on the 'screen' in the browser (Firefox) on my local computer. According to the Read Me, I am missing the "zzz-lorbysi-aao-ffx21" folder. Where can I find this?

Ok, thanks for clarifying that. Looks like I will have to use MSFS for some commands then. At least the 'General' keybinds don't seem to disappear like the 'Aircraft' ones do. Thank you

Lorby, I have tried looking for 'Translate Cockpit View Backward' in AAO's input menu but there's nothing there. How do I populate the menu with default MSFS actions like this one, if I want to rebind default keybinds?

As always, I appreciate your help understanding how to better use AAO, thank you.

After losing random bindings after updating to SU2, I would like to use AAO for everything moving forwards. 1. I know how to save and link a master template but I haven't figured out how to edit the assignments, or add more, if I am in a different livery/aircraft to the one that the master template was created in. Is this possible? 2. If I create a general set of controls e.g.throttle axis, gear up/dn etc, how can I use this as a baseline and then add custom controls for specific aircraft e.g. Condition Lever for Turboprops? 3. What I am struggling with is how to create, save and then apply a master template over multiple liveries without having to select it for each livery. And then add custom controls on top of the master template. Thank you

This fix might help you too then if you have a similar setup. Something has changed in SU2 with regards to how the sim processes monitor refresh rate. I don't know what but I have found a fix for these new 'SU2 juddery stutters'. https://forums.flightsimulator.com/t/for-anyone-struggling-with-stuttery-flickering-using-head-tracking-in-su2/721115

Well, it looks like I might have found the problem and a fix... If you have multiple monitors, I have 2, and they run at different refresh rates, you might get this SU2 specific stuttery head tracking. I've put the solution that works for me here: https://forums.flightsimulator.com/t/for-anyone-struggling-with-stuttery-flickering-using-head-tracking-in-su2/721115

Something has changed in either the latest Nvidia Driver or in the MSFS 2024 code to cause this. I see it since updating to SU2 and I saw it in the Beta as well, with a different Nvidia driver. Switching to FSR3 FG does fix it but that isn't the solution. Strangely, turning off DLSS and FG doesn't fix it either, which is why I suspect something in SU2's code changes is causing this. Head tracking with Track-IR has become quite juddery since updating to SU2 and it was smooth before. Hoping that Asobo/Nvidia can find a fix asap for those of us who use head tracking.

That works! Thank you

Hmm, not sure where I have gone wrong but neither of those options are triggering the button action.