I don’t know if you were paying attention at the time, but at release there were hundreds if not thousands of posts over the first year or so at least of people complaining that we did not per-aircraft control assignments, and the only way around that was to create a bunch of clunky individually-saved profiles and then remember to switch profiles when we switch aircraft.
So now Asobo have given us what we wanted, which is the ability to set up per-aircraft controls that should automatically go into effect when we load into that aircraft. However the current implementation and UI is complex, clunky, non-intuitive and some of it just doesn’t work (like axis sensitivity curve displays for instance).
As I noted earlier, as much as I hate most of DCS’s user interface, aircraft-specific controls assigments is one thing that works perfectly. It’s ugly as hell, but dead simple to see and understrand at a glance. You get a big spreasheet-looking page with every single available contorl binding running down the left side of the page, and a row of every controller and device you have attached to your PC along the top row. To assign your ailerons to your stick, for instance, you scroll down the list to find AILERONS or type it into the search box, then click into the corresponding box under your stick or yoke. A mini-dialogue box opens and you can move the axis you want to assign and bam, assigned. You click a box and you can tweak the response curve right there on the same basic interface screen. Save and done. Do the same for elevators, throttle(s), trim controls, etc. Eveyrthing all there, in one place.
Every aircraft has its own bindings, and each developer creates and assigns names for them individually. Yes, sometimes you get weirdness like one developer calling it “Nosewheel Steering” and another calling it “NW Steering” or even “NWS”, but the interface for assinging the controls for every plane is dead simple and easy to use. Absolutely ugly to look at, sure, but it WORKS. And once assigned, controls are transparent to the user. Switch planes, your bindings switch, and that’s it.
I presume that was the hope for FS2024’s new scheme as well, but it’s not working out that well in practice, at least yet. One thing promised in streams past was that controller manufacturers and/or aircraft developers could distribute and share controller profiles we can load and use as a starting points for our own assignments but that is obviously not yet a thing. Maybe it will be eventually, and maybe it will help alleviate some of the growing pains.