EDIT:

 

Was Able to import the template ok (it Had been a while since I had imported one and forgot about that option) I then merged it with my current profile ok.

 

So Did Some testing.

• Heading Bug script Works Great ✔️
• Implemented your Pitch Wheel Script by using my Thrustmaster Warthog "throttle friction" axis and VS selector on my HC Bravo as the Combo button which works well, it's just a wee bit twitchy though.✔️
• Implemented your Elevator trim wheel script which does work, however, during use, the trim wheel animation spun in the reverse sense! I subsequently modified the following example

...From this!

1 (>K:ELEV_TRIM_DN) (L:f275_Trim_Pitch_Wheel, Number) s0 100 < if{ l0 ++ s0 } els{ 0 s0 } (>L:f275_Trim_Pitch_Wheel, Number)

....to this!

1 (>K:ELEV_TRIM_DN) (L:f275_Trim_Pitch_Wheel, Number) s0 100 < if{ l0 -- s0 } els{ 0 s0 } (>L:f275_Trim_Pitch_Wheel, Number).

It did fix the animation, However, as the Trim wheel traverses the "0" postion in either direction on the trim indication gauge, the wheel animation ceases to function, unless I use my mouse to move it past the "0" postion, it would then once again animate, till of course, it passed the "0" position.❓

Virage/Bank switch/knob. I've Omitted at this stage, though it did work, As its Function is more for Orbiting/Holding/Non Precision Approaches and probably a precursor to the more modern CWS Yoke Button for dodging Thunderstorms etc. I would probably prefer to implement it via a lateral "rocker" switch on my HC Yoke, as I don't have any hardware with a laterel style axis and would be counterintuitive. 

 

9 hours ago, Torkermax said:

Script AP VS wheel:

VS INC

(L:F275_AP_Pitch_Wheel, Number) ++ dnor (>L:F275_AP_Pitch_Wheel, Number)

VS DEC

(L:F275_AP_Pitch_Wheel, Number) -- dnor (>L:F275_AP_Pitch_Wheel, Number)

I did try this Script on my HC bravo Throttles using the rotary and VS selector combo. It did kind of work and would probably prefer the setup, But, when the pitch wheel traversed past the "0" position on the dial, it wound the dial instantly down to 12 max position putting the aircraft into an almost unrecoverable Dive! thankfully I had some altitude below me when I did the test, So I probably won't use that one lol! 😆

 

Sorry Lorby, I could see you replying to my previous post as I was typing this, But I just wanted to get this out there, incase others are trying to script this brilliant little Fokker!.....and I type awefully slow lol.

 

 

 

Edited December 1, 20241 yr by toucanair

56 minutes ago, toucanair said:

(L:F275_AP_Pitch_Wheel, Number) ++ dnor (>L:F275_AP_Pitch_Wheel, Number)

56 minutes ago, toucanair said:

I did try this Script on my HC bravo Throttles using the rotary and VS selector combo.

I'm afraid that this script is wrong. dnor forces a value range between 0 and 359, while the LVar would require a range of -46 to +46

Like this:
UP
(L:F275_AP_Pitch_Wheel, Number) 46 < if{ (L:F275_AP_Pitch_Wheel, Number) ++ (>L:F275_AP_Pitch_Wheel, Number) }

DOWN
(L:F275_AP_Pitch_Wheel, Number) -46 > if{ (L:F275_AP_Pitch_Wheel, Number) -- (>L:F275_AP_Pitch_Wheel, Number) }

Just be mindful how this works. A bigger number also means higher pitch. You could IMO also just assign a fixed number to force a certain pitch value every time you want to climb or decend. Not sure.
UP
20 (>L:F275_AP_Pitch_Wheel, Number)

DOWN
-20 (>L:F275_AP_Pitch_Wheel, Number)

56 minutes ago, toucanair said:

1 (>K:ELEV_TRIM_DN) (L:f275_Trim_Pitch_Wheel, Number) s0 100 < if{ l0 -- s0 } els{ 0 s0 } (>L:f275_Trim_Pitch_Wheel, Number).

That is not correct. Using the script like this can make the LVar go below 0, which the animation LVar does not support. The LVar must stay between 0 and 100 or things will go wrong. To reverse the direction of the wheel rotation, just reverse the K: event at the beginning of the scripts.

1 (>K:ELEV_TRIM_DN) (L:f275_Trim_Pitch_Wheel, Number) s0 0 > if{ l0 -- s0 } els{ 99 s0 } (>L:f275_Trim_Pitch_Wheel, Number)

1 (>K:ELEV_TRIM_UP) (L:f275_Trim_Pitch_Wheel, Number) s0 100 < if{ l0 ++ s0 } els{ 0 s0 } (>L:f275_Trim_Pitch_Wheel, Number)

 

In all these cases I suggest taking a look at the actual behavior code, using MSFS Developer Mode.

1. Activate Developer Mode in MSFS

2. Open "Tools->Behaviors"

3. Click back into the simulator window, hover the mouse over the button/knob/lever you are interested in and press Ctrl + G

4. In most aircraft this will bring up the behavior code of that component. In there you will find "...Interaction.." or "..mouserect..." elements which contain the RPN code that is executed when you are using the mouse. That is the code that you want to replicate in AAO. All my findings above were taken from there.

Notes about how to deal with behavior code:
- You cannot access O: or I: variables. In most cases you can work around them, but there are isolated components where this is not possible - as a consequence this component cannot be operated from the outside at all, only with the mouse.
- LVars need a Unit when you use them in AAO. The safest bet is just adding the default Unit ", Number". So (L:somename) in the sim becomes (L:somename, Number) when you use it in AAO.

 

 

Edited December 1, 20241 yr by Lorby_SI
Corrected the pitch wheel scripts

Thank you for all your guidance, I managed to get the Fokker scripted and functioning beautifully, I just have been busy at work lately and only now have found the time to reply.

I had in the past opened developer mode in the behaviour debug section to see what switches are assigned to etc.

Is there any way to say copy paste data from the logger to the AAO scripts editor, as right now I want to try and edit a few scripts for the MSFS2020  DC Concord Autopilot rotary knobs, which seem quite complex to edit.

The ones I'm interested in are:

• HDG/TRK rotary Knob, Increase - Decrease
• Altitude Select, Increase (By "100's")
• Speed Select Knots rotary knob, Increase - Decrease
• AP Vertical pitch selector (down on the pedestal) Nose down - Nose up.

 

Any guidance for the above is truly appreciated.

though in hindsight this should probably be in a new post

 

Kind regards, T

 

5 hours ago, toucanair said:

Is there any way to say copy paste data from the logger

Not in MSFS2020.

In MSFS2024 you sometimes get a right-click context menu with a "copy to clipboard" entry. But that doesn't seem to be everywhere consistently.

5 hours ago, toucanair said:

Any guidance for the above is truly appreciated.

Sorry, I don't have that plane installed anymore. My MSFS2020 got nuked when Microsoft ended the beta program, and I haven't got around to reinstalling everything (plus, everybody is on 2024 now anyway).

6 hours ago, toucanair said:

Any guidance for the above is truly appreciated.

Check out this package, it contains a script file that you can import into AAO - at first glance it should have most of the items you need.

DC Designs Concorde - Streamdeck XL Profile for Lorby's AAO for Microsoft Flight Simulator | MSFS

Never mind that it was made for the StreamDeck - scripts are usually hardware-agnostic. Just ignore the StreamDeck part, you only want to import the script XML file.

Edited December 14, 20241 yr by Lorby_SI