I am trying to configure my 8-way switch to views. As a starter, I wanted to move my view height up but what event do I use?
"EYEPOINT_UP" seemed logical to me but it does nothing. Then I used "VIEW_UP" but that did nothing either. In the controller configuration within MSFS2024 the action is called "DECREASE COCKPIT VIEW HEIGHT", but I cannot find an equivalent in AAO.

There is nothing in the SDK that is like "view height" so there might not even be a way to adjust the view height.

14 minutes ago, Allard said:

but I cannot find an equivalent in AAO

The controller assignments in MSFS have nothing to do with what AAO is allowed to do using the MSFS SDK. These are completely different "logics".

Unfortunately, the camera events from the SDK never worked in MSFS or MSFS2024. I have no idea why Asobo is keeping them in the SDK documentation (which is why they are in the AAO lists). The only camera control that an external/SimConnect app has is though the camera variables: Camera Variables
But those TMBK don't have panning or shifting. 

In all honesty, it is better to assign the camera controls in MSFS itself. The shifting and panning usually are the same for all aircraft, and AAO doesn't mind if part of a joystick is assigned somewhere else. 
The only other options would be using vJoy, ViGEm or virtual keys - but I'm no fan of that solution.

 

11 hours ago, Lorby_SI said:

In all honesty, it is better to assign the camera controls in MSFS itself. The shifting and panning usually are the same for all aircraft, and AAO doesn't mind if part of a joystick is assigned somewhere else. 
The only other options would be using vJoy, ViGEm or virtual keys - but I'm no fan of that solution.

That's too bad. In MSFS2020 I had my Yoke configured in MSFS and the other controllers in AAO which worked fine. I never got around to also migrate the yoke assignments to AAO since, as you wrote, these assignments rarely change between aircraft.
I come accross a bug in MSFS2024 where my Yoke profile always gets reset to "no profile" when I load in the Cessna 172.  Other controllers are fine but the Yoke profile always gets reset so when I start a flight, there is no profile loaded for the Cessna172. Because of this nuisance I had hoped AAO could solve this, but I am dissapointed in MSFS that it doesn't allow that.

It continues to baffle me why Asobo doesn't just allow access to all internal actions through Simconnect events. Even worse, why the SDK that third parties have to rely on isn't reliable because some events that are in there don't work.

Even some things that worked fine in MSFS2020 don't work now, like the opening the ATC window; There is no event available (that works) to toggle it.
I'm no fan of virtual keys either. Vjoy is a somewhat better option IMO, but that means adding another driver that could mess things up.

Anyway, thanks for your continued support. It's great that AAO worked almost out of the box on release date and you continue to update AAO.

14 minutes ago, Allard said:

some events that are in there don't work.

Or we are not using them correctly. I've never seen a working example of the camera events, but that doesn't rule out that for example they only work in a specific camera state (set with the variables) or need additional parameter (>K:2:...) etc.

12 hours ago, Allard said:

"EYEPOINT_UP" seemed logical to me but it does nothing.

This seems to be working:
n (>A:COCKPIT CAMERA HEIGHT, Percentage)

n between 0 and 100

INC/DEC would work like this:

(A:COCKPIT CAMERA HEIGHT, Percentage) ++ 100 min (>A:COCKPIT CAMERA HEIGHT, Percentage)

(A:COCKPIT CAMERA HEIGHT, Percentage) -- 0 max (>A:COCKPIT CAMERA HEIGHT, Percentage)
 

Edited December 14, 20241 yr by Lorby_SI