They didn’t have beta testers; clearly. They had Asobo QA testers who most likely used an Xbox and 1 peripheral. To your point, the biggest mistake Jorg made was not making this into a summer long alpha like FS2020.
I’m also having issues I don’t understand. I followed Rmag’s excellent tutorial on setting up my Honeycomb Bravo. Somehow, I managed to attach the “Basic Single” control assignment to the Cessna 172 G1000, or at least so I thought, even though I’m not sure how that happened.
Anyway, subsequently, I flew the 172 for about 4 hours with the controls remaining attached to that airplane. Now this morning, I tried a flight and upon spawning at the airport, the engine died because the mixture was pulled all the way out, and was no longer connected to the Bravo. It appears that the 172 reverted back to some kind of default control.
I have no idea what’s going on, whether it’s my screwup, or it’s a bug, or if it’s supposed to be this way.
Very frustrating!
For those of you who are not liking the MSFS 2024 controls setting; if you have SPAD.next or another 3rd party peripheral tool, I can’t stress how amazing it is within MSFS2024 (and MSFS 2020) - you don’t ever have to use a single control binding from this sim again. Trust me, use SPAD.
If a system to autodetect a switch or lever movement in the sim could be done, much like how SPADneXt detects switch movements then allow the user to bind it to his peripherals as desired, would this not help soften all these issues. Key commands have been inherited from past versions of MSFS and are just antiquated and unnecessary. Everyone raves about SPADneXt which doesn’t use a single predetermined key command.
My TrackIR works just fine. But…I can start a session and the sim loads and the TrackIR settings have all been changed…very frustrating to have to exit out, back to IR settings and correct everything. Trying to be patient, but it is ridiculous that a software company can’t proof before release.
Has anybody worked out how the 3 sets of options per device function?
As a retired developer I think the set of 3 makes it far too complex for the average user.
I haven’t a clue how the options split into 3.
Xplane does it with 1 profile for all settings. That means just one profile per plane, if that’s what you want.
Xplane is just as flexible, but far simpler to use and understand.
2024 seems like it might have “layers” that blend together. Hence the total confusion for some people.
What we need is file import/export to share useful peripheral setups with everyone, especially those that are struggling.
I thought it was quite simple.
The first set of options are general, non-aircraft specific commands, like pause, switch to VR etc.
The second set refer to the main aircraft type you chose, for example C172. This will be used for controls common to all the C172 variants, like thrust, flaps etc.
The third set refer to the variants within the above type, for example the C172 steam gauge or the C172 glass cockpit. Each variant may require different controls, and there will have different set-ups for these controls.
You must of course make sure you have selected the right aircraft for the controls you are setting. Note that you cannot change the basic default files. If you try to change these, the sim will automatically prompt you to save to a new file, which you can name and select as necessary in your subsequent flights.
Cheers,
I think the 3 sets are:
Set type. : Prefix in assignments
1 General commands. | “General”
2 Airplane commands. | “Airplanes”
3 Plane specific. | “Specific”
Specific is like “PFD Soft Key 1”. The first G1000 key.
Aircraft is like “Flaps down”
General is like “Zoom In”
The complication is that each plane always has type 1, then
type 2 is optional
type 3 is optional
Types 1, 2 and 3 blend together in one of 4 ways: 1, 1+2, 1+3, 1+2+3
Further, for 4 peripherals keyboard, mouse, yoke and throttle say A,B,C,D
Each peripheral has its own set of types 1, 2 and 3
For example
A (1+3)
B (1+2)
C (1+2+3)
D (1)
That is extremely flexible, designed by a mathematical person.
By contrast, XPlane 12 is far simpler.
Each profile contains: all commands for all peripherals
For example, one profile called “X1000” that contains all the above:
“A (1+3), B (1+2), C (1+2+3), D(1)”
The types 1, 2 and 3 disappear to become “all commands”
Note: MSFS is theoretically more flexible, but adds significant additional complexity.
However in XP you can still achieve whatever you want for each plane.
PS:
Other scary stats, there are 327 keyboard shortcuts in MSFS 2024.
Spilt this way:
Camera 141
DEV 51
Tools 23
Airplane 112
What we really need is for them to provide some decent documentation on this convoluted mess.
I too am a developer of over 30 years and it confuses me as well.
^^^^ This ^^^^
Product developer over 30 years also. I don’t care how many people you have developing a product if it can’t be properly understood then customer satisfaction will suffer.
Document updated. Complete re-write, additions and corrections.
At work, chatting over coffee we often discussed how to make our product look simpler for beginners.
One level down, powerful commands for the experts were available.
It’s a difficult balance to establish, but it was our philosophy.
When developers get a bit confused about the combinations and permutations something is wrong.
In my head I’m thinking how I would explain 2024 controls. Maybe some diagrams would help.
One thing I spotted, extra filters are needed and a means to disable a device. A flight stick and yoke are mutually exclusive. General commands from both might clash.
Thx @MSFSRonS , well done. While I haven’t tested it, I believe not saving bindings is related to where you stated:
"Be careful of which the Presets are displayed when executing the “Save and Back”.
I believe the sim will only save those exact 3 profiles. In addition, I suspect if you flip to another profile and then back you’ll lose any new bindings you made to the profile you moved away from before pressing save and exit.
The fact that no pop up is displayed warning you that you will lose any changes just shows how quickly this interface was put together and not tested.
You call it a philosophy, I call it a product requirement. And yet here we are trying to reverse engineer a product released globally in order to understand how to use it.
We should be able to save without being forced to go back…
And to go back without having to save 
Just delete all bindings and run spad.Next.
Exactly; life savior. Haven’t had a single issue since.
Okay… I’m firmly against control binding programs like this because I feel that something as critical and basic as control bindings should be done without external programs.
That said, FS24’s binding interface is TERRIBLE.
Should I get over myself and buy SPAD.neXt? Is it worth learning yet another external program?