That should not be the case when it comes to physical hardware such as a yoke or pedals but still MSFS stops accepting input from them. Xplane doesn’t do that so it’s a clear issue that needs resolving.
1 Like
Good point 
I don’t think you actually understand the problem that’s being described here, and your justification as to why it’s like that is quite wrong.
The loss of input when focusing on pop out panels is unique to popouts, not to other Windows applications. You can use ANY 3rd party program on the same PC. You can switch in and out of MSFS without issue and still issue hardware commands either from your physical controls (yoke, stick, pedals, any external hardware or software using SimConnect). You can use helper apps, browse the web, etc with zero loss of input control. So that whole “Windows waits for the user to move focus to another window” is completely wrong.
The issue ONLY exists when one of its own popout windows gets focus. In fact, you don’t even need to give it focus. Pop out the ATC panel, as an example, and simply move your mouse over the popout without actually clicking it. It doesn’t actually have focus since it wasn’t clicked, but you lose all input control. Move the mouse out, again without clicking, and control returns.
This is a BUG, not normal behaviour.
In fact, it wasn’t always this way. This bug was introduced with the VR update last December that also had a huge effect on performance when popping out windows. Prior to the VR update, there was no issue with losing focus like this.
As for running Air Manager on another PC to avoid this, that’s also wrong. I run AM on the same PCand always have. I get no loss of input when using my touch panels. Plus, running AM on another PC immediately negates the ability of using popout windows for things like PFD / MFD, since you can’t move those to another PC. Now, running AM on another PC or tablet for instruments that don’t require popouts is a good idea, as it doesn’t take resources from the main system running the sim. But it in no way has anything to do with the problem people are reporting in this thread.
3 Likes
I can see how the VR support mangles mouse/keyboard capture.
Windows will only send keyboard events to the active window. Have you written any Windows software prior to MFC? (1993). If you have you will understand how windows filters events.
You can only type into one Windows’ window - the one that has the input focus, indicated by a flashing cursor.
It is possible for a window to capture WM_MOUSE_MOVE events and then gain input focus. It looks like Asobo have done that to make VR work. Its worth mentioning the XBox world has one display window, which throws a spanner in the multi-monitor requests.
My comments are relevant to how C++ code operates, not what you see in FS which as you say was modified for VR.
Cheers
Paul
1 Like
Also I wonder if simply the popout window was intended for view only. That might explain why input events like touch are ignored and not handled correctly.
Modifying NavSystemTouch.js seems worthy of time.
Paul
In any case, it’s a bug. It wasn’t like this initially. The VR update last December broke popouts in many ways. This loss of control is one of the issues that was introduced in that update.
It’s quite obvious that popout windows are never tested by Asobo’s internal testers if they missed this.
I wouldn’t think it would be intended for view only, considering it works perfectly fine if you use a mouse in popout mode. It’s clearly made so you can use it on another display with a mouse if you really wanted to.
I would also like to see this bug fixed along with the FPS issues involved with popping out these displays to another monitor takes.
1 Like
Even using a mouse to try to control a popout does not work for me. It’s literally display only when popped out.
Mouse seems to be hit or miss. It works for some people, not for others. It works for me if I run the sim on my 4k 16:9 monitor. Doesn’t matter what monitor I move a popout to, it works with a mouse.
If I run from my UWQHD 21:9 monitor, popups don’t work when moved to other screens. I suspect aspect ratio somehow messes things up.
The fps loss with pop outs is ridiculous…
And it’s gotten worse lately. So much so that I can’t fly the CJ4 anymore without turning visuals way down.
Yeah, this problem has been around for over a year but it’s worse now, which is why I made that post.
Then there’s the touch not working, which precludes me from enjoying any G3000/5000 or G3x planes.
It’s frustrating.
1 Like
And also precludes those of us using touch setups from using the incredible PMS50 GTN750.
But agreed. This would take planes with the G3X, the TBM and Longitude to the next level of realism if touch worked. Right now, I can’t be ■■■■■ to fly any of them, even though I quite enjoy them.
1 Like
The reference to
is interesting.
In that data CoherentGTDraw seems to be a problem. A Google search finds lots of other problems in this forum related to CoherentGTDraw affecting FPS.
Simmers found high cockpit refresh rates to be a FPS killer, for some planes. There are claims that setting cockpit rendering to LOW in Options improves FPS.
-Paul
PS: Has anyone tried a 2nd GPU card for the pop out windows? Do those with 12-core CPUs get better results?
There was someone in another thread who claimed this helped. I run a 2080 as my GPU. Normally my 2 Air Manager monitors are running off a USB-C to 2 x HDMI adapter. Tried adding in my son’s old 1070 and connecting my Air Manager monitors to that. After much messing around, I wasn’t able to replicate the results. I got the same frame rate drop no matter what.
Unlike what some others have reported, I seem to have no ill effect from moving my popouts to different monitors, even the ones on the USB to HDMI adapter. I take the frame rate hit from popping them out. What I do with them after that is inconsequential.
1 Like
Hi,
I just finished my new home cockpit setup, including a new Lenovo Tab P11 (which I recommend, low budget but high quality and speed!). I wanted to use Spacedesk to use the Lenovo Tab as my 6th monitor, specifically for the G3000 FMC. I knew that touch screen monitors and MSFS Popout instrument pretty much don’t work together.
Did anyone by any chance find a workaround? Or any tips? Would love to make it work!
Sending a bug report to Zendesk, hope it helps.
1 Like
SU8 didn’t fix any touchscreen issues. I submitted a Bug request, but doubt that does anything.
Annoying simple things like this can’t be fixed.
There will be a huge bug list and they all have to be prioritised. Which ones go to the top of the list probably relates to % of users affected + strategic plans from Microsoft. If it remains low priority it will not get fixed until the list is much shorter. I suspect we might see a fix when we get multi-monitor.
good morning, can you kindly tell me where to find the MFD PFD commands for tbm930 to put on my stream deck? thank you very much
Download and install Mobiflight: Download MobiFlight for MSFS2020, P3D or X-Plane using Arduino.
This will install the Mobiflight WASM module MSFS. Then you can send Simconnect events for the PFD / MFD including the extended ones that Mobiflight has added. You will need to do some research to get the full list (there’s useful stuff on the Mobiflight forum, and you can pick apart the files from the WASM module), but this paste (it’s a bit old, so there will be more now) lists a lot of them:
MobiFlight Event Module SimConnect Event IDs - Pastebin.com
I use Spad.neXt to send these Simconnect events to the sim when buttons on my PFD / MFD are pressed.
This workaround for spacedesk allows you to use the panels on a tablet. Using an iPad to control the 787 fmc pop out.
This is the new workaround if you still want to use the mouse touch input instead of actual touch screen input.
– connect your viewer app first
– open the device manager then click “View” tab “Device by connection”
– go to spacedesk Virtual Bus and expand it
– initially you will find spacedesk Mouse and spacedesk virtual HID Device (HID Keyboard Device)
– try to send a touch input from your viewer app and you will find another spacedesk virtual HID Device with HID-compliant touch screen underneath
– Just right-click disable both spacedesk virtual HID Device and HID-compliant touch screen underneath it
Then you will notice on your next touch input it will now use the mouse touch input.
Thanks a lot for this @dohspc. This is the best solution yet! Still a bit clunky on my ipad, as it seems sometimes touches are not registered, but it still works well enough for me to operate the PMS GTN 750 with touch.
And of course, the annoying issue where control input is not registered when you focus on a popped out panel, so fingers crossed Asobo will fix that!