Subject: Bug Report - Custom Camera Views Not Saving in Microsoft Flight Simulator 2024
Product: Microsoft Flight Simulator 2024
Version: Microsoft Store Version
Description: I am experiencing an issue with custom camera views not saving in Microsoft Flight Simulator 2024. In MSFS 2020, I had no problems with custom camera views, but in MSFS 2024, the custom camera views don’t always save as expected.
Steps to Reproduce:
Launch Microsoft Flight Simulator 2024.
Navigate to the camera settings.
Create and save custom camera views.
Restart the simulator or load a flight.
Attempt to use the saved custom camera views.
Expected Result: The custom camera views should save and be available for use after restarting the simulator or loading a flight.
Actual Result: The custom camera views do not always save and are sometimes unavailable after restarting the simulator or loading a flight.
Additional Information:
I am using the Microsoft Store version of the simulator.
This issue did not occur in MSFS 2020, where custom camera views saved and functioned correctly.
System Specs:
Operating System: Windows 11 Pro
CPU: i9-13900KF
GPU: RTX 4070 Ti
RAM: 32GB
Thank you for your attention to this matter. I hope this issue can be resolved soon to improve the overall experience with Microsoft Flight Simulator 2024.
I will agree here, as i have also seen a couple “liveries” of aircraft that have different custom cameras and no matter WHAT i do, there is a saved custom camera that is in some VERY odd position, that cannot be overwritten by my save. (seen it on the H125 and the Cessna)
The custom views seem to work only for the Variant to save them on. They work for different liveries as well for that variant at least for the planes I work with so far. This is in no way a workaround or consider a fix the views should stick per variant it sucks to redo them 3 times or more in my case.
There maybe a deeper issue here with other planes but the 3 planes I setup so far the views are sticking as long as you dont change the variant.
I have spent over two hours tinkering with this system and even tried creating custom profiles for a few airplanes. There are too many bugs in the settings that do not allow custom views to be retained from one flight to the next, and it’s unacceptable! The Daher TBM just won’t allow me to set a custom view ‘5’ with the Alpha yoke; the simulator reverts to the front of the plane. Why is this so broken? Why is this not being fixed, Asobo Microsoft? Is this what $140 gets us?
That view is my view each time I reset my pilot view. The saves work for other custom saves and loads as well the kicker is the variant must stay the same. You change for wheeled to float variant for example the float is considered a whole other plane needing its own customs, and it sucks.
Couple of these buttons are custom saves works all the time I load in plane this is my stream deck layout
With all that I agree 2024 is a mess, seems like a whole other team from ground up refuse to even look at 2020 for all the good things and now we are back to square one fixing and patching 2024 for a long time to come. I dont mine new but this should have been MSFS2025 at least.
Just adding a vote to this topic. This is probably the most annoying bug I’ve encountered yet, and I’ve experienced a hell of a lot of bugs. It’s not going to be an issue for anyone if they stay in the same aircraft. But If you get into an aircraft and save custom cameras, then get into another aircraft and save custom cameras, it seems to recall the cameras from the previous aircraft when selected.
Only way I have found to “fix” it, is to restart the sim. And lets be honest. That’s not really an acceptable “fix”.
Just to add my experience in. I was very used to being able to set custom camera views to ALT keys on the keyboard. I lived on these views in fs2020 and was keen to set them up in fs2024. So I was frustrated to find that ctrl+alt+1,2,3,4 etc were not functioning as I usually expected using the default fs2024 profile for keyboard.
Then I found that using the 2020 profile for keyboard map reverted that situation to where I could setup and use custom cameras again like I was used to.
However - and this is where it gets interesting, when you save a new keybind it doesnt save it to the default fs2020 profile keybinds it saves it to a new profile name eg. something like “my new keyboard profile”.
Now what I found was if you accept that default name instead of renaming it to something more obvious eg “my new keyboard profile - Twotter” every time you modify a profile again on any aircraft it will also use the default “my new keyboard profile” too. So for example on the Twotter I had set up custom cameras for the keyboard, but they seemed to work once then suddenly on next flight they would stop working. It took me ages to find that I had duplicate profiles all called the same thing, but only one of them had my custom camera views for the Twotter saved in it. I went through them and deleted all the extra ones (about 4 of them) with the same name and the one with saved camera views is now saved to have the word Twotter in it to make it more obvious as to what it is.
So it’s worth checking for duplicates if you are using the default new profile names instead of renaming them to somehting you will remember. I’m not sure if all these duplicates are a bug or not or just my inexperience. It’s very likely though that they came from other aircraft when I went in to customise their keyboard commands and forgot to give them a memorable name.
Adding my vote. I have been able to define sets of save-load view keyboard combinations but this works only for some aircraft. In others, when I try to save a different view, the load command still gives me the default view (whatever was programmed originally).
