MSFS2024 Not Saving Custom Camera Views

I am new to 2024 after coming from 2020. I have duplicated the default controls profile for my joystick and throttle, and named them. I have assigned buttons for recalling (loading) 6 custom cockpit views. I set a view, hit Alt + Cont + a number button to save. But when I try to use my assigned buttons to recall them, it does not work. I checked the control bindings and there are no conflicting commands for those view bibdings. In addition, I assigned a joystick button to toggle cockpit and external view, again no conflicts, but that button doesn’t work either.
So, even though the bindings appear in the Controls menu, they obviously aren’t getting saved.
Yet, other things like trim and flaps are getting saved. What am I doing wrong?!

2nd question- If I create a control profile (NOT the defauilt one- I am using my duplicatred, renamed on), if I try to then edit/change a binding a popup window asks me to create a new profile. ??? Can’t I edit the one I already created?

2020 had a few things to learn but it was so much easier. Whoever designed this “newer” UI should be fired.

More issues. When I load into the flight, the cockpit camera slowly pans down- very slowly, and no matter what keyboard or hardware command I give it does not stop it. I have watched several good tutorials on setting up the control bindings and most of my bindings are not working after I save the profile.

Hi, way back when I started flying in 2024, I selected the 2020 keyboard in 2024 for a number of reasons. To this day I still have the 2020 keyboard selected in 2024 even though I stopped flying 2020 months ago. Not sure if this is helpful here, but maybe something to check? Cheers!

Have you checked if the command to save custom views actually is Alt+Ctrl+number? And if so, can you use the keyboard shortcut to change to those views? Some camera settings changed between the sims, and I can’t now remember the defaults.

Edit: for the second item, that seems like stick drift on a connected Xbox controller? If so, try increasing the deadzone of the controller, or try a different controller.

Thanks for the suggestions. As far as the keyboard goes, I will use the 2020 keyboard but I’m dealing with the hardware, a thrustmaster throttle and joystick. I won’t use the keyboard for all those things.

I watched a very good YouTube tutorial about this and it said the first thing to do is duplicate the default profiles for your Hardware, and then clear them so that there are no bindings and you start from scratch. I did that, and when I set up my bindings and looked at the Assigned bindings everything looked good. No conflicts. But when I switch to All, there were still a lot of conflicting Bindings that didn’t show up when I just used the Assigned mode. This seems like a bug. In any case, I spent a long time deleting every binding that had nothing to do with what I needed assigned and I think now everything is working.
I will report back. Surely there should be a better way to design this controls UI…
grrrrrr…

There is a custom camera video by ozzysafa in YouTube

I’ve got everything pretty much figured out now, but I still don’t know what option in the Controls menu binds the NAV switch to. I got HDG to toggle on and off but not NAV yet. I’ll have to try a few of the other options. Sometimes the wording isn’t obvious.

I finally have all my throttle and joysticks binding working. It is very complex compared to 2020 but, other than setting up, I find that it is a really nice looking simulator and actually much better frame rate without even using any kind of external scaling program. The next test will be to make sure that Simbrief and Beyond ATC are also working correctly with it. Thanks goodness for YouTube videos!

I feel your pain. Except for the satisfactory outcome you had, I am in more or less the same boat. This is most execrable piece of software engineering I have ever had the misfortune to encounter, and after MS2020 I thought I had seen it all!
There are way too many inscrutable settings and every time I load a new airplane, or even a different version of an airplane, I am forced to redo my view settings, which I prefer to have set up identical to what I have in XP. Then, after all of that, it somehow does not obey those instructions and I am stuck with no view control with the numeric keypad. I was under the impression that most of this should have already been in place when I bought the thing…

Is there a recommended video somewhere that demystifies the process of setting up views using the keyboard and offers suggestions that work for all airplanes off of one keyboard setup??

I’m sure YouTube has a couple. One thing that threw me is that there are more than one keyboard profile in the Controls options. The shortcut to save camera views in 2020 was Ctl-Alt-number. That didn’t seem to work with the default keyboard profile so I changed to their 2020 keyboard profile and set up all my camera views, clicked the profile and selected “Apply to All Aircraft” and that did the trick. However, the 2020 kbd profile didn’t work for things like getting into the cockpit from the starting flight screen so I had to change back to the default 2024 keyboard after all my views were saved! Horrible. I tried duplicating the default 2020 kbd and adding in the enter cockpit shortcut Shift-C but that didn’t work- don’t know why. You’d think they could have at least left the kbd shortcuts alone and just added a couple of 2024 specific bindings. It took a while and googling (not always the correct answer I found) to learn how to enter Slew mode, set/release parking brake, etc. since it is not the same as the 2020 kbd.

Subject: A camera-view bug open since November 2024 — what does this say about priorities?

I want to raise something that goes beyond a single bug. The “custom camera views not saving” issue has an open thread dating back to November 2024. It’s still unresolved as of mid-2026 — a year and a half for something as basic as saving a view.

I’m not writing to pile on the bug itself. I’m asking a different question: when something this fundamental sits unfixed for this long, is it a matter of priorities we don’t have visibility into, or is there a real disconnect between what the development team is working on and what customers reasonably expect from a flight simulator they paid for?

I’d genuinely appreciate some transparency here — even a “this is hard to fix because X” would go further than silence has.

What camera view bug are you referring to? Do you have a link to the topic? I couldn’t find anything when searching for it.

I set custom camera views in all planes I fly, and it works as expected.

Same here. I have had no issues with them but it took some rethinking after realizing that ctl+alt+number didnt work.
I had alot of priblems with control settings until i started frim scratch, not using any default kbd profile.
Since have lots of buttins on my joystick and throttle I need very few kvd commands, mainly the custom camera views
So…

  1. I duplicated the default 2024 kbd and named the new profile.
  2. I hit the settings next to the profile and hit “clear”, thereby starting from a completely clean slate.
  3. In the controls menu I searched for custom camera and created six custom views in my new profile using shift + the F numbers on top of the keyboard but I anything would work since there are no existing kbd commands in the new profile.
  4. Since the shift + C allows you to enter the cockpit in the default keyboard I also assigned that to my new prifile. The control options you need to bind that to are “Quick Flight” and Take Control of Avatar" ( I hope that is accurate as I am away from my computer right now but I think you’ll figure it out.)
  5. After that set up any other Bindings that you think you’ll need from the keyboard. Make sure you then select the option to save to all Aircraft so you don’t have to do it again.