Fully document all commands available to assign to controllers

Currently there are many commands available to assign to controllers that don’t work as expected, don’t work at all, seem to be duplicative or might be subtly different, etc.
There does not seem to be any comprehensive documentation of what each available command does.

A simple example:
-Autopilot airspeed hold
-Set autopilot airspeed hold

There are dozens of examples and dozens of threads where people are trying to work out a particular function - condition vs mixture in a turboprop, throttle reverse/beta , etc.

I would like Asobo to simply document all the available functions - what they do (or if they are legacy and don’t do anything, please tell us that), whether they only work with particular planes, particular engines, particular instruments, etc. It is very frustrating to try to assign functions to controllers without knowing what each function does.

https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Simulation_Variables.htm

While the simvars documentation may be good for developers and “pro” simmers, it may be not suited for every user that wishes to assign a controller button for a common task.

5 Likes

Totally agree!

This is very interesting - but these are variables that return information. Presumably the controller assignments are not variables - you can’t return a value to a lever. Is there something equivalent for commands? I can see that the commands would be related to the variables but they’re not the same.
Nothing on that page tells me the difference between:
-Autopilot airspeed hold
-Set autopilot airspeed hold

Also - controller assignments in the Sim are not intended just for developers. Those are for regular users, so presumably you shouldn’t have to go to developer documentation to find out how to do this.

2 Likes

Maybe Event ID’s (from the same SDK document) are what you’re looking for?

Example:

1 Like

Yes, this is the most helpful suggestion so far - and if this were a community support thread, this would be a great response. However, this is the wish list - and what I wish for is actual user-focused documentation. By definition, SDK docs are not for the average user. It is still difficult to find things in the event IDs, and not all of them are well-explained.

You need to buy FSUIPC7 or axes and ohs or something similiar to those programs. MSFS default doesnt cover the entire buttons

I agree. I created a thread about this some time ago. It refers to SPAD, but I believe it would be helpful to the average user as well.

I would suggest the same, and before buy you can check out these documents but it is
Pretty hard to read, but it will give you more insight just download fsuipc 7 trail version
And check the pdf
And in the documentation you find how it works on parameters etc
But also you can create profiles for each airplane.
In these created .ini files you should be able to read back

Hi - I actually have a fully licensed version of fsuipic7, but I don’t see how that addresses the need for clearly written explanations of those commands. If anything, it just increases the need for that.