So I have all my controls and views setup in MSFS 2024 as I use them in MSFS 2020. Now to be fair, I only use a Thrustmaster 16000m as my joystick, and I also use my mouse and keyboard. I don't have more complex peripherals as some of you have. 

To be honest, the huge learning curve for setting up controls and views was in MSFS 2020, not in MSFS 2024.  The reason is, MSFS 2024 is pretty much using the same terms to bind your control inputs to that MSFS 2020 is using. So as long as you can search for the correct term to bind your control input to, you can duplicate your settings from MSFS 2020 quite easily into MSFS 2024.  IMO, the hard part was learning those terms in MSFS 2020. I remember in MSFS 2020, it took me forever to setup my controls and views because I was not familiar with the terms in MSFS 2020 and searching for the correct term to bind to was a pain in the ***.  For example, terms like "Translate cockpit view left" and "Cockpit Quickview 120° left" are terms I had to learn in MSFS 2020, and it was a pain to learn.

But because I setup the controls and views in MSFS 2020 before, I had already learned the "quirky" terms that Asobo uses for binding and this made binding the control inputs in MSFS 2024 much faster for me. 

Probably the fastest way to duplicate your control input bindings is to run MSFS 2020 and MSFS 2024 at the same time, if you have a dual monitor. If you don't have a dual monitor or an extra laptop that can run MSFS 2020 on the side, you can note the bindings you are missing in 2024, then close MSFS 2024 and open MSFS 2020, search for the control input that you want to bind to, and find the terms that they are bound to in MSFS 2020. Write down that term or take a screenshot of MSFS 2020, then open MSFS 2024 and search for that term. Like I said, if you have a dual monitor and can run MSFS 2020 and MSFS 2024 at the same time, or you have an extra laptop to run MSFS 2020 on, it makes it much easier because you don't have to open and close MSFS 2020/2024 multiple times to find the terms to bind to.  Otherwise, I would suggest just making a list of your missing bindings in MSFS 2024, then open MSFS 2020 and find all the terms that match your list in one single go.  And every time you bind a control input, immediately after, search that control input that you just bound to, to make sure there are no conflicts - by default, MSFS 2024 may have some other term that is already bound to the control input you just used (in which case, you can delete the conflicting assignment).

Now I only have bindings for all general bindings and all aircraft bindings.  I don't have any bindings for a specific aircraft at this moment.  So for me, when I was binding under "General" and MSFS 2024 prompts me to create a new name for the profile, I just use the exact same name every time for General - I typed something like, "General Profile Bindings".  And for "Aircraft," every time MSFS 2024 prompted me to create a new name for the profile, I just typed something like, "Aircraft Profile Bindings".  Don't forget to save your bindings before you exit the controls menu!

And just like that, I was done binding my control inputs within 30 to 45 minutes.  Everything works in MSFS 2024 the way it works for me in MSFS 2020.

FYI, this is a quick FAQ on MSFS 2020 camera views - if you are struggling to setup your views in MSFS 2024, maybe check this FAQ first to see if it is helpful to you: https://flightsimulator.zendesk.com/hc/en-us/articles/360016003159-Camera-Video-FAQ

 

Edited November 26, 20241 yr by abrams_tank

I forgot to mention, when the popup for "General" or "Aircraft" comes up asking you to create a new name for the profile, I checked the "Apply to all aircraft" checkbox.

Thanks for the reminder from @jcomm:

 

Just as easy using Axis and Ohs and or spad next. In fact they will port over, well at least 95%.  Haven't used default axis/button assignments since 2004! Why punish ones self?

7 minutes ago, Torkermax said:

Just as easy using Axis and Ohs and or spad next. In fact they will port over, well at least 95%.  Haven't used default axis/button assignments since 2004! Why punish ones self?

Because there isn't any punishment and my question back use another app when default works as you just read.

9 minutes ago, Torkermax said:

Just as easy using Axis and Ohs and or spad next. In fact they will port over, well at least 95%.  Haven't used default axis/button assignments since 2004! Why punish ones self?

If I wanted to punish myself I’d use axis and ohs.  But both of those programs ARE really powerful, and necessary if you have advanced controller hardware.  But they are payware, not necessary for most users and… aren’t more intuitive than the built in system.  I think I like the new system, if I can finally stop using spad for this sim, I’d call it a win.

31 minutes ago, Torkermax said:

Just as easy using Axis and Ohs and or spad next. In fact they will port over, well at least 95%.  Haven't used default axis/button assignments since 2004! Why punish ones self?

Axis & Ohs and Spad Next are are payware, right? For starters, people like me that are using a Thrustmater 16000m and a mouse and keyboard have no need to pay additional money for Axis & Ohs or Spad Next. That's overkill for somebody like me and probably a waste of money, especially when I can set everything up in 30 to 45 minutes just using the MSFS 2024 controls menu.

Now if you have a lot of advanced peripherals in addition to a Thrustmater 16000m, then I can see the value of buying them. But for anybody else that only has a Thrustmater 16000m (or a comparable simple flight joystick) and doesn't own any other advanced peripherals, I would suggest they don't buy it, it's simply not needed.

Edited November 26, 20241 yr by abrams_tank