I have found sharing the same control profiles across multiple aircraft can and has (on several occasions) resulted in a situation where this will trigger CTD’s. What you describe is absolutely logical and should work, but I have found it to be a very clunky and bug-ridden solution right now.
1 Like
I just finished an hour session trying to make the Controls apply here and there to the aircraft I quickly test in MSFS2024. Yes, the assignment could have benefit from a more straight forward process I believe.
I manage a UI/UX team and maybe I will ask them to review the interface as part of our monthly forum. Maybe they would disagree, let’s see!
Edit: I do not want to pretend having a better solution but in my opinion, if assignment went from pressing / clicking on any controller button without “toggling the search by Input” / pointing to the button of the controller / having a list of controls we can assign to it by searching for key word.
Now if we “toggle the search by input”, press a button, if it is not assigned to anything, we can’t have an option to assign something to it? Am I missing anything?
An awesome thing would have been to import our Control settings from MSFS 2020. And I think there is some usability acrobacy one need to get used to in the 3 layers of profiles.
Cheers
5 Likes
A good example is trying to set up a 4 engine airframe with someone only has two physical throttle axis to work with. Airplane specific profiles would allow them to switch between 1, 2 and 4 engines airframes without rebinding everything.
Granted, it’s janky and a little bit of a learning curve, but I was able to jump between the FBW a380 (on dev branch) and the B38M without too much trouble , minus swapping out throttle detent profiles on my VKB STECS Max.
For a Cessna I could set one throttle to power and the other to mixture then switch to the H125 and have one for engine RPM and the other for the collective itself.
Mostly useful for people with more versatile controller setups instead of someone with an Airbus or Boeing exclusive rig
My biggest gripe is the trial and error of it all. But I think that’s the nature of rebinding 20+ something controls…
2 Likes
I imagine they’ll first laugh and the foolishness you’ve put before them and then gasp in shock when you tell them that this is the actual control settings UI for what is theoretically a AAA(A even?) game. 
1 Like
Yes, tips and frustrating comments and all the problems reported in the last few weeks are important for the future. But the overwhelming frustration and the endless hours of thinking and trying to get the sim to work is a real imposition and damaging to Microsoft’s image. Shameful for a global corporation! It’s a problem to bring unfinished things onto the market; we’ve gotten used to that. But on such a scale as now, this is very worrying. It is not finished yet. We would have understood that and would have been happy to help make it the best experience. Jörg is certainly less to blame, it will probably have been decided that way further up.
When there are too many variables in a complex system, a lot of understanding and perspective is required. We are on a rocky road, that is unfair. Never mind, later on we will be happy.
I don’t know if it has been mentioned earlier but one of the most annoying things I found whilst setting up control profiles was :-
Whilst trying to setup controllers with lots of buttons, the marker number that indicates how many extra profiles have been setup on this particular button, is placed right above the actual button number, obliterating the actual button number completely.
I found myself staring at an item with 5 replications but absolutely no clue which button it was!
I thought "there must be somewhere on this page, the button number when i highlight it, in case it is covered with a circular white number. Nope! not anywhere. Ridiculous.
EDIT: Have just noticed this has been mentioned already Sorry.
I agree, but again, it would be much easier to understand, at least in my mind to have one general profile. Than to make changes for specific aircraft and save if for that specific aircraft.
For example.
General profile, views, throttle, control surfaces, flaps, gears, AP etc to be set as general.
Because only most of aircraft I will use the same controls for flaps, views, AP, etc.
Than AC A 2 engines, make separate axis for throttle.
AC B 4 engines, again separate axis for throtle.
AC C, 1 engine, with prop and mixture, asign axis.
I have one axis controller for throttle, so I would use same general profile for all, but people with more than one axis could make profiles like in example.
2 Likes
There is a workaround I’ve found.
Click the little cog on that row, then you see a list of all buttons in the left column and can scroll to see which is switched on. You can turn it off there also. And turn another one on (if you know which you need but that is another problem!).
2 Likes
Major fail then.
1 Like
That is pretty much what I did. For each controller you 3 groupings of configurations general controls for things like radios, views and simulator controls. then a group for aircraft controls for your engines, control surfaces, trims etc. Funally a group for specific functions that would be for a specific aircraft.
Since the control mappings for all aircraft are the same for my Honeycomb Alpha , I modified the default for when I want to fly in VR or not since I remap so e of the thump switches. For the Bravo, I created a master for all the switches as a template then made a profile for single, single complex, twin prop, two engine jet and 4 engine jet. Will probablely make separate profiles for turbo props when I start flying those. Pretty much the same as I had in 2020. What is nice, these profiles are presistent once mapped to an aircraft so I don’t have to manually switch profiles.
1 Like
I’ll give the new controls a B-, for FS20 old controls I’ll give that a C. The new one is better in functionality, but definitely not as good as it could be, and the UI although usable when you’ve learnt it is far from intuitive, not terribly well designed, and could be so much better.
Good:
- Saves control profiles for each plane, very big win.
- 3 levels of control profile to reduce duplication of settings between different planes, ie. If I want to change a camera control I only have to change it once and not 20 times for different planes.
- The new pop up controls window in flight is fantastic, helps so much when configuring controls.
- Being able to select button combinations by switches in the UI is very convenient, and it works for multiple button bindings too, be sure to click the button switches in the right order because it remembers that.
- It’s possible to save and load bindings from files. Which reminds me I haven’t tried that yet.
Bad:
- They decided to spilt the buildings into 3 static groups with a mapping only Asobo control. I think they did it because they thought it would be easier to use, but it’s not. It’s more confusing, and also much less powerful and flexible. Instead keeping all bindings the same and having 3 layers of profile, where you could add/remove/override any binding at any layer would be easier to use and much more flexible.
- The whole UI. So many individual elements of it could be improved, many have been commented on in this thread. I don’t have space to list here.
- Mostly due to the UI, but much of it is not easily discoverable. It took me several hours of use until I understood it all (I think), and as a developer I’m very used to leaning and understanding difficult technical UIs, I really think that a large proportion of less technical/computer savvy users will never be able to get the most out of it.
- The bugs. Some of the features are broken if using the popup keybindings window (eg. search by binding, deleting bindings), you need to use the main settings screen to get the best experience. Some things are broken full stop (eg. axis are not animated when configuring curves, this is a huge problem).
- The ability to configure “tweak curves” with a binding is actually good, but because of the use of the 3 static groups of bindings it means that you still can only configure curves at an aircraft class level and not at an individual aircraft level because Asobo fixed the pitch/roll/etc axis bindings in the aircraft class group. This means if you really must have a plane specific curve tweak you have to clone and maintain a whole new aircraft control profile instead of just a few overrides.
- Setting bindings by pressing combinations doesn’t work as well as in FS20 and in particular it will not set digital buildings from an axis direction like FS20 does, forcing use of the individual button switches window.
- It’s impossible to see the control mappings at a glance like it was in FS20 because they are truncated in the display. Where I was able to take a bunch of screenshots on FS20 showing pages of controls at a time, so I could manually enter them in FS24, that is simply impossible to do in FS24.
There’s more stuff that I don’t remember right now, I might come back and edit more points as I remember.
6 Likes
…which is NOT the description of a well designed user interface.
Those developers are locked into some odd ecosystem that fits their brain patterns, but not ours.
6 Likes
I like this too. I have an Axair MIAP which issues up to 3 keystrokes when you turn a knob, and the search feature often drops characters. This gives the ability to input the key sequence manually.
However, it uses a semicolon for some of the functions and there is no semicolon in the list. The key sequences are hard coded in the MIAP and cannot be changed. So that knob on the MIAP (Obs) cannot be used.
In 2020, you could use a physical keyboard to type in the sequence, but that doesn’t work in 2024. I’ve already submitted a ticket for this.
1 Like
I know I’m a bit daft, but some things just don’t make sense.
I mapped a button on my Alpha to ‘Toggle External View.’ Cool - at least I figured out how to find that control.
Back in the cockpit… Press the button and it switches to external view. Awesome.
Press the button again…nothing.
Delete the mapping and assign the button to ‘Toggle Cockpit View.’
Press the button…nothing.
I can’t get back into cockpit view.
Do I not understand what ‘Toggle’ means? 
I fear for my sanity if I keep having these logic failures as I go through this interface.
2 Likes
I have the same. Sometimes they work, sometimes they don’t. No logic to it at all. It’s all very frustrating.
2 Likes
There’s a thread specifically for this. It hasn’t gotten a ton of traction, but you aren’t alone:
4 Likes
I have my button set to “Cockpit / External View Mode” and works perfect as the toggle you are looking for.
4 Likes
Thank you! I’ll try that out.
ETA: Worked great. 
2 Likes
in a perfect world, that’s exactly how it works. Flaps for all my planes are the same buttons (a 3-way boat switch) for example. It just seems way more convoluted to achieve full flexibility with different setups in FS24.
Then there’s people who have a side stick for airbus, yoke for boeing and a collective for choppers and they got swip and swap their pieces and parts out depending on what they wanna fly in that moment. #immersion
Along the lines of the Internal/External view toggle, is there one for the ATC window like there is in 2020? Or the Comm popup window that’s in the toolbar, which now contains all the radios? I can get that stuff open, but the only way I can seem to close it is with the mouse. I’ve searched pretty extensively, but it’s quite possible that I’ve missed something.
Thanks.
1 Like