In CONTROL OPTIONS KEYBOARD the ctrl + 2 is for TOGGLE INSTRUMENT VIEW 2.
I would like to have this at an assigned button in AAO. Which event should I use to get that function at my botton? I can't find any event in AAOs Select Simulator Event list to do this.

I'm not sure that there is one. Or at least not a simple, single "thing" to do. AFAIK camera control is quite involved in MSFS SimConnect and requires calling several events in succession. But I'm no expert on that. I only know that large parts of the (published!) camera control SDK events are non functional in MSFS.

What AAO is allowed to do over SimConnect, and what the internal controller logic of the simulator does, are two entirely different things. The lists in AAO (only) contain what has been published with the MSFS SDK for SimConnect. There are thousands of other options on top of that to control things, different for every aircraft. Although what you describe sounds like a very "default" thing to do, it is entirely possible that it cannot be done with SimConnect.

What you can do as a work around is either sending the keyboard event from AAO (best done using an RPN script) or binding a virtual joystick button to it (using the vJoy or ViGEm interfaces in AAO). 

 

 

2 hours ago, Lorby_SI said:

I'm not sure that there is one. Or at least not a simple, single "thing" to do. AFAIK camera control is quite involved in MSFS SimConnect and requires calling several events in succession. But I'm no expert on that. I only know that large parts of the (published!) camera control SDK events are non functional in MSFS.

Thank's for the ansver. It was what I thought. I have tried many events but none will do it. I have to do it in another vay. I am using LUAMacros for to use many keyboards and it works very well for many other events.

Thanks!

Edited March 3, 20233 yr by jonny

LUA is not processed by AAO. That would be FSUIPC.

In AAO you use RPN scripts. Like this one, which is calling up the view that you are looking for (I think)

2·(>A:CAMERA·VIEW·TYPE·AND·INDEX:0,·Enum)

This is not the same as triggering the MSFS controller input though. It just switches the camera to this view.

More about the topic can be found here:

Camera Variables (flightsimulator.com)

As has been the case since the beginning of MSFS, the camera EVENTS seem to be pretty much non-functional (although they are present in the SDK documentation). Apparently we are supposed to operate views with these variables now.

Edited March 3, 20233 yr by Lorby_SI

2 hours ago, Lorby_SI said:

LUA is not processed by AAO.

LUAMacros is processed by simconnect.dll direct to MSFS202 and I can use almost as many keybords I want.