Are your profiles not saving, or are your aircraft not loading with a profile? Both bad, but not quite the same thing. I’ve seemed to find that helicopters don’t load in with any profile selected, even after I went through and created a new “Helicopter” profile. When I did that for the first airplane I flew, all airplanes have subsequently loaded into the game with that profile up and running. I just did my first bunch of heli flying early today and had to go in and click it from “none” to “new default helicopter (or whatever it’s named.)” with every new one I flew.
Definitely a bug either way, but hopefully it’s just the latter so your’e not actually losing the work you’ve done setting up your profile.
What are the key bindings when you go into the keyboard - camera settings?
Shift - A should move that view left. Though, I donno why you wouldn’t just choose an actual Pilot view, several of which are default mapped in that section.
I began mapping my Xbox controller to what it was in 2020 default. Ie left direction pad for brakes. Click down left joystick for cursor. One click not combinations of buttons like 2024 default. Why do that?
Thanks for your wisdom on the controls, I was very confused at first. Overall it seems pretty good, but one thing I’m struggling with is that the “Specific aircraft name controls” aren’t always so hyper-specific to that aircraft. For example, I spent hours mapping the C172 G1000 PFD and MFD buttons to various keyboard keys, only to find that those PFD and MFD buttons fall under “Specific”. So when I go to fly a DA 62 with an extremely similar G1000 setup, I can’t use my 172 controls. And it appears that selecting “Apply to all aircraft” in the settings for “Specific aircraft name controls” doesn’t actually apply to all aircraft. So at the moment it seems I have to re-map everything that falls under Specific because that can’t be shared across planes even if they have the same control.
Any thoughts or ideas, maybe (hopefully) I’m missing something? Thanks!
Wow, this is interesting. You’re the first person that I’ve read who’s managed to get settings into the “Specific aircraft name controls” section.
Could you provide a couple of examples of the bindings that fall into that category so I could check this out, too, and see what I can come up with here for thoughts?
I would have really expected G1000 controls to fall under the “Aircraft controls” rather than specific, for the reasons you’ve stated.
I haven’t looked closely at this yet, but I have noticed that the Cessnal 172 (for example) is only listed once in the “aircraft” list. Pressing on “configure” reveals the aircraft variants, including both steam gauge and G1000 variants. These could be described as “Specific” variants of the C172 aircraft, and of course have various controls not in common.
So “aircraft” would refer to the C172, and “Specific” would refer to the G1000 variant? The latter would need to include the MFD and PFD, as @RadDad5060 found.
TL;DR The MSFS2024 control binding interface screws up when there are multiple vJoy devices. By extension, maybe this is true whenever there is more than one device with the same name.
vJoy allows you to set up virtual joysticks. Unfortunately, all vJoy devices are called “vJoy Device”, which makes it a pain for any game to distinguish them. Usually, assigning a different number of buttons or axes to each instance will help. And DCS even checks their GUID. But MSFS2024 isn’t so clever. If you have two vJoy devices, you can’t tell them apart because the bindings interface just calls them both “vJoy Device”. If you manage to create a single profile for each, say vJoy#1 and vJoy#2, either can be picked for both devices, so one of them will show the wrong bindings. Even if you select the correct profile for both devices in a given session, MSFS2024 tends to forget your choice once re-started.
I use vJoy a lot. In fact, I have five installed virtual joysticks, so the inability of MSFS2024 to distinguish them is quite problematic. Why use vJoy at all? Because, for example, using a program like VoiceAttack as intermediary, it’s possible to turn different actions on one physical button, like Tap, Double-Tap, Long Press, into different virtual buttons, or a button sequence, or a toggle… anything you like.
Observations on how to minimise the problem:
Use HidHide to hide any vJoy devices not needed for MSFS2024
Use FSUIPC7 or similar to send low level SDK commands therefore avoiding the need to press virtual buttons
As often as possible, map physical buttons from physical devices instead of using vJoy
Programmatically send keystrokes instead of virtual button presses (this is not a panacea as keystroke combinations with common characters often interfere. Especially common are modifiers like Ctrl)
Identify the selected “vJoy Device” by programmatically pressing virtual buttons until you find the virtual stick that doesn’t invoke a Wrong Device message
Kudos to anyone who read this far. It’s more a set of observations than a request for help. But hopefully useful to someone.
I dislike the changes to the controls UI, its very confusing a lot of stuff is backwards as well, not sure if velocity one flightstick problem but my throttle and mixture was backwards, had to go into controls and invert the mappings.
Also for some reason I have duplicate mouse inputs.
Its really messy and needs looking into.
edit/ read a few more posts down from OP, thanks for explaining some of the functions @NixonRedgrave.
Yet they called this a great invention. I call this regression. 2020 controls were much easier to understand and at least clear. Even DCS type controller option is 10x better than this nonsense.
2020’s system needed changing because having to manually change profiles for several devices every time you changed plane - or worse, aircraft type - was a massive PITA. The DCS style isn’t suited for MSFS because it means binding every single aircraft separately.
The new system is absolutely not intuitive, but works very well once you get your head round it. I’m happy to concede that despite initial reservations, I actually think they’ve done a pretty good job.
While I have had some success setting up my hardware in 2024, I don’t think I really understand the best use of that third category, the aircraft specific one at the bottom left. Please anyone who is finding success with that one share what you are using it for and how it is working for. your set-up. Thanks!