@RoastGnu, I updated to 3.4.1 just now and took it for a test ride. The touch functionality is very noticeably smoother! Panning the map, working the scroll bars, the response time of the number keys. It’s really works fantastic, job well done, thoroughly impressed! Thanks again!
Hi,
Thank you for this great piece of software. It is really a game changer.
Since 3.4.1 everything is much more responsive and very smooth but I have an issue with a RealSimGear GTN750 Gen1 hardware. The “refocus” isn’t working anymore as it was in 3.4.0. Single click and mouse drag are ok but then the mouse cursor always stays over the panel and doesn’t come back over the main MSFS window.
I checked the Preferences settings, and also if the new “Disable Games Refocus” option was not checked. All were ok, so I tried to use the same pop out panel (PMS50 GTN750) on another touch display in the same game session and it behaved very well as awaited.
This other display is using the standard Windows 10 drivers, but the RealSimGear GTN750 is using a PenMount driver as the GTN750 is a GEN1 RealSimGear device.
Any idea to perform more tests? Can we get more verbose logs? Should I try to uninstall PenMount drivers and use standard Windows ones instead? I’m not sure to be able to calibrate the touch screen without the PenMount drivers.
Thanks again for your work,
Philippe.
Hi The1/2p,
Would you please try increasing the refocus delay to 1000 milliseconds or higher (v3.4.0 default) in preference setting. In v3.4.1, I’ve adjusted it to a more aggressive 500 milliseconds by default after touch inactivity.
Thanks a lot for this feedback,
I thought of that and already tried to set it to 2000ms but did not see any mouse event fired.
I started the 3.4.0 version with the same profile, and the refocus was working again.
Hmm… how refocus work is pretty simple. Once your last touch is registered, my code starts a timer for say 500 milliseconds and if no new touch is detected, it will use code to move your mouse cursor away from the panel to the center of the game window which in effect gives you flight control back. The mouse move code is the same for both v3.4 and v3.4.1 and the only difference in v3.4.1 is it checks for two additional flags to determine should the app move the mouse back:
Since you’ve verified the above settings already, probably something I changed regarding mouse timing is giving you issue. I’ll dissect my code and see why it was working before for you and not in v3.4.1.
Stanley
Hey gang, I’m sure I’m not doing something right there. Please feel free to tell me to RTFM. 
I did watch a YouTube video and it didn’t seem to cover what I need.
My setup:
At the moment I took that, I didn’t have the Popout … I stand corrected. I zoomed in on the bottom monitor, and it is running. I think I might have been troubleshooting before I took off. Either the iPad Pro shown or an older iPad Mini are running the Duet software to extend my Windows desktop. With that, I can move the popped-out GTN750 to the iPad no problem.
Ok - so, PMDG DC-6 with the GPS enabled, PMS GTN750 replacement with JD’s mod. As you can see, I can use the “regular” version of the GPS (it works in the housing on the upper panel, too) - if I pop it out, I can move it to the iPad. Because the popout manager didn’t move it though, I can’t use the touch feature.
I may not have set up the pop-outs correctly with the POPM. Since the GPS is attached to the upper panel in the center, it’s not visible from the default view. What’s the proper process for that?
Is it possible to manually pop out a window and then have POPM recognize it? Or does that defeat the whole purpose of the mod? 
Hi Latka,
If I understand correctly, you’re trying to select a panel which is off screen to use touch feature.
In your DC-6 profile if your haven’t created one already, create one. First click “Start panel selection”, if you’ve existing panels selected, it is going to ask you to overwrite, click Yes. Then here is the important part, don’t click anything yet but instead hold down your right mouse button and move your mouse up so GTN750 panel is visible in your game window, this is the camera angle pop out manager is going to save and use in order to pop out panels for your profile. Now, just left click once on GTN750 and then Ctrl-Left click to complete the selection. For a good measure, which is not required, click the button in Pop Out Manager “Override Auto Panning Camera” to save this camera angle. Now click “Start Pop Out” button. Your screen will do couple things, it will move your game window to center cockpit view first, then move to your custom camera view where GTN750 is visible and then try to pop it out. The rest of the process is the same. Since pop out manager is the one that pops out the panel, your touch will work as expected. The camera movement feature above is called “Auto Panning” in my app, and you can also customize settings in Preferences => Enable Auto Panning.
Please let me know if I misunderstood your requirement.
Stanley
Yes, you got it correct!
The more I think about it, popping it out and moving it to the iPad like I was doing…Iʻm doing it wrong.
Regarding the process you described, I tried just now but Windows and Duet arenʻt happy that Iʻm on a remote desktop session to my PC. Will wait until I can restart in “normal” mode to give it another shot!
@RoastGnu this should make you laugh… during my lunch break I fired up my PC normally. Fired up the POPM and the DC-6. I forgot that I already had a profile set for it (which I promise did NOT work the last time I tried it)… so I figured I’d let it do it’s thing. It popped out the GPS just fine!
I wonder if it had something to do with me messing with a bunch of MSFS stuff while it was running. Seems when I just let things go, they work.
…new toy arriving today that I can’t wait to try out the GTN750 mod + your mod on!
Hi Latka,
Glad you got DC-6 panel sorted out. I won’t be laughing since similar thing happened to me, too I was testing my code and scratching my head for almost an hour trying to figure out why panels on 737 failed to pop out. I kept changing my code over and over again and believing there must be something wrong there. Eventually, I realized I had Kodiak profile selected instead of 737 and it was staring at me all along and I just blindly kept clicking “Start Pop Out” button without seeing I had the wrong profile. LOL!
Stanley
Oh, I hear you. Whenever people call in at work and apologize for something simple I tell them, “You should see the stuff I mess up every day…and I do this all the time!”
Just like to give another positive report for the new features. The automatic activation of the Fly now button coupled with the improved time for the pop out process and more responsive touch make this version awesome. Great work.
Thanks for the huge amount of work you put into POPM (I’m a retired CAD/CAM developer).
I downloaded it and got it working. My initial suggestions:
Use the arrow keys to move the popped window origins around. One pixel per key character, auto repeat will boost the speed.
Ditto for X and Y lengths. I’ve seen that on a flightsim instrument package and a commercial CAD/CAM program I developed, for pixel perfect alignment of 2D vector data.
There’s some kind of rounding error in the X value at bottom left. I nudged a window one pixel steps until the boundary (one pixel wide) just disappeared. Back one pixel to show the boundary, but the X value was -7.
Easily done in the dark depths of Window DC coordinate depravity.
I got a bit confused with ending the window selection, couldn’t get remove last working and you allow selections within the POPM. With keyboard/mouse capture, I suggest you ignore selection clicks within your window.
A red “Finish selection” button gives another command route which would be good on a touchscreen.
Thanks again, and best wishes.
Paul
Hi TaurineCorn668,
Thank you for your insights and your suggestions.
For windows placement and sizing, there are hidden keystrokes to manage them without using buttons. In panel configuration, when you click on any of the four cell for a panel X-Pos, Y-Pos, height, and width, you can use 4 hidden keystorkes Ctrl+, Ctrl- Ctrl [, Ctrl ], to add/minus 1 or 10 pixels. You can also hover over the +/- pixel buttons to see the keystroke description but it isn’t obvious. I will probably need to add an info button screen to show user about the keyboard shortcuts.
Great idea for disabling panel selection if cursor is within Pop Out Manager.
An alternative way to end panel selection instead of just using Ctrl+Left click is definitely more user friendly. Combine with the point above, the new command route is cleaner.
The rounding error and also -8 pixels are the remnants MSFS pre-SU7 or SU8 bug which I need to work around where pop up panels have a starting X and Y location of -8 pixels instead of 0. MSFS had seen fixed the issue and I need to find a way to migrate all user’s pixel perfect panel data and shift and resize them without breaking their profile. You’re the first to point out panel coordinate is off by 8 pixels, good eyes! This is an issue that is bugging me for months and I need to find a good way to fix it without destroying all users’ profiles.
I’ll add as many of the above recommendations into next release!
Stanley
Stanley,
When you get the window handle, you can query it’s true origin from Windows (easy in MFC C++). That might workaround the MSFS bug(s).
The 8 pixel offset feels suspiciously like a shift error (100 binary) or a quirk of GPU addressing.
Using cursor keys to move in 2D space is a personal preference, but also familiar to word processor and spreadsheet users. Fairly intuitive and quick with two fingers on left/right or up/down without taking eyes off the 2D object. Of course, I’m used to flying around C++ code with arrow and other keys; they can be faster than a mouse.
See what you think.
Paul
Hi Paul,
Totally Agreed. My code is already using windows handle and Pinvoke Rect to shift window. This old MSFS bug, only happens on MSFS generated child windows and not on any other application windows. It will shift window (pop out) 8 pixels to the right after a 2nd click of the pop out window. How this bug behaved was say if you click the pop out title bar, after the 2nd click, it will keep shifting itself 8 pixels to the right per click. This was a weird bug and MSFS finally fixed it. But my code had to compensate this bug before by shifting pop out window by 8 pixels to the left (-8 pixels) and all existing user profile coordinates is now stuck. The good thing is it is now a coordinate display issue only and does not affect the functionality of Pop Out Manager. You’re probably right that it was a shift error in the pop out window and pop out window was never Asobo/MS priority. Imaging when I use PInvoke code to move a pop out window to the right for 1 pixel, it will move 1 pixel, and I move it again for 1 pixel, it will move 9 pixels since MSFS game code somehow move it an additional 8 pixels. LOL!
It is kind of hard to explain since I can’t download older version of MSFS and compare it with the latest SU. Even though my code is constantly evolving to compensate MSFS updates, I’m very optimistic that the MSFS game code is getting more stable day by day code wise (not game performance as some users had experience) compare to code from half a year ago!
As for arrow keys, I’ll add that as an extra keystrokes to move windows
Stanley
This looks great. However when I stopped flying (for the last 18 months) there was an issue back then with pop-out sim windows causing serious FPS issues. What little I can find now seems to indicate that it was once fixed but then recently broken again. What’s the current situation?
Stanley,
Your doing the best you can do. Moving from 3D coordinates to a 2D integer plane is always a compromise, because the integer grid snapping can always create a one pixel error.
I’m speculating, but if the Asobo mouse uses 3D coordinates and projects back to the camera view for API pixels the 1 pixel offset is unavoidable.
So don’t worry about ±1 pixel mouse errors. As Obi-Wan would say “they are not the pixel errors you are looking for”. Move along.
Btw My PFD popout is clipped in Y also, at screen bottom. Looks like 8 pixels
Oooooh look what just showed up a few hours ago! I know I have an HDMI cable around here somewhere. Might have to wait until tomorrow evening to get it all set up.
So on top of my Alpha / FIPs it would block the middle 1/3 of my bottom monitor.
This might work though - it’s far enough out that it’d just barely ad to what can’t be seen now. I’d probably left-adjust it though rather than the right side.
Has the ability to locate a sim window been removed from POPM. I was about to give it a try with the menu GTN but I don’t see the tick enablement in the preferences anymore. I gave it a go regardless but no luck.
