I solved this issue I had by deleting the keybinds I had set my cam presets on and reprogrammed them.
This was the issue:
I use my numpad for this and pre SU7 the numpad buttons had different names.
For example numpad button 4 was num left and now with SU7 it is named as num4.
This resulted in not being able to either program or load my cam views previous set with SU6.
This is because you had NUM LOCK on when you bound that button one time, and then NUM LOCK off the other time. The sim treats “4” as two different keys, so always check to make sure NUM LOCK is on or off depending on how you originally set it.
Installed SU7 yesterday, including content manager and was flying my favorite test routes, all good. Today, 24hrs later, I fired up the sim and was greeted by another mandatory update of roughly 6GB (splash screen, not content manager) which I’m now downloading. Anyone else with this?
Very disappointed after a long and hyped up wait. I can no longer take off and land any planes due to throttle and rudder being uncontrollable. The SDK has introduced new false errors that prevent me from saving any changes. Old airports that I created successfully can no longer be modified due to these false errors. Please give your customers a way to revert to SU6 and SDK 0.14.1
Really? I have been taking off and landing today without any issues with throttle and rudder though. Are you quite sure you depict the issues you have truthfully?
Yes I “truthfully” have tested with several default planes and have had the same results. Why would I make this up? MSFS 2020 is the best simulator in so many ways. I just hate to see a half baked update get released before its been adequately tested. Can you spell R-E-C-A-L-L?
Maybe you are misinterpreting things, I have not seen anyone else complaining about the throttle and rudder, nor have I experienced it myself. You know, I’ve had issues with the sim in the past, and after checking here in the forums when nobody else has been complaining about the same, I have taken a closer look at my own setup and config and always found the culprit there.
My gripe at the moment is that at night runway lights don’t show up. This happens the vast majority of the time. And they’ve gone backwards and made the black avionics screen bug worse. But I’ve been used to that problem for 3 months now and don’t envisage a quick fix, if at all.
Is there any workaround for the inability to move UI (like ATC window) in VR? I cannot move it with the mouse, nor with a controller. To be honest I cannot do anything with it - even close.