Hi!

I'm searching and trying for quite a while now... Managed to get the RANGE knob on the G1000 MFD to accept zoom increase/decrease as well as pushing to enter the panning feature. However, I did not achieve to get the panning feature working.

Via the event monitor I can see "[AS1000_RANGE_PUSH_MFD): -172,938746384 (>IE:AS1000_RANGE_PUSH_MFD) while holding the left mouse button and moving the mouse to either side. The value displayed is a positive or negative number reching from about -190 to +190 depending to where and how far the mouse is moved.

I did try to send values to 0 IE:AS1000_RANGE_PUSH_MFD via keyboard or Stream Deck but the MFD pointer on the G1000 is not moving.

Would be great to get any hint, advice or perhaps info if that has been solved ...

 

Thanks!

A.

This particular IE is one of those that needs more than one parameter (x-y position). You can't do that with AAO at the moment, because the multi-Parameter IEs are dynamic - it is next to impossible to implement this in a generic way in AAO.

One solution would be to use BVars instead of the IE and send them to the sim for processing with (SIMPROC)

(SIMPROC)·0·1·(>B:AS1000_RANGE_MFD_Set)·
(SPLIT:200)·
(SIMPROC)·1·0·(>B:AS1000_RANGE_MFD_Set)·
(SPLIT:200)·
(SIMPROC)·0·-1·(>B:AS1000_RANGE_MFD_Set)·
(SPLIT:200)·
(SIMPROC)·-1·0·(>B:AS1000_RANGE_MFD_Set)·
(SPLIT:200)
(SIMPROC)·0·0·(>B:AS1000_RANGE_MFD_Set)·

This small script moves the joystick full circle, then puts it back in the middle. The x - y parameters both go from -1.0 to 1.0 

In the MSFS 2024 variant of AAO it should also be possible to do this:

0·1·(>B:2:AS1000_RANGE_MFD_Set)·
(SPLIT:200)·
1·0·(>B:2:AS1000_RANGE_MFD_Set)·
(SPLIT:200)·
0·-1·(>B:2:AS1000_RANGE_MFD_Set)·
(SPLIT:200)·
-1·0·(>B:2:AS1000_RANGE_MFD_Set)·
(SPLIT:200)
0·0·(>B:2:AS1000_RANGE_MFD_Set)·

 

Thank you very much!

I'm not sure if I exactly get what you suggest 😁    But I certainly try work with your advice! 

Thanks!

A.

1 hour ago, Akha Khan said:

I'm not sure if I exactly get what you suggest

? Each of the (SIMPROC) scripts pushes the joystick in one specifc direction, left right, up, down.

Assign them to four buttons and you have your range control.

left
(SIMPROC) 0 1 (>B:AS1000_RANGE_MFD_Set)

right
(SIMPROC) 0 -1 (>B:AS1000_RANGE_MFD_Set)

up
(SIMPROC) 1 0 (>B:AS1000_RANGE_MFD_Set)

down
(SIMPROC) -1 0 (>B:AS1000_RANGE_MFD_Set)

(not sure about the directions, you will have to try which one does what exactly)

Thank you. That helped!

For each direction I ended up using 2 scripts:

Button down:
(SIMPROC)·0·-1·(>B:AS1000_RANGE_MFD_Set)

Button up:
(SIMPROC)·0·0·(>B:AS1000_RANGE_MFD_Set)

Sending the button down sets the pan stick to the left, but does not release it to center. So just sending the 0 -1 start the cursor moving left, never stopping.

It seems to be not entirely clean that way. As pushing the button quickly after push/release doesn't seem to send the stop properly and the curser might not stop. Butte using the direction buttons slow, seems to work ok.

 

Thanks again!

A. 

All right, while finishing my clumsy fiddling,... somehow I struggle with the up / down...

And while searching again, what I might have done wrong I stumbled across another hint on how to move the PAN knob:

There are events available I failed to find earlier:

H:AS1000_MFD_JOYSTICK_UP
H:AS1000_MFD_JOYSTICK_DOWN
H:AS1000_MFD_JOYSTICK_LEFT
H:AS1000_MFD_JOYSTICK_RIGHT

H:AS1000_MFD_JOYSTICK_PUSH
The PUSH did not help much, but the 4 directions behave very nice.

I'm sorry for the huge circle triggered around this issue ... 🫣

Best!

A.

 

9 hours ago, Akha Khan said:

Sending the button down sets the pan stick to the left, but does not release it to center. So just sending the 0 -1 start the cursor moving left, never stopping.

You should be able to do both in one single script, and then use "Repeat slow" on the button assignment. 

(SIMPROC) 0 -1 (>B:AS1000_RANGE_MFD_Set) 0 0 (>B:AS1000_RANGE_MFD_Set)

IIRC those scripts were initially bound to joystick axis, and the parameters would move through the entire range from -1.0 to 1.0. Can't do that with the HVar (I think).

Edited April 3, 20251 yr by Lorby_SI