Popout Failure

[Kenny584]

Hello there. I am using Version 4.0.1.0002 and I am unable to pop out any panels. I am using Windows 10. I used to be able to popout panels in the longtitude before but am now getting this error message with the latest updated version. I cannot find the Error.log file in my installation folder. I have attached two screenshots for you. I have also tried following the Getting Started Guide and the PFD and MFD panel Failed. However, the GTN 580 (Touch) panel popped out but it contained the PFD window even though it was labelled as the GTN.

I have attached two screenshots for you. Regards...Kenny.

[hawkeye-stan]

Please try the latest 4.02 beta-5 from my pre-release section. https://github.com/hawkeye-stan/msfs-popout-panel-manager/releases/tag/v4.0.2

MSFS AAU2 broke CJ4 pop out function and it could have broken Longitude, too. The latest v4.02 beta-5 fixed the pop out issue in CJ4 problem and it may fix your longitude pop out issue too. Unfortunately, I only have the standard version of MSFS and is unable to test longitude with POPM.

Stanley

[Kenny584]

Hello Stanley.

Thank you for the prompt reply. I appreciate it. I'll certainly try the beta-5 release and report back to you.

Best Regards...Kenny.

------ Original Message ------ From: "Stanley" @.> To: "hawkeye-stan/msfs-popout-panel-manager" @.> Cc: "Author" @.***> Sent: Monday, 28 Aug, 23 At 01:28 Subject: Re: [hawkeye-stan/msfs-popout-panel-manager] Popout Failure (Issue #91)

Please try the latest 4.02 beta-5 from my pre-release section.

https://github.com/hawkeye-stan/msfs-popout-panel-manager/releases/tag/v4.0.2 https://github.com/hawkeye-stan/msfs-popout-panel-manager/releases/tag/v4.0.2 MSFS AAU2 broke CJ4 pop out function and it could have broken Longitude, too. The latest v4.02 beta-5 fixed the pop out issue in CJ4 problem and it may fix your longitude pop out issue too. Unfortunately, I only have the standard version of MSFS and is unable to test longitude with POPM. Stanley — Reply to this email directly, view it on GitHub https://github.com/hawkeye-stan/msfs-popout-panel-manager/issues/91#issuecomment-1694815480 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKVUOFLVNWVFF52CBRE2IILXXPQZDANCNFSM6AAAAAA4AL6W3M . You are receiving this because you authored the thread.Message ID: @.***>

[Kenny584]

Hello again Stanley. Here is a quick update for you. In the Longitude, I position the Green, Red and Blue circles over the PFD Touch Screen Controller, MFD TSC and the MFD. However, after clicking on the Start Pop Out button, the cockpit view changes and the three circles appear on-screen in a different location. This causes the pop out to fail. I have tried selecting the panels one at a time, with limited success. One time, the PFD controller popped out but I was unsure how to retain it. When I then selected it again along with another panel, it failed them both by moving the circles. Another time it popped out the PFD TSC but it contained the PFD screen not the controller. This is with the beta 5 release. I am going to see if I still have the zip for an earlier version.

Regards...Kenny.

[hawkeye-stan]

Hi Kenny,

I'm guessing somehow MSFS custom camera view is not saving correctly on your machine. First, check if you can load/save custom camera view consistently which POPM uses. When you're in flight, in POPM, click the "panel source target icon" once, this will load the custom camera view used for the profile (default is Ctrl-Alt-0/Alt-0) and all your number circles should line up where you want them to be. If not, adjust the circles and click the "panel source target icon" again and this will force save the camera view. Next, move your cockpit view around and click the target icon again. The view will shift and the circles should line up again. Finally, click the target icon again to complete the setup. If everything works, start pop out should be able to load the custom camera view and pop out panels correctly.

If you perform the above steps and loading and saving of camera view is not consistent, then something is off. Check if MSFS keyboard controls are set to load/save custom view and they match what is defined in POPM preference setting. You can pick a different Ctrl-Alt-Number combination as needed.

If none of above tricks work, then something else is causing your issue and POPM is unable to move camera view around correctly in order to click on your defined panels to pop them out..

[Kenny584]

Hi Stanley.

Thank you for the detailed reply. I appreciate it. There is something screwy going on with my camera views. The first press of Alt+0 always takes me to a different view to the one that I have saved with Ctrl+Alt+0. I'll spend some time going through them to sort it out. It's driving me nuts!! I had my custom cockpit camera views for the Longitude saved to my keyboard Num Pad, and they all worked fine. Now that I am trying to set up a default view as per your instructions, it is not working as it should. I'll get to the bottom of it eventually. I'm wondering if it is a default sim view that is saved somewhere.

I'll post back with any results. Regards...Kenny.

------ Original Message ------ From: "Stanley" @.> To: "hawkeye-stan/msfs-popout-panel-manager" @.> Cc: "Author" @.***> Sent: Wednesday, 30 Aug, 23 At 03:13 Subject: Re: [hawkeye-stan/msfs-popout-panel-manager] Popout Failure (Issue #91)

Hi Kenny, I'm guessing somehow MSFS custom camera view is not saving correctly on your machine. First, check if you can load/save custom camera view consistently which POPM uses. When you're in flight, in POPM, click the "panel source target icon" once, this will load the custom camera view used for the profile (default is Ctrl-Alt-0/Alt-0) and all your number circles should line up where you want them to be. If not, adjust the circles and click the "panel source target icon" again and this will force save the camera view. Next, move your cockpit view around and click the target icon again. The view will shift and the circles should line up again. Finally, click the target icon again to complete the setup. If everything works, start pop out should be able to load the custom camera view and pop out panels correctly. image https://user-images.githubusercontent.com/72271266/264206367-9d23b681-d1e8-427b-a2ba-827268c77df4.png If you perform the above steps and loading and saving of camera view is not consistent, then something is off. Check if MSFS keyboard controls are set to load/save custom view and they match what is defined in POPM preference setting. You can pick a different Ctrl-Alt-Number combination as needed. image https://user-images.githubusercontent.com/72271266/264206871-d8f33af9-647a-4dd4-a5e2-2b6c0cba215b.png image https://user-images.githubusercontent.com/72271266/264207003-2b886ed0-d78b-4150-89d0-c40e21c0d751.png If none of above tricks work, then something else is causing your issue and POPM is unable to move camera view around correctly in order to click on your defined panels to pop them out.. — Reply to this email directly, view it on GitHub https://github.com/hawkeye-stan/msfs-popout-panel-manager/issues/91#issuecomment-1698387995 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKVUOFMHLJZSUAXPV7WJJVLXX2OWDANCNFSM6AAAAAA4AL6W3M . You are receiving this because you authored the thread.Message ID: @.***>

[Buurman166]

Check your camera settings in the menu (Options-General-Camera). Altitude, Zoom and horizontal position should be set to 50. This was the solution for me.

[hawkeye-stan]

The latest beta also provide workaround for MSFS bug where custom camera view does not save and load correctly when zoom level is set to value other than 50. Thank you Buurman166 for pointing out the MSFS issue. If not using the latest beta, the custom view that POPM relies on may not work.

[Kenny584]

Hello again Stanley and Buurman 166.

I have checked my settings as you have described, but unfortunately, I am still getting a failure on all three panels. I have attached a screenshot for you. I'm really puzzled as to what has changed with me as I was able to pop out these panels until about a fortnight ago. I never could with the old interface but when I installed the version with the new interface it worked first time and the Auto popout setting worked just fine also. Now I cannot get them to popout. Very strange.

Cheers...Kenny.

[hawkeye-stan]

Hi Kenny,

You case is really weird since POPM was working and then sudden stopped. My guess is some combination of events may be causing your problem. First, I've uploaded new beta version (beta-6) with updated logic just for your case to help identify your issue. Please download it and try your scenario again by creating a new profile. There are many possible reasons for all 3 panels to fail in your screenshot and the most likely ones are either custom camera fails to load or POPM mouse click emulation fails to pop out your 3 panels in Longitude.

1. First check POPM preference what your definition is for pop out camera angle, in your case previously, it was Ctrl-Alt-0 so if you manually use your keyboard and execute Alt-0, MSFS should load your custom camera view.

   

2. Once you've defined all your panel circles, click start pop out. You should see the following message "loading custom camera angle" is executing, this should be really quick. But if it lasts for more than few seconds (up to 10 seconds), then it means POPM is not able to execute Alt-0 keystroke and most likely the custom camera view is missing or corrupt in MSFS.

   

When loading custom camera view failed, you will see the following message and with beta-6, POPM will no longer try to execute the pop outs:    

3. If POPM is able to execute the above step and if the number circles are not lined up with the 3 panels, you should see panel fail one after another, about 7 seconds in between since POPM will try to pop out a panel for up to 7 seconds.

   

The above are the two scenarios I can think of that will recreate your screen shot of 3 panels failed to pop out with 0 for all data (top, left, with, height).

Lastly, try to run POPM as administrator and maybe somehow Windows is blocking POPM from executing keyboard and mouse emulation and running as administrator may resolve your issue.

Stanley

[Kenny584]

Hello Stanley.

Thanks for sticking with me on this. I agree that it is really strange and that something on my end is blocking it. I'm not a techy as such, but I'm wondering about Windows Defender having a role in it. Every aspect of the procedure seems to work fine. I have my profile, I select the three screens correctly, the sim screen 'jumps' up to a close up view of the top part of the glareshield above the autopilot panel and then orients down to my 'Alt 0' screen view. I see the 'Resetting camera view (OK) message. I then get the failure message and my hopes are dashed!! I'll download the Beta6 version and report back. Oh, I'll also check that I'm running as Administrator. To be honest, I've lost track, but I'll double check.

Cheers...Kenny.

[Kenny584]

Hello again Stanley. Here is a bit of information for you that is relevant to my issue. I had mentioned my dilemma to a young IT friend. He came round to have a look and a tinker. The outcome is that POPM is now working for me!! He did not fix anything as such, but what he did do was to move the mouse pointer over each of the target circles in turn and lo and behold the panels popped out. I had said to him that it would not work as the mouse is not meant to be moved during the popout operation, but it did.

I have tried it several times now and it is working fine, but only when I select the circles onscreen by moving the mouse pointer to each in turn. If I do not select them in this way the I get the Failed message. Very strange. I am unsure if this 'fix' is peculiar to my pc or if it may help other folks also. The lack of other post here would suggest that it is unique to my pc.

I'll post back to confirm it is still working for me.

Regards...Kenny.

[hawkeye-stan]

Hi Kenny,

This tells me POPM code emulates mouse click worked but mouse cursor movement command failed on your PC. During the pop out process for each panel, POPM will perform the following steps in code to emulate MSFS pop out commands.

1. Set focus on MSFS game window
2. Using code to set mouse coordinate at the circle location
3. Send key down command to hold Right-Alt key
4. Send multiple left click command instead of single click to overcome certain aircraft bug
5. Send key up command to release Right-Alt key

POPM will repeat the above code with multiple tries extremely quickly, in milliseconds with about half a second in between tries. So, you and your friend's experiment tells me step 2 above fail and when you manually move the mouse to the correct coordinate on screen, POPM then is able to execute step 3 to 5 so the panel is able to successfully pop out.

The question is what is blocking POPM code from executing mouse move command. This could be some Windows security issue (anti-virus, windows defender, windows settings, etc) that stops POPM from moving the mouse or a pure timing issue.

So, one last try, if this does not work, I'm totally out of ideas what could be causing your issue. I've updated beta 6 release by adding couple lines of new code. I'm forcing step 2 above by setting cursor position multiple times before issuing Alt-left click. Maybe POPM code is too fast and MSFS is not able to catch up. Please download beta-6 again and give it a last try. I did not update the release to beta-7 since you're the only one that needs this new code at the moment.

Once again, thank you so much for your patience and crossing my fingers that this final update works!

Stanley

[wembree]

Had a bizarre Nvidia driver update dance (involved “boost”) which resulted in reloading MSFS and some msfs file location changes… ugh! Since then, no version of MPOP will actually pop out any panels from any aircraft. (msfs20 v. 1.33.8.0 and MPOP beta 4.0.2.0006) Panel Source displays, and all other functions of MPOP seem fine, but the actual pop out fails. Any ideas?

[JoJota]

Not sure if my issue is connected to this, posting it here just in case. I have tested the popup feature with two aircrafts, the Fenix A320 and the Flybywire A320neo. For the Fenix, I'm unable to popup any displays with this the tool (FAILED message). With the flybywire it did work with all displays, excluding the navigation display (ND). This was tested with only the aircrafts in the community folder. Latest update is installed for MSFS, Nvidia. the aircrafts, and the latest popout panel manager beta.

Edit with solution: The workaround, fixed it for me. It's important to not open any display with the ALTGR + left click shortcut before applying the workaround, as this will popup all displays outside of the monitor, resulting in no popups being visible at all, as it happened to me with the Fenix. The flybywire uses slightly different titles for their popup windows. The reason for this issue is that many non-stock planes use the same window name for the popups ("WASMInstrument") , thus all of the popups with the same name will subsequently be opened by MSFS in the last (not visible) monitor location (see here for further explanation).

[hawkeye-stan]

Hi Jojota,

You're correct, when you started a flight and manually using Alt-click to open the pop outs, depending on the aircraft, POPM will have no way to identify and re-open these panels depending on how aircraft pop outs are designed on the aircraft. Since instrumentation pop outs will not automatically open when a flight session start, you can restart the flight, which existing pop out (visible or invisible) will close and POPM will be able to pop them out correctly. The only pop outs that automatically opens are built-in ones (ATC, checklist, weather, etc) and POPM uses this feature to be able to manage them.