(Edited the below to change from a question to more of a checking my logic kind of thing.)

It'd be nice to have the aileron rudder interconnect work like it is designed to, and I think figured out a solution. The reason for this effort is that all of my other planes I have mapped in AAO for everything and this one plane currently needs to have the aileron and rudder mapped in-game so I have to switch the binds every time I switch planes. Here's what I've sorted...

Set rudder axis to a float output from -1 to 1 and have it go to L:ARI_RUDDERINPUT.

Set aileron axis to a float output from -1 to 1 and have it go to L:ARI_AILERONINPUT

Everything looks great and even blends in sim, but I know one other variable changes due to the blending of these axis and its L:HANDLING_AileronRudderInterconnect. Currently that does not update like it should and my guess is something I can't see would be broken. What I've found in their files (and seems to match the behavior in the sim) is this code:

(L:ARI_RudderInput, Percent) abs (L:ARI_AileronInput, Percent) abs max (>L:HANDLING_AileronRudderInterconnect, Percent)

Basically look at the absolute value of both axis and set the variable to whichever is biggest. So what I've done is create an airplane automated script to run at 50ms with the above line and it seems to work. So I'll continue testing but if anyone else is fiddling with this idea it might be a way to handle it and keep all things in AAO (my preference).

Edited May 10, 20251 yr by HadronFlux
Changed from a "how do I do" to a "I'm trying this".

3 hours ago, HadronFlux said:

Set rudder axis to a float output from -1 to 1 and have it go to L:ARI_RUDDERINPUT.

Set aileron axis to a float output from -1 to 1 and have it go to L:ARI_AILERONINPUT

Not sure I agree with that one. These LVars seem to go from -100 to 100

Anyway, an alternative would be to do it all in directly assigned scripts, without the autoscript. Might be beneficial to performance

1. Aileron Script

Group: SWS_PC12
Title: Aileron
Code: (L:SWS_PC12-Aileron)·d·(>L:ARI_AileronInput,·Percent)·abs·(L:ARI_RudderInput,·Percent)·abs·max·(>L:HANDLING_AileronRudderInterconnect,·Percent)

2. Rudder Script

Group: SWS_PC12
Title: Rudder
Code: (L:SWS_PC12-Rudder)·d·(>L:ARI_RudderInput,·Percent)·abs·(L:ARI_AileronInput,·Percent)·abs·max·(>L:HANDLING_AileronRudderInterconnect,·Percent)

Both scripts are then assigned to their respective control using an Int range from -100 to 100. The benefit would be that the scripts are only executed when required (= when control input changes). 

But it doesn't really matter that much - use whatever works for you!