Microsoft Flight Simulator Build version
MSFS 2024 tech alpha and 2020 1.36.2.0
Steps to reproduce
Start MSFS in safe mode to avoid conflicts with community content
Assign elevator and ailerons to a joystick within MSFS
Load any stock aircraft with glass cockpit element (TBM 930 for instance) and ensure the assigned controlls work well
Undock a glasscockpit gauge or the VFR Map
Start moving around your joystick continously so that you see the inputs on your VC
Start moving the mouse cursor over the undocked panel while continuing to move the joystick around
As soon as the mouse is over the undocked panel the control inputs are not received/accepted by the MSFS main window. The controls “freeze” on the position they’ve been when the mouse entered the area of the undocked gauge.
Move the mouse cursor away from the undocked gauge while still moving the joystick will lead to MSFS catching up the movements and applying it to the in-sim aircraft.
Expected result
The assigned controls in MSFS work as long as the sim is running, no matter where the mouse hovers or which application is the active window. Like in P3D, XPlane, FSUIPC, AxisAndOhs, SpadNext, Mobiflight and all the other applications.
Actual result
Controls assigned in MSFS stop working when the mouse hovers over an undocked glass cockpit gauge.
Repro Rate
Every time (100%)
Hope that helps, and we get it fixed soon.
Disabled controls make the aircraft not flyable. Undocked panels are standard in larger home cockpit setups and this bug was confirmed by the developer of Popout Panel Manager for MSFS 2024 as well.
Pretty impressive that only six votes we’re collected so far.
So really no one using the undocked panels or popout panel Manager? Or are those users not using a Mouse?
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
The issue can be easily reproduced with all undockable windows as well!
As long as the map is not undocked, it’s all good. But if you undock the map from the main MSFS window (even if you keep it on the same location) the assigned controlls stop working when you hover the mouse cursor on the VFR map.
The issue happens also on trying same with the //42 campout utilities, GSX Main Menu, Flight assistant window, Weather-Panel, Camera Panel, Bushtalk radio etc.
It seems like the issue is related to the window management of MSFS and completely independent from WHICH panel / window is undocked.
So no excuses like It’s an 3rd party issue…
Sad that issue is known since years but even with the full rework of the controller stuff in MSFS24 was never tested.
You seem to be describing a characteristic of the Asobo FS series which has always existed. While flying, if you mouse your cursor out of the active application (MSFS) then all control inputs are disabled. This includes moving cursor to one of the popout screen views.
I reported this years ago for FS 2020. l am afraid it was accepted as simply a characteristic of the app and not a design bug. I am quite sure I did not have this problem with previous versions of the MSFS series dating back to the beginning in the 1980’s.
I like to have LittleNavMap opened on my laptop screen below my main screen. Have to be real careful to be in stabilized flight mainly use autopilot or just pause the sim whenever I want to do something in LNM, etc.
I too am surprised that my much earlier request about this issue did not raise more interest. By this time, 4 years into it with 2020, it has been simply accepted as a something you have to get used to. The sim would be a whole lot friendlier if they could figure out this issue and solve it.
Right along with this issue is the request for multiple fully functional windows within the app. Probably involves some of the same technical problems to implement, or would require too much processing power now that the sim is stretching the capabilities of our machines to the limit. FS2024 added something called a second window, but it is simply a duplicate of the original in all respects - what is needed is multiple windows where the camera can be located to give different views customized by the user.
Thanks for your insights.
As neither P3D nor Xplane have these issues, I still hope, that Asobo/MS one day understands that there’s a world outside MSFS.
I don’t wanna believe they see the demand for working controls while flying as relevant only while the user stays in MSFS - on a single Window - it would be far away from “as real as it gets” or the community and open Plattform approach.
Then all 3rd party vendors developing applications being run outside MSFS are pushed into the “unwanted” corner.
And why would we then need Simconnect API and such?
So I’m still hoping that this bug gets fixed soon.
