Axis and Ohs: Help and questions

Discussion Hub Tools & Utilities
1787

Is there a way to assign the drone camera actions to the X Touch Mini with AAO? I want to use the rotary dials to go up, down, right, left, etc.

1788

Hi,
I would like to increment and decrement the Glareshield Lights in the DA40 using a rotary knob of Xtouch Mini and I suppose is possible with an RPN script.

Watching simulator events I understood that the relative event is

GLARESHIELD_LIGHTS_SET (0 is OFF and 100 full light)

Is there someone who can help me on how to create the related RPN script?

Thanks
Stefano

1789

IIRC that is only for turning it on or off, not for dimming.

Try these instead

25·(>K:LIGHT_POTENTIOMETER_5_SET)
50·(>K:LIGHT_POTENTIOMETER_5_SET)
75·(>K:LIGHT_POTENTIOMETER_5_SET)
100·(>K:LIGHT_POTENTIOMETER_5_SET)
1790

Thanks for your answer 
 however what does it means IIRC? Just for my understanding.

And how can I use these settings? Inside a RPN script?
25·(>K:LIGHT_POTENTIOMETER_5_SET)
50·(>K:LIGHT_POTENTIOMETER_5_SET)
75·(>K:LIGHT_POTENTIOMETER_5_SET)
100·(>K:LIGHT_POTENTIOMETER_5_SET)

Thanks for your help
Stefano

1791

“If I Remember Correctly” (= I think that I have seen it before)

Depends on what you want to do. With the rotary encoder, you would create a script like this:

Scriptgroup: DA40Lights
Scriptname: PanelLightDimmer
Script code: (L:DA40Lights-PanelLightDimmer) (>K:LIGHT_POTENTIOMETER_5_SET)

The group and script names are whatever you want them to be, just make sure to repeat those names in the LVar of the code

Then use an Axis assignment in AAO to assign this script to your rotary MIDI encoder, save, call up the Axis again in Change mode and set Axis Min = 0 and Axis Max = 100.

1792

It is about the HVAR
For me it change by two, very strange
I can’t explain

1793

set Axis Min = 0 and Axis Max = 100

On a slightly different subject, will AAO accept a range between 0 and 1? I have a COM volume lvar which will set the volume between that range (e.g. .5 is 50% volume)

1794

Unfortunately it doesn’t work 
 probably LIGHT_POTENTIOMETER_5_SET is not the variable that controls the glareshield lights

1795

It is most definitely working for me - for the unmodded DA40. The potentiometer number will be different in other planes (= not “5”).

This is my script, it also turns the lights on or off at the appropriate time:

Script group: DA40
Script Name: PanelLightDimmer

(L:DA40-PanelLightDimmer)·(>K:LIGHT_POTENTIOMETER_5_SET)·
(L:DA40-PanelLightDimmer)·0·==·if{·0·(>K:GLARESHIELD_LIGHTS_SET)·}·
els{·1·(>K:GLARESHIELD_LIGHTS_SET)·}

image

1796

Axis Min/Max at 0/1 is a special case that is reserved for triggers.

I would just use 0 to 100 and divide the script variable by 100. That should give you the desired range. You have to create this script anyway if you want to operate your LVar with an axis assignment.

Script group: YourScriptGroup
Script Name: ComVolume

(L:YourScriptGroup-ComVolume)·100·/·(>L:mycomvolume)

1797

I can’t get AAO to control the eyepoint position in the sim.
When I assign in AAO the events:

  • EYEPOINT_BACK
  • EYEPOINT_FORWARD
  • EYEPOINT_DOWN
  • EYEPOINT_UP
  • EYEPOINT_LEFT
  • EYEPOINT_RIGHT

to the joystick or MIDI device buttons and then I press the buttons, the eyepoint is not moving in the sim.
For now I can only steer the eyepoint movements by keyboard presses assigned directly in the sim, which is not convenient to me as the sim must be in focus to read the keyboard presses. I would like to assign the eyepoint movements to my MIDI device and control the eyepoint no matter if the sim window is in focus or not.

1798

I would like to use AAO voice control feature.
I’m sucesfully using Windows voice recognition in Pilot2ATC, despite I’m not US English native speaker. All works fine in Pilot2ATC - the program listens to my voice when the PTT button (specified locally in Pilot2ATC config) is pressed and regonizes the voice properly.
In AAO I assigned some events to voice commands as specified in the manual. But it doesn’t work.
Should anything be globally enabled in Windows to allow AAO listening? Like Cortana?
For testing purposes - should the green LEDs in AAO interface blink when the voice command is recognized?
How to determine if the voice control is not working at all for AAO or if just a given command is not recognized due to my Polish accent?
image

1799

AAO is also trying to utilize the Windows Voice Recognition, it doesn’t have any proprietary logic. Most likely you can only use one such application at the same time.

1800

While these events are present in the SDK documentation of MSFS (and hence available in AAO too), they don’t do anything. This has been the case since the Alpha of MSFS, and the complaints to Asobo have been numerous. But instead of making them operational, other native SimConnect camera control assets started disappearing entirely from SU to SU. Looks like the MSFS camera system is not really suited for external control.

Anyway, the only way currently is to either assign the camera controls in-sim, or to use the “Virtual Key” feature in AAO to send keyboard combos to the sim.

1801

Tricky. I would try simple “one-word” commands first and make them toggle all the aircraft lights (= no scripts or anything like that, just plain simulator events - in this case ALL_LIGHTS_TOGGLE)

1802

AAO voice control is not working for me even if Pilot2ATC is not running.

1803

Must the sim be in focus to receive such keyboard combos?

1804

Yes. I am just running it on my end, and it is working fine for me. When the AAO voice recognition can tie into the Windows system, you should see the small microphone symbol in the system tray once the aircraft profile has been initialized in AAO

image

1805

Yes. Most people are using PRN scripts for this, that force the focus on MSFS.

1806

When Pilot2ATC is running the microphone icon appears. The same for the other apps using the microphone. For AAO (sim running, profile loaded, some voice command defined) - the microphone icon doesn’t appear.
Strange device appeared here:

image
image772×432 28.7 KB

image

When I removed all my voice control bindings in AAO, this [0] device dissapeared.
This [0] device appears after just one voice assignment is defined in AAO, even if the AAO configuration folder is recreated from scratch (so it is not a glitch caused by my quite complex config).
No bidings are listed under this device, just the profile - see the screen above.