I'm trying to create a custom cockpit view but I've not been able to succeed.

I sit in the cockpit and adjust the view to my liking and then press the key combination to save a custom view, e.g. ctrl-alt-0 with the default key binding. When I'm then in another view and want to go to my custom view I press e.g. alt+0. This causes an infinite loop where MSFS appears to be struggling between two different views, causing a flickering/flashing effect where it goes between those two views about 20 times a second. It does not stop until I go to e.g. external view and then back into the cockpit. However, every single attempt to load the custom view enters the flickering loop again.

Any ideas?

I've googled this issue and I can see that several users have experienced this exact issue over the last 2-3 years. Some of these users had conflicting key bindings, causing MSFS to load two different views at the same time. This makes sense, but unfortunately this does not seem to be the problem for me. I've checked, double checked and then checked again. No conflicting bindings. I've tried the default key bindings, I've tried several other (unused) keyboard bindings and I've even added the save/load custom view bindings to a joystick that is completely clear of any other assignments. Still the same problem every time though.

Any ides?

Also a related question, can you enable some kind of notification or see in a log file that a custom view was actually saved? MSFS is usually very verbose (to say the least) when it comes to tips and notifications, but when doing things like saving custom views it seems that one can only assume or hope that it worked.

 

 

I have the same problem for long time 

Nobody knows? I even uninstalled MSFS, cleaned out any traces of it, and reinstalled it again from scratch. Same problem.
I've also found many other bugs and issues even though I've just started. In 95% of the cases when googling them I end up in some thread or bug report from years ago with frustrated users wondering why it's not fixed. Sometimes there is some answer from Asobo that they will look into it (which they appearently don't) but most often there isn't even an answer.

For example the completely broken "home cockpit mode" reported in 2020 that is still in 2023 just as broken. For cockpit builders seeking to remove the VC it seems we're supposed to use terrible workarounds like creating a custom camera in front of the VC's front window (which will totally screw upp the view aspect/angle). Unfortunately I can't even save that view due to the bug described in my first post.

Having lived with LM's inability to fix even the most basic bugs for many years I'm really, really sad to see that MSFS is in the same state.

The interesting thing is that others work and we don't. Perhaps we have some special configuration of additional hardware that bite. Have you tried disconnecting all peripherals and leaving only the keyboard?