The AAO dropdown list contains Throttles 1 to 4, but I haven't been able to map the specific un-numbered  "Throttle" axis with it.

I admit it's not an issue with most aircraft, but MsFs seems quite pedantic with that particular axis with certain aircraft, like their "Volocopter" and some helicopters.  The Volocopter's flying height adjustment (altitude) works when assigned via the Sim itself to the "Throttle" axis, but not "Throttle 1", or via AAO's "Throttle 1".

Is there another simple way to assign it with AAO that doesn't involve coding ?  (I quickly get out of my depth with that !)

7 hours ago, glider66 said:

Is there another simple way to assign it with AAO that doesn't involve coding ? 

Use the event selection, the second box from the top on the axis assignment dialog.

If the axis variables don't work, the Events usually do. Filter for "throttle" in the treelist. The MSFS defaults are those that end on _EX1 (like THROTTLE1_AXIS_SET_EX1), but any of the others might work too for a particular aircraft.

Edited April 22, 20224 yr by Lorby_SI

Thanks again for another very prompt answer.
I'll give it a try and reply again with the result.

I tried setting my throttle lever to THROTTLE_AXIS_SET_EX1, but it still couldn't move the height control in the Volocopter.
I then used MsFs to assign the same lever to the Throttle Axis, and it worked ok.

I tried the numbered throttle axis as well in AAO's simulator events, but there was no movement with them either.

It would be handy if there was a way to assign it using AAO, because then your nice feature of remembering it for just that aircraft would really come into play, rather than me having to enter MsFs's Control settings interface to change that assignment eacch time I switch to or from the Volocopter, (and any other aircraft that might be so pedantic about needing "Throttle" rather than "Throttle1".

You mean that Microsoft "Volocity" thing, from the MSFS default vehicles? The "collective" in that one is not controlled by an axis. I had to do this by manipulating an LVar.

The thing to understand with MSFS is, that there is no correlation between those things that you can configure in the in-sim controller management and that what it lets you do over the SimConnect API. The Events and Axis from the SDK that you see in AAO may sound similar in name, but there is no direct connection of any kind between them and the controller setup in the sim. It is entirely possible that this particular model is mapping the input axis that you assigned to Throttle to one or more BVars that do something completely different in the behavior logic than a SimConnect program would expect.

On my computer I had to map the up/down/middle movement of that rocker switch on the Volocity joystick to buttons. It wouldn't work any other way. And for those assignments I had to make RPN scripts:

Go Up
1·(>L:XMLVAR_VOLOCITY_COMMANDED_VERTICAL_SPEED,·Number)·

Go Down:
-1·(>L:XMLVAR_VOLOCITY_COMMANDED_VERTICAL_SPEED,·Number)·

Go Middle:
0·(>L:XMLVAR_VOLOCITY_COMMANDED_VERTICAL_SPEED,·Number)·

And that is assigned to two buttons (a trim rocker switch on my yoke) by using the go up/go down scripts as the Down Event and the go middle script as up event. So I can steer up and down by flipping that switch like I would use a trim. Seems realistic to me, because in the VC it is a rocker switch to and not a collective lever that would correspond to an axis.

Edited April 22, 20224 yr by Lorby_SI

Correction: I just remembered that I can do this with an axis and an RPN script too

Script group: Volocity
Script name: Collective
Script code: (L:Volocity-Collective)·(>L:XMLVAR_VOLOCITY_COMMANDED_VERTICAL_SPEED,·Number)

Then assign this script to the desired axis control and set "Axis Min" to -1 and "Axis Max" to 1 
(doubleclick in those textboxes to input the values with your keyboard, no need to spin the mouse wheel excessively)

Edited April 22, 20224 yr by Lorby_SI

Thanks Lorby, 

I completely understand the point about the Volocity's "collective" being an up/down toggle switch rather than a true axis.

I did originally think it was certain to be a pair of 'press to hold' switch inputs, one up, one down, since as you say, that's how it's displayed on the stick in the 3D cockpit  view.  What was confounding that though was the way it was working as an axis using MsFs's built-in control assignments.

I'll set it up with your script,  thanks for showing it.

I had to smile at your expression Volocity "thing"  🙂

I guess it must be the last thing a serious sim pilot would be seen in, but I find it handier for inspecting scenery than the remote drone. (That's my excuse anyway...)

 

Thanks Lorby, the script for the axis control works perfectly,  (and now I can begin to see how they work too 🙂)

I sorted my throttle deadzone too, (after reading the help file more carefully).

I added a profile, (fast increase, then normal), so now the MsFS throttle lever starts to move almost at the same time as I move the axis lever on my GVT throttle control.

 Your AAO program accurately sees the entire movement range of my throttle, whereas the sim was only starting to respond after it passed the halfway mark.