Axis and Ohs: Help and questions

[Funatic68]

Thank you for the detailed explanation!

[Renvah]

Not a support request, I just need this to get out of my chest.
After I did stream deck profiles with AAO for few default aircraft I started doing TBM930. Aaaaand sad face. After some digging I found the culprit. BVars. I’ve found out it’s impossible for now and found the other thread " State of affairs when using external controllers - not good (IMHO)".
So I’m just another person not happy with the current state of external controllers support by Asobo.

[bLindyee]

Axis and Ohs: Help and questions

Hello @ll, AxisAndOhs version 2.21 will have the ability to operate BVar controlled input events in MSFS. If you are being held back by the BVar logic too, and are a user of AAO with a bit of experience in RPN scripting, you are welcome to try it and maybe help finalizing the procedure so everybody can use it. Just send a message or email with your proof of purchase to the address on the last page of the AAO manual.

Next AAO version will have support for BVars

[Renvah]

Thanks!
I’ll send a message. Would gladly test it.

[Jambuna]

Hello Oliver,
in one of the posts in June you mentioned a script to translate the pyhsical position of MixtureLevel1 to the logic of the PMDG DC-6. For whatecer reason the name of the first LVAR don’t give back any value beside a zero. I have tested with and without the assignment of the mixturelever1 axis to a joystick axis?
Was there a change during the last updates of the PMDG?

(L:DC6-MixtureLever1) flr (L:dc6_400_obj, Number) > if{ 40007 (>K:ROTOR_BRAKE) } (L:DC6-MixtureLever1) (L:dc6_400_obj, Number) < if{ 40008 (>K:ROTOR_BRAKE) }

Is there another VAR to get the value of the physical position of the Mixturelevers?

Regards
Michael

[LorbySI]

(L:DC6-MixtureLever1)
is the “script variable”, it contains the value that is being sent from the axis assignment. This one will only work when your script is in the group “DC6” and is named “MixtureLever1”. If you are using a different group or script name, this variable must be renamed accordingly. Example: if your script is called “Fred” and it resides in the group “Flintstone”, then the script variable is (L:Flintstone-Fred)

[Jambuna]

Thanks a lot - the group name did it.

[plerzelwupp]

Hello,

thanks a lot for the software. I learned a lot in the past months.

One short silly question: Is there a possibility to easy delete the special character center points (interpunct for spaces) in scripts? It could possibly be the goal that these special characters are optionally not copied, but only displayed? This could be a small relief for the daily workflow.

[IanoFX]

Hi Oliver, I tried to add an AOA gauge to my Saitek FIP. Sadly the needle does not behave as expected.
This is the code for the needle a added to the PFD.xml:

When I am in the world map AOA is 0 and my needle is at 350°, when I start a flight and the aircraft is still on ground AOA is 180 and my needle is at 315° - as expected. But after take-off with AOA values in the 170s or 160s I was expecting the needle to move clockwise in the 320° range. But it does the opposite, moves into the 310° range. What am I doing wrong here?

[LorbySI]

@plerzelwupp

Is there a possibility to easy delete the special character center points (interpunct for spaces) in scripts

Why, what is your use case? When you copy code between different scripts, the editor should treat the dots correctly (it expects them). And when you post code online, it is easier to get right for other people. Only when you copy script code into another app the dots would matter.

[LorbySI]

@IanoFX

What am I doing wrong here?

Not sure. Did you check the AOA value range? There is a good chance that it yields negative numbers, and that you have to add a dnor or something. Try querying the variable when you are in the air with the “Test” button and observe the actual values.

[IanoFX]

@LorbySI

Did you check the AOA value range?

Thanks for your response. I have the AOA value on a Stream Deck text gauge. While in air it is in its 170s and 160s. I never seen it becoming negative. However, technically I didn’t need nonlinearity, I just needed a scale and an offset. I achieved that by switching from degrees to radians and multiplied my scale factor and added my offset in the value definition. Problem solved.

[Slarti42Bart]

Hey guys, does anyone have a solution for changing the map zoom in the MFD of the Kingair 350?

I’m using

1·(>H:AS3X_Touch_1_knob_inner_r_inc,·Number)

in other planes, but this one does not have that knob, and it is not working.

Thanks for your help!

[LorbySI]

@Slarti42Bart

1·(>H:AS3X_Touch_1_knob_inner_r_inc,·Number)

Hi, looking at the code in the behavior definition file, I think that the the instrument ID is “2” in this case. Did you try 1·(>H:AS3X_Touch_2_knob_inner_r_inc,·Number) ?

On the other hand, the code leads into Templates that are based on B: vars, which is not a good sign.

[Slarti42Bart]

Thanks for the tip, I did try that already. No luck. The first display can be also split to show a map and my sample does not work there either…

[bLindyee]

Unfortunately touch screen functions cannot be used outside of the sim. At least not yet, feedback has been given and hopefully someday it’s possible.

[Slarti42Bart]

Thanks for letting us know!

[Slarti42Bart]

Are you still looking for testers for the new version supporting BVars?

[LorbySI]

@Slarti42Bart

Are you still looking for testers for the new version supporting BVars?

Many thanks for the offer, but we have just decided to release it…

[Slarti42Bart]

No worries Will be testing the next version maybe Have a great weekend