Might be a simple question, but I can’t find the answer.
I’ve got actions that are available on one controller (i.e. flaps, by keyboard) which are not available to map on to another controller (Honeycomb Yoke).
I tried just mapping it from the keyboard profile, and letting it scan the input, but it says I’m on the wrong controller.
How do I edit the available-controls-list for a specific controller. And specifically, how do I control my flaps with my yoke?
Thanks!
Well… I might be oversimplifying the answer but if I understand your question…
Each controller when configured, has three possible views of the available commands in its settings:
Assigned - which only shows the possible commands that are already assigned to the controller
Essential - which lists those commands considered “likely” to be assigned to such a controller
All - which lists EVERY possible command that can be assigned to such a controller
You can only modify the currently selected controller. If there is a command that you want to apply to your currently selected controller (flaps, as the example you give) and it’s not presenting itself to assign in your current controller view, then on the left side, choose “All” and see if that command is now listed. Then select it and choose your “scan for input” on the controller to assign it. Then Validate it. Done.
Following this logic, I was just able to map the Retract Flaps (currently F5 on the keyboard) to a switch or button on my Alpha.
Did that help? Of have I completely misunderstood your question.
Jim-Sim
Select the controller you want to assign commands to from the top of the screen
You literally have to select a controller up at the top to make it assignable or detectable.
Workflow.
Controls>select your device from horizontal bar at top>detect or assign bind as appropriate.
Clunky as hell but there you go…
Yes JimSim, that sounds like it.
Sadly, for the time being I’m moving over to x-theotherone, since it seems like a better platform for learning preliminary actual pilot skills. Multiple monitors look like they work better, and it has flight training capabilities built in to the platform. It seems like MSFS has the advantage in pretty scenery and probably other things, but in x-p it seems to be better set up for sim-as-actual-trainer. I may be not giving MSFS it’s due entirely, since I always felt like I must be missing something…
Still, I’m sure I’ll be back once I have some basic skills, and you got my question exactly right: I guess I didn’t see that there were different lists I could access on each controller. I didn’t have any trouble editing the controller I wanted (the Alpha), but the options I wanted to assign weren’t available.
I understand completely. I installed and experimented with X-P while waiting for the initial release of MSFS. I’m probably here to stay however, when things are working well, there is just no comparison in my opinion.
I had the Alpha early on, and ordered my Bravo the very second their website made it available. I’m happy with both, but the challenges of getting them to work with MSFS have been huge. Even with the claims of being 'Natively Supported" and the two companies having a “Strategic Relationship.” Beyond frustrating. Still… I’m in it for the long haul.
Have fun (that’s what it’s all about), and I’m sure we’ll see you back here as your skills advance and MSFS matures into what they claim it already is. 
Should be a good fit by then.
Good luck, and glad I could be of help.
Jim-Sim