Microsoft Flight Simulator Build version
MSFS 2024 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 sim window while continuing to move the joystick around
As soon as the mouse is over the undocked sim window 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 content area of the undocked window.
Move the mouse cursor away from the undocked window 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 or sim window like ATC/camera/weather/VFRmap.
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 also exists in 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.
Ever since they allowed Xbox users along for the ride, itās been broken. They must be lovinā those ābig dollarsā theyāre getting from the console group to forget the PC users even exist.
I just found that I can control the plane with joystick while having the cursor working on something in LittleNavMap. I am not sure if that was the situation earlier.
But using the EFB is still a problem if you want it in a separate window. EFB location as mounted in the cockpit means that if you want to use it there and not in its own window then your view angle on everything else is really skewed and its pretty hard to control the plane unless you are on autopilot (and there is no autopilot in some planes).
Unbelievable that if your cursor is working in EFB window then your joystick or any other airplane controls donāt work and you have to keep mousing out of EFB window back into the main screen to keep on course and not crash.
As long as Iām tracking this issue (years) it behaves exactly as you describe.
The issue seems to be only related to undocked MSFS windows.
No matter whether youāre using BeyondATC, LittleNavMap, Navigraph Charts, a web browser or just windows explorerā¦ No issues.
But if the mouse cursor is positioned over an undocked simulator window, it deactivates the controls in the simulator itself.
It took me a minute to notice the issue as I usually pop out displays onto a couple iPads and then never interact with the displays directly, so my mouse is usually on the primary screen without the pop outs.
Did run into this the other day though after using the mouse to interact with the radio panel on the Vision Jet and ended up taxiing off the taxiway as my brakes no longer worked because the mouse was over the radio panel still.
Well itās not (only) a focus issue. A window doesnāt get the focus just by hovering the cursor over it.
So it would be great to get your vote here as well.
Itās still broken and seems to affect all HID devices including Keyboard.
Looks a bit like the HID is fetched in main thread and the threads for the undocked windows is interfering when hoverd by catching the HID awareness (as mouse still works). But all the other HID events are not āforwardedā to the main thread and not handled by the undocked windows.
It would be great if this issue were resolved sometime in the near future.
Iāve experienced nerve wrecking moments already trying to respond to the moderately impatient ATC lady by mousing over the ATC window on my secondary monitor, hoping Iāll be in time to avoid the passive-agressive ādid you receive my last transmissionā coming through from the other end of the radio, while in a banked turn to catch the VOR radial, only to see the nose dropping and the bank quicky developing into a death spiral.
What kind of simulated reality is this, where reaching out with my right hand to manipulate a radio PTT switch causes my left arm and both my legs to become uncontrollable?
add the fact that I cannot use touch properly on the popped out EFIS like the G3x. Double-tap to highlight the button blue, then another touch to actually āpressā it. all other software including AirManager just works nicely with the touchscreens - only those MSFS 2024 popouts donāt properly work. And it does not matter if itās real hardware touchscreen or just space desk. MSFS 2024 popouts canāt handle touch inputs - why?
