hawkeye-stan / msfs-popout-panel-manager Goto Github PK

When using Auto Pop Out Panel, the process to click "Ready to Fly" button seems to be causing issue for some users and hanging up the auto pop out process. I'll be adding the option to skip "Ready to Fly" button option when use in conjunction with community plugin I created "Ready to Fly Button Skipper" at Flightsim.to. This not only remove the wonky issue for the app in trying to click the "Ready to Fly" button but also speed up the pop out process tremendously.

Target release version 3.3.8 or 4.0

Does this work on the PMDG 737? It does not appear so.

Thanks

Hi, I use since a few weeks/month a profile to export 4 displays for the FENIX A320 to an external mini-monitor. All was still working fine yesterday.

Today, after automatic 3.4.3 update, the popout process fails.

The first two displays (PFD - ND) are exported, but the process fails for the third screen (upper ecam) and stops here.

However, the panel location overlay is ok, there's no obstruction, and I can (manually) export the display.

The error I get is : "Unable to pop out panel number 3. Please check panel's number circle is positioned inside the panel, check for panel obstruction, and check if panel can be popped out. Pop out process stopped."

When starting the panel selection process I get an Microsoft.Net Error message "Parameter is not valid" This never happened before in any older version of the tool

User reported issue in Version 3.2 Auto Pop Out Panel feature is enabled and with a profile bound to a plane, the auto clicking of "ready to fly" button does not work in full screen mode on 4K monitor.

Hi,
Thank you for this excellent product. I was able to create my 530 and 430 pop-out panels on a second monitor, but when I quit the application or MSFS simulator, every thing is lost.
Also, the folder "%userprofile%\Documents\MSFS Pop Out Manager" is not created. I understand that %userprofile% is my "C:\users\my_folder\Documents"

I have version 3.4.5
MSFS is up-to-date, both sim and world
I use Steam edition of MSFS, and it is installed on a SSD drive, different than C:
I use the application as administrator.
I installed MSFS pop out on the same drive, and made sure that the folders "mobiflight-event-module" and "zzz-ready-to-fly-button-skipper" are in the Community folder.
I made sure I have the VC++ redistributable 2015-2022 x64 installed.
I do not receive any error messages when using MSFS pop out Manager.
Any change on the Preferences are not retained after closing the application.

I hope I have given sufficient information.

Thank you in advance for your support.

Richard

Hello Mr Stan, in the video of how to use the application, it shows that when you put the pointer on the panel, the pointer changes to a little hand to select the panel. However, this does not happen in my case and despite the fact that I left click, the respective number does not appear. But if I move the pointer to the taskbar and left click then the number appears, but still I can't drag it to the panel I want to select. I would greatly appreciate any guidance or suggestion.

Depending on how a panel is constructed in MSFS since they come with different sizes and aspect ratios, the panel may expand to full screen with black bar on top/bottom or left/right.

Target release version 3.3.8 or 4.0.

When doing landing challenges, for example, it's difficult to follow course while the panels are popped out. It would be great to add an option automatically do an active pause and unpause while the panels are popped out.

Reported by Sling380 on flightsimulator.com:

When auto pop out panel is enabled, application is not clicking the "ready to fly" button consistently.

Hello Stanley and friends! I´m trying to first create a profile to configure the 2 GTC´s - Garmin Touch controls on a Honda Jet, SU10, MSFS popout manager v3.4.3 and v3.4.2 also. No success. I experience same problems, when I select instrument 1 and 2, after that, click control+left mouse and for a few seconds I see both together in a msfs popout window but something happens, and i got the same error here reported "Unable to pop out panel #" and just one of the gtc stays on popped out windows. Tried to make it work for the whole night, no success, if you guys can help or need something from me in order to help, let me know! Oh, almost forgot, both of them are able to pop out using default msfs altgr+left mouse, so , they pops out, both.!

UPDATE1: If I select just one instrument GTC at a time it works perfect, selecting both of them it goes wrong in the moment the pop out window seens to make calculations. One instrument appears completely, the other in its side just the title window, but it is there. I thing when program automation tries to click on a button title of the not totally visible instrument, to make adjustments, something goes wrong and then the reported error message. I am in 4k, 60 hz, tried with and without vsync, overlays are positioned correctly, just tested. The issue is something in the process of resizing/calculating both instruments in the same popout window.

By Voss1917:
To further make the setup more automatic, I wonder if there is a way to start the app in minimized mode by either a keypress shortcut or even better a joystick button and have it automatically run the “Start Pop Out” with the default profile I have for my G1000 screens?

Prerequisite:

• User has a profile completely setup and set as default profile

Use Case:

• Application can be set to minimize on start
• Without restoring the app window, user can either use an user-defined joystick button or a predefined keystroke combination (ie. Ctrl-Alt-P) to initiate the pop out process.

Extra:
With the app minimize to system tray, add right click context menu to tray icon to switch user profiles. This way, once the app is set to auto-start, user will never need to open the app to pop out windows or switch profile.

Good morning,
I am running a FlightDeck Solutions Airbus MCDU with POM and Device Interface Manager.
Running into an issue using when pop out manager is initially auto popping out windows while device interface manager is running I get a BSOD. I start DIM and POP via the exe.xml for ease of startup and although I could start the DIM manually after the sim is up and running I wanted to see if you could take a look at the log file and potentially have a solution. Thank you!

error.log

Reported by user. Issue added by Stanley

When using multi-monitor setup, the reliability for panel separation needs has room for improvement.

1. Investigate panel definitions and their construction (GTN 530/430 as example) to make sure current separate can work reliability on single monitor.
2. Investigate and improve the pop out process when the game monitor and primary monitor is far apart in user's setup, Also need to test when all monitors have different DPI.

Targeted fix/improvement v3.4.2

Hi guys, this software was working flawlessly until last week. Now when the panels pop out, the sim freezes and I have to shut it down through task manager. The popout manager works well with the PFD/ND on both the captains and F.O side but when I attempt to resize the upper and lower EICAS, the sim freezes. Could it be down to the screen resolutions? I am using the PMDG 737-800.
Many thanks
Andrew

I can select each of 5 screens and the numbered Circle appears but when I "Start Pop Out" it only selects the Pilots main Navigation Display

The results are here. I have triple 55" 4 K screens, 3 RSG Displays and a 27" Utility Screen run on 2 GPUs. I've spent two hours trying to get this app to work with no success.

• • Need an UNDO button if you pick the wrong display
• • Need a Clear one or all Panels Button. Each time the process fails I have to delete the Profile and start over.
    

Reported by Sling380 on flightsimulator.com:

When using C208 improvement mod operation. That aircraft requires the avionics switches on to power the G1000 screens and therefore the auto pop out panel doesn’t function. Powering up before manually starting the sequence works fine.

https://github.com/SheepCreativeSoftware/msfs2020-C208-Improvment-Mod

User reported issue:

MovedSmile53222
2h
Thanks for this tool. It seems very useful but I cannot make it work.
I have a 3 monitors set-up:
1 A 1920x1200 Main monitor where MSFS pop-up panel manager is displayed
2 My MSFS 4K TV
3 A 1920x1080 touch screen where the pop-out panels should be displayed.

I use it with A320NX FBW
I do the panel selection for the 4 main panels (starting with ND then PFD and both EICAS)
I press Start Pop-out.
Panels are extracted and they are displayed on my Main monitor.
I position them on my Touch screen.
I press File/Restart
I press Start Pop Out again.
Panels are extracted on the main monitor. I can see them briefly on the Touch screen but 3 of them return to the Main monitor. Only one stay on the Touch screen. It is not always the same.
Panel Location parameters ( X-Pos, Y-Pos, Width or Height) are correct.
If I retype one of these parameters, the panel goes at the right place on the Touch screen.

I try also with both G1000 on C172. Same thing. One panel stays on the Touch screen, the other return to the Main monitor.
The Error log seems OK.
I have one of these lines everytime I open the tool:
2022-02-11 14:00:42,280 [1] INFO MSFSPopoutPanelManager.WpfApp.App - DPI Awareness is set to: Process_Per_Monitor_DPI_Aware
I also have this line the first time I use the tool:
2022-02-10 11:56:45,725 [1] ERROR MSFSPopoutPanelManager.WpfApp.App - Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
It didn’t come back.

Thanks for your help.

Yves

Hi,

at first i want to say a big thankyou for this amazing tool.
That is very important for my Home-Cockpit.

I tried to set it up today. The problem is, that the connection icon is always red and the software is not connected to the msfs.
I installed the newest version of it. I have the msfs version 1.26.5.0 installed.

Cna you help me?

Thanks a lot

Jonas

Hi,

First, thank you for your tool!

When I launch the msfs popout panel manager, the windows shows up, connects to MSFS and then crashes.

I have the following log file and the error seems to come from mailslot but don't know much more...

Thank you,

08.11.2022 13:50:13.919 [0000375c] --- App --- SimPitWarp v4.3.1 (01.12.2020)
08.11.2022 13:50:13.919 [0000375c] --- OS 6:2 Microsoft Windows 8 Professional (build 9200) (version UNK), 64-bit 7(0) 8(0) 8.1(0) 10(1)
08.11.2022 13:50:13.919 [0000375c] --- PID [11832]
08.11.2022 13:50:13.920 [0000375c] --- Enumerating displays ...
08.11.2022 13:50:13.922 [0000375c] --- Device N[\\.\DISPLAY1] S[NVIDIA GeForce RTX 2080 Ti] M[Generic PnP Monitor] F[desktop ]
08.11.2022 13:50:13.924 [0000375c] --- Device N[\\.\DISPLAY2] S[NVIDIA GeForce RTX 2080 Ti] M[Generic PnP Monitor] F[desktop ]
08.11.2022 13:50:13.925 [0000375c] --- Device N[\\.\DISPLAY3] S[NVIDIA GeForce RTX 2080 Ti] M[Generic PnP Monitor] F[desktop ]
08.11.2022 13:50:13.927 [0000375c] --- Device N[\\.\DISPLAY4] S[NVIDIA GeForce RTX 2080 Ti] M[] F[]
08.11.2022 13:50:13.929 [0000375c] --- Device N[\\.\DISPLAY5] S[NVIDIA GeForce RTX 2080] M[Generic PnP Monitor] F[desktop ]
08.11.2022 13:50:13.930 [0000375c] --- Device N[\\.\DISPLAY6] S[NVIDIA GeForce RTX 2080] M[Generic PnP Monitor] F[desktop primary ]
08.11.2022 13:50:13.932 [0000375c] --- Device N[\\.\DISPLAY7] S[NVIDIA GeForce RTX 2080] M[Generic PnP Monitor] F[desktop ]
08.11.2022 13:50:13.935 [0000375c] --- Device N[\\.\DISPLAY8] S[NVIDIA GeForce RTX 2080] M[] F[]
08.11.2022 13:50:13.935 [0000375c] --- SM_CMONITORS         = 6
08.11.2022 13:50:13.935 [0000375c] --- SM_SAMEDISPLAYFORMAT = 1
08.11.2022 13:50:13.935 [0000375c] --- SM_XVIRTUALSCREEN    = -1916
08.11.2022 13:50:13.935 [0000375c] --- SM_YVIRTUALSCREEN    = -2160
08.11.2022 13:50:13.935 [0000375c] --- SM_CXVIRTUALSCREEN   = 5760
08.11.2022 13:50:13.935 [0000375c] --- SM_CYVIRTUALSCREEN   = 3240
08.11.2022 13:50:13.935 [0000375c] --- SM_CXCURSOR          = 32
08.11.2022 13:50:13.935 [0000375c] --- ---------
08.11.2022 13:50:13.968 [0000375c] --- ATI: No ATI GPU found
08.11.2022 13:50:13.968 [0000375c] --- GPU
08.11.2022 13:50:13.968 [0000375c] --- GPU[1] [\\.\DISPLAY1]:[NV|NVIDIA GeForce RTX 2080 Ti:1024|#|G1|3|1|0] -1916,-2160 1920x1080 Output[fffffffe] GPUs[408508296]
08.11.2022 13:50:13.968 [0000375c] --- GPU[2] [\\.\DISPLAY5]:[NV|NVIDIA GeForce RTX 2080:4096|#|G1|3|3|0] 14,-1080 1920x1080 Output[fffffffe] GPUs[408508296]
08.11.2022 13:50:13.968 [0000375c] --- GPU[3] [\\.\DISPLAY6]:[NV|NVIDIA GeForce RTX 2080:1024|#|G1|3|3|0] 0,0 1920x1080 Output[fffffffe] GPUs[408508296]
08.11.2022 13:50:13.968 [0000375c] --- GPU[4] [\\.\DISPLAY2]:[NV|NVIDIA GeForce RTX 2080 Ti:2048|#|G1|3|1|0] 1924,-2160 1920x1080 Output[fffffffe] GPUs[408508296]
08.11.2022 13:50:13.968 [0000375c] --- GPU[5] [\\.\DISPLAY3]:[NV|NVIDIA GeForce RTX 2080 Ti:4096|#|G1|3|1|0] 4,-2160 1920x1080 Output[fffffffe] GPUs[408508296]
08.11.2022 13:50:13.968 [0000375c] --- GPU[6] [\\.\DISPLAY7]:[NV|NVIDIA GeForce RTX 2080:16384|#|G1|3|3|0] 1934,-1080 640x480 Output[fffffffe] GPUs[408508296]
08.11.2022 13:50:13.969 [0000375c] --- [\\.\DISPLAY1]:[NV|NVIDIA GeForce RTX 2080 Ti:1024|#|G1|3|1|0] [NVIDIA GeForce RTX 2080 Ti] [MONITOR\OTM8652\{4d36e96e-e325-11ce-bfc1-08002be10318}\0006] [Generic PnP Monitor]
08.11.2022 13:50:13.971 [0000375c] --- [\\.\DISPLAY2]:[NV|NVIDIA GeForce RTX 2080 Ti:2048|#|G1|3|1|0] [NVIDIA GeForce RTX 2080 Ti] [MONITOR\OTM8652\{4d36e96e-e325-11ce-bfc1-08002be10318}\0007] [Generic PnP Monitor]
08.11.2022 13:50:13.973 [0000375c] --- [\\.\DISPLAY3]:[NV|NVIDIA GeForce RTX 2080 Ti:4096|#|G1|3|1|0] [NVIDIA GeForce RTX 2080 Ti] [MONITOR\OTM8652\{4d36e96e-e325-11ce-bfc1-08002be10318}\0008] [Generic PnP Monitor]
08.11.2022 13:50:13.975 [0000375c] --- [\\.\DISPLAY5]:[NV|NVIDIA GeForce RTX 2080:4096|#|G1|3|3|0] [NVIDIA GeForce RTX 2080] [MONITOR\ROW0000\{4d36e96e-e325-11ce-bfc1-08002be10318}\0044] [Generic PnP Monitor]
08.11.2022 13:50:13.976 [0000375c] --- [\\.\DISPLAY6]:[NV|NVIDIA GeForce RTX 2080:1024|#|G1|3|3|0] [NVIDIA GeForce RTX 2080] [MONITOR\IVM661E\{4d36e96e-e325-11ce-bfc1-08002be10318}\0038] [Generic PnP Monitor]
08.11.2022 13:50:13.978 [0000375c] --- [\\.\DISPLAY7]:[NV|NVIDIA GeForce RTX 2080:16384|#|G1|3|3|0] [NVIDIA GeForce RTX 2080] [MONITOR\HTR4628\{4d36e96e-e325-11ce-bfc1-08002be10318}\0045] [Generic PnP Monitor]
08.11.2022 13:50:13.980 [0000375c] --- Enumerated 6 displays
08.11.2022 13:50:13.980 [0000375c] --- Displays initialized
08.11.2022 13:50:13.980 [0000375c] --- Displays[0] M[00010003] HDC[f90117df] GDC[04010b1b] L=-1916 T=-2160 R=4 B=-1080 RECT[-1916,-2160 1920x1080] N[\\.\DISPLAY1]:[NV|NVIDIA GeForce RTX 2080 Ti:1024|#|G1|3|1|0] M[Generic PnP Monitor] F[0] PROJ[1x1] MAPS[1]
08.11.2022 13:50:13.980 [0000375c] ---    Grouping G[0] N[0] GD[]
08.11.2022 13:50:13.980 [0000375c] --- Displays[1] M[00010005] HDC[41010c33] GDC[f3011724] L=14 T=-1080 R=1934 B=0 RECT[14,-1080 1920x1080] N[\\.\DISPLAY5]:[NV|NVIDIA GeForce RTX 2080:4096|#|G1|3|3|0] M[Generic PnP Monitor] F[0] PROJ[0x0] MAPS[0]
08.11.2022 13:50:13.980 [0000375c] ---    Grouping G[0] N[0] GD[]
08.11.2022 13:50:13.980 [0000375c] --- Displays[2] M[00010001] HDC[c5010b07] GDC[ff011758] L=0 T=0 R=1920 B=1080 RECT[0,0 1920x1080] N[\\.\DISPLAY6]:[NV|NVIDIA GeForce RTX 2080:1024|#|G1|3|3|0] M[Generic PnP Monitor] F[1] PROJ[0x0] MAPS[0]
08.11.2022 13:50:13.980 [0000375c] ---    Grouping G[0] N[0] GD[]
08.11.2022 13:50:13.980 [0000375c] --- Displays[3] M[00010007] HDC[4c011754] GDC[350116e5] L=1924 T=-2160 R=3844 B=-1080 RECT[1924,-2160 1920x1080] N[\\.\DISPLAY2]:[NV|NVIDIA GeForce RTX 2080 Ti:2048|#|G1|3|1|0] M[Generic PnP Monitor] F[0] PROJ[1x1] MAPS[1]
08.11.2022 13:50:13.980 [0000375c] ---    Grouping G[0] N[0] GD[]
08.11.2022 13:50:13.980 [0000375c] --- Displays[4] M[00010009] HDC[0e011728] GDC[b2010c4a] L=4 T=-2160 R=1924 B=-1080 RECT[4,-2160 1920x1080] N[\\.\DISPLAY3]:[NV|NVIDIA GeForce RTX 2080 Ti:4096|#|G1|3|1|0] M[Generic PnP Monitor] F[0] PROJ[1x1] MAPS[1]
08.11.2022 13:50:13.980 [0000375c] ---    Grouping G[0] N[0] GD[]
08.11.2022 13:50:13.980 [0000375c] --- Displays[5] M[0001000b] HDC[e2010ac9] GDC[370111fa] L=1934 T=-1080 R=2574 B=-600 RECT[1934,-1080 640x480] N[\\.\DISPLAY7]:[NV|NVIDIA GeForce RTX 2080:16384|#|G1|3|3|0] M[Generic PnP Monitor] F[0] PROJ[0x0] MAPS[0]
08.11.2022 13:50:13.980 [0000375c] ---    Grouping G[0] N[0] GD[]
08.11.2022 13:50:13.980 [0000375c] --- ---------
08.11.2022 13:50:13.980 [0000375c] ??? Model:Error connecting to mailslot
08.11.2022 13:50:13.980 [0000375c] --- hookD3D9
08.11.2022 13:50:13.981 [0000375c] --- DirectX9 dll=eace0000
08.11.2022 13:50:13.985 [0000375c] --- DirectX9 API detected
08.11.2022 13:50:13.985 [0000375c] --- DirectX9Ex API detected
08.11.2022 13:50:13.985 [0000375c] --- i1: InterfaceProc1
08.11.2022 13:50:13.985 [0000375c] --- interfaceFunc1 MaxHTProjectrs=0
08.11.2022 13:50:13.985 [0000375c] --- interfaceFunc1 [\\.\DISPLAY1] totalMaps=1
08.11.2022 13:50:13.985 [0000375c] --- interfaceFunc1 [\\.\DISPLAY2] totalMaps=1
08.11.2022 13:50:13.985 [0000375c] --- interfaceFunc1 [\\.\DISPLAY3] totalMaps=1
08.11.2022 13:50:13.986 [0000375c] --- DXGI dll=1e670000
08.11.2022 13:50:13.988 [0000375c] --- DirectX DXGI API CreateDXGIFactory detected 1
08.11.2022 13:50:13.989 [0000375c] --- DirectX DXGI API CreateDXGIFactory1 detected 1
08.11.2022 13:50:13.991 [0000375c] --- DirectX DXGI API CreateDXGIFactory2 detected 1
08.11.2022 13:50:13.991 [0000375c] --- DirectX DXGI API detected
08.11.2022 13:50:13.992 [0000375c] --- DirectX D3D12 hd3d12=15f70000
08.11.2022 13:50:13.992 [0000375c] --- DirectX D3D12 API detected hd3d12=15f70000
08.11.2022 13:50:13.993 [0000375c] --- DirectX D3D12 API detected 1
08.11.2022 13:50:13.993 [0000375c] --- hookOpenGL
08.11.2022 13:50:14.010 [0000375c] --- OpenGL API detected
08.11.2022 13:50:14.010 [0000375c] --- hookVulkan hModule
08.11.2022 13:50:14.011 [0000375c] --- VVulkan::VVulkan
08.11.2022 13:50:14.013 [0000375c] --- Vulkan API detected
08.11.2022 13:50:20.759 [00004888] --- PROCESS DETACH

Hi,
After 3.4.0 update, my profiles disappeared.

userprofiledata.json is still present and has content, but the profile selector doesn't allow to choose any of my previously created (and fine tuned) profile.

Is that normal due to the update ? Is it possible to restore them ?

thanks for your help (and BTW thanks for this great tool !)

Hi
MSFS pop-up panel manager works great except for an annoying issue.
I used it with FBW A32NX. Sometimes the auto panning works sometimes it is not working.
When the Pop out starts, I can see the auto panning trying to go to the wide view but quickly it reverts to the default view before the pop-out starts.
Sometime it works fine and go to the wide view and extract pop-out correctly.
I disabled the auto panning and now I extract them manually by going to the wide view (alt-0) and pressing Start Pop-out button.
Do you have a solution ?
I saw previously that there is a Hotkey to start the pop-out but I forget it. Can you tell me what it is?

Thanks for your good work.

Yves Levesque

error.log
I've tried numerous times with no luck,

When I use an external display and I use popout manager on the TSC in the g5000 longitude it registers every tap twice if I tap flight plan it taps the same area twice registering flight plan -> add waypoint. 

Popout manager settings: full screen, touch enabled

Windows 11, MSFS SU11

this happens on two different external display types: Generic 7 inch touch screen, wireless display via spacedesk

The GX3 pop out with Touch enabled does not function as expected using the Air Manager GX3 Instrument. The GX3 Instrument is a GitHub Sim Instrumentation download. Touch is enabled on the Pop Out Manager, and Air Manager is set to transparent, but neither the mouse or touch work with the instrument.

Thanks for the helpful program. I have a request: if I use the soft well, currently changing the screen, for example from the main view of the cockpit to overhead, I take the popup instruments with me. Obviously in the new screen I am forced to close them because they are bulky. Returning to the cockpit view, to reopen the pop up instruments I have to relaunch the program. Would there be a quicker and more direct way to get the instruments back in place correctly in the main view cockpit ? ( my basic situation… ) Thank you.

As the instruments and their placement depends on the model (aircraft) and not the livery I strongly suggest to refer to the aircraft type instead of the Livery. It makes it ways easier to just fly with new liveries as long as the model underneath is the same.

That would be great for people flying differet liveries.

See similar thread for FSUIPC .

User Request (Rosen213)

I have a small 800x480 5 inch lcd, been using your addon for a few days and really like the function. Would like to ask if it is possible to stretch the pop out to fully fit my screens 800x480 as the best I can get it to stretch is 830x520, anything more or less just automatically resets the panel size.

I ask because I am about to build a frame around the screen and would prefer not to cut some of the screen off, or maybe build around full screen.

Application has encountered a critical error and will be closed...

EXE.xml: Renamed to *.txt
EXE.txt

Error Log:
error.log

Thanks for looking into this.
Best regards

I installed latest version 3.3.3. The program starts, but does not seem to detect that msfs2020 is active.

Upon exit I get three errors like this and in the log file.

2022-06-21 18:31:34,618 [1] ERROR MSFSPopoutPanelManager.WpfApp.App - Could not load file or assembly 'Microsoft.FlightSimulator.SimConnect, Version=11.0.62651.3, Culture=neutral, PublicKeyToken=baf445ffb3a06b5c'. An attempt was made to load a program with an incorrect format.
System.BadImageFormatException: Could not load file or assembly 'Microsoft.FlightSimulator.SimConnect, Version=11.0.62651.3, Culture=neutral, PublicKeyToken=baf445ffb3a06b5c'. An attempt was made to load a program with an incorrect format.
File name: 'Microsoft.FlightSimulator.SimConnect, Version=11.0.62651.3, Culture=neutral, PublicKeyToken=baf445ffb3a06b5c'
   at MSFSPopoutPanelManager.FsConnector.SimConnector.Stop()
   at MSFSPopoutPanelManager.Provider.SimConnectManager.Stop() in C:\Src\MSFS Pop Out Panel Manager\master\Provider\SimConnectManager.cs:line 54
   at MSFSPopoutPanelManager.WpfApp.ViewModel.ApplicationViewModel.OnExit(Object commandParameter) in C:\Src\MSFS Pop Out Panel Manager\master\WpfApp\ViewModel\ApplicationViewModel.cs:line 171
   at MSFSPopoutPanelManager.WpfApp.ViewModel.DelegateCommand.Execute(Object parameter) in C:\Src\MSFS Pop Out Panel Manager\master\WpfApp\ViewModel\DelegateCommand.cs:line 17
   at MSFSPopoutPanelManager.WpfApp.ApplicationWindow.Window_Closing(Object sender, CancelEventArgs e) in C:\Src\MSFS Pop Out Panel Manager\master\WpfApp\ApplicationWindow.xaml.cs:line 100
   at System.Windows.Window.OnClosing(CancelEventArgs e)
   at MahApps.Metro.Controls.MetroWindow.<>n__0(CancelEventArgs e)
   at MahApps.Metro.Controls.MetroWindow.OnClosing(CancelEventArgs e)
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__140_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
2022-06-21 18:32:08,006 [1] ERROR MSFSPopoutPanelManager.WpfApp.App - Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
   at MSFSPopoutPanelManager.WpfApp.App.ShowExceptionDialog() in C:\Src\MSFS Pop Out Panel Manager\master\WpfApp\App.xaml.cs:line 81
   at MSFSPopoutPanelManager.WpfApp.App.HandleDispatcherException(Object sender, DispatcherUnhandledExceptionEventArgs e) in C:\Src\MSFS Pop Out Panel Manager\master\WpfApp\App.xaml.cs:line 63
   at System.Windows.Threading.Dispatcher.CatchException(Exception e)
   at System.Windows.Threading.Dispatcher.CatchExceptionStatic(Object source, Exception e)
   at System.Windows.Threading.ExceptionWrapper.CatchException(Object source, Exception e, Delegate catchHandler)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
2022-06-21 18:32:08,959 [1] ERROR MSFSPopoutPanelManager.WpfApp.App - Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
   at MSFSPopoutPanelManager.WpfApp.App.ShowExceptionDialog() in C:\Src\MSFS Pop Out Panel Manager\master\WpfApp\App.xaml.cs:line 81
   at MSFSPopoutPanelManager.WpfApp.App.HandleDispatcherException(Object sender, DispatcherUnhandledExceptionEventArgs e) in C:\Src\MSFS Pop Out Panel Manager\master\WpfApp\App.xaml.cs:line 63
   at System.Windows.Threading.Dispatcher.CatchException(Exception e)
   at System.Windows.Threading.Dispatcher.CatchExceptionStatic(Object source, Exception e)
   at System.Windows.Threading.ExceptionWrapper.CatchException(Object source, Exception e, Delegate catchHandler)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at System.Windows.Application.Run()
   at MSFSPopoutPanelManager.WpfApp.App.Main()

This is a fresh install of Windows 10 21H2 with all updates and MSFS2020.
I hope this can help to resolve this issue.

Automatically bind a livery to profile if the current active livery in MSFS is not bound to any existing profile. This will allow auto pop out panel to work automatically without the need to click the livery binding button when user first created a new profile. This will also help alleviate some of the confusions regarding auto pop out panel.

Number circles for panel do not appear at the location where you click your mouse if your monitor Windows Display Scaling is >100%. This is a display only issue and the coordinate where you click your mouse should still register correctly.

A fixed has been created and is pending to be included in the next release v3.3.7.

Requested by user - added by Stanley

Since panel locations (number circles) is 100% dependent on the location and size of MSFS main game window, when the game is run in window mode, the panel locations might change and become incorrect when main game window is resize or move to a different location on a monitor. To resolve this issue, adding an ability to save and recall MSFS main game window size and location will be very useful so panel location definitions will be accurate even when user moves the main MSFS game window to a different location.

Targeted for release v3.4.3

Hi, I am getting this error on start and not sure what to do. Any ideas?

2021-12-31 08:57:12,993 [1] ERROR MSFSPopoutPanelManager.Program - There is an error in XML document (3, 2).
System.InvalidOperationException: There is an error in XML document (3, 2).
---> System.Xml.XmlException: There are multiple root elements. Line 3, position 2.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.ReadEndElement()
at System.Xml.Serialization.XmlSerializationReader.ReadEndElement()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSimBaseDocument.Read3_SimBaseDocument(Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSimBaseDocument.Read4_SimBaseDocument()
--- End of inner exception stack trace ---
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Xml.Serialization.XmlSerializer.Deserialize(Stream stream)
at MSFSPopoutPanelManager.Shared.Autostart.CheckIsAutoStart() in C:\Src\msfs-popout-panel-manager\Shared\Autostart.cs:line 122
at MSFSPopoutPanelManager.UIController.StartUpController.Initialize() in C:\Src\msfs-popout-panel-manager\UIController\StartUpController.cs:line 37
at MSFSPopoutPanelManager.UI.StartupForm..ctor() in C:\Src\msfs-popout-panel-manager\UI\StartupForm.cs:line 40
at MSFSPopoutPanelManager.Program.Main() in C:\Src\msfs-popout-panel-manager\Program.cs:line 38
error.log

I posted a video over in the MSFS forums but wanted to make sure folks could see it here too

https://forums.flightsimulator.com/t/msfs-pop-out-panel-manager-with-touch-support-v3-4-1/460613/356?u=latka

RealSimGear GTN750 with Jay Dee's 750 replacement for the GNS530 in the v2.0 (testing) version of the BN-2 Islander. Popout manager works and gets the GTN750 to the RSG device, which through the RSG Device Interface is recognizing the knobs and buttons, but not touch events. Short video here: https://youtu.be/GC3Cr0owgR0

Hi !
Just a little suggestion here ...
When you have to fine-tweaking popped out instruments size and position, it's more precise to directly edit the .json file and made adjustments pixel by pixel.

To make the process easier, could it please be possible to auto-indent the userprofiledata.json file ?

What I'm doing currently is :

• opening userprofiledata.json file with notepad++
• copy/past json content in https://json-indent.com/
• paste / replace result into notepad++
• save file
• restart msfs popout panel manager

Reported by user and issue added by Stanley:

Investigate and find a solution so users do not have to run the app as administrator in Windows 10 or possibly Windows 11.

Currently, there is a default feature to recenter to cockpit view (using Ctrl-Space) when pop out is completed. A new preference setting is requested to allow disabling/enabling this default fall back camera and also allow a setting to fall back to a "Custom Camera View" (Ctrl-Alt-0 through 9)

Target release version 3.3.8 or 4.0.

Dear Stanley,

As i'm using in all my planes [Alt]+[0] for a outside view without VC (in front of VC) and [Alt]+[1] as standard VC PIC view, it would be great, if it would be an option to set the number of the custom camera to be saved for the auto panning camera.
Of course both views are assigned to joystick buttons as well.

To use the tool in my setup it would require that i have to edit the cameras.cfg for all planes, remove the custom camera 0 and reassign the joystick button for all planes.

Probably i'm not the only one and if the effort for selecting the custom camera it would be really helpful.
It not, please let me know, so that i can completely rework my setup to get your great tool available. :-)

Best regards,

     Joe

Hi Stan, I'm on the runway in the C172 Skyhawk G1000 on my left 4K screen (3840x2160). Started the popout app version 3.2 beta and having it also open on my left screen. Added a new profile "C172" and clicked "Add binding". Clicked "Start panel selection", moved cursor to the PFD of the C172, a hand cursor appears and clicked left mouse. NO number inside a circle!
What am I doing wrong? Hope you can help.
Regards Ben Steggink

I am using the C172 with G1000 and the 2nd panel is saying it cant be popped out even though i see it popped out next to the 1st one.
It was working before, but for some reason it no longer works.
I have version 3.4.5 and even tried to reinstall as well as redo the settings.
I have panning off and can verify the 1 & 2 are placed with no obstructions and as mentioned...i see the 2nd panel popped out next to the 1st.
Any chance it needs to pop out seperately as i see it doing it in the same window as the 1st?

Thank You for your help on this

Reported in Flightsim.to:

Been using your wonderful app since the first days now 😊 However after the recent update it stopped working. I had to roll back to Ver 3.3.4. When starting the pop out in 3.3.5 the panel selection and the mouse arrow are misaligned.

MSFSPopoutPanelManager.exe does not exist. Or does it?

Issue created from comment in MSFS forum by FrazapBzh:

I use msfs Pop Out Manager successfully daily on Flybywire A320 and other aircraft. But on the Fenix, whatever the instrument, it stops on the second instrument. I’m in the default cockpit view and I’m not touching the camera. Manual detachment allows you to detach all the instruments you want

.

G'day again,

Just copying from the MS Forum:

Once I press analyse the pop-up manager opens at least three of those four packages and then crashes with the error message I’m showing here (ooops, can’t upload images it seems). It’s a .Net error “Unhandled Exception Error has occurred in your application…”

Interestingly I've been able to get the Popup Manager to work on the Milviz Turbo Porter with 2 panels so is it possibly the CRJ causing the problem?

Cheers

Warwick

Hello Stanley,
when using 4k (4096x2160) on main display with two full HD displays, pop out does not work correctly. The windows are too big. Please see screenshots. Even if I touch a field like X POS, the corresponding panel doubles the size.

I use V 3.1 (software says 3.0)

Best regards
Olive




r

Reported by RMROC451,

I’ve noticed, when displaying MSFS on my 4k monitor (mixed with other 1920x1200 monitors), I’ve had to make sure the program is on the same monitor as my 4k monitor, or it won’t get the click positions right.

Unsure if that is a bug, or if that is just something wonky with my profile/setup.

Hi Stanley,

Thanks for this great utility, but I've had a problem lately. When start the popout (on 2 different aircraft now), the utility pops out the first 2 panels, then stops with an error message saying that "Unable to popout Panel number 2. Please check..."

It's just popped out Panel 2 and for some reason stops the popout process completly.

One of the aircraft has 4 panels (PMDG 737) and another just 2 (MIlviz Porter).

I've tried deleting the profile and re-learning but the same thing happens. The Popout Panel Manager isn't blocking the screens so I don't know what might be causing this.

Many thanks

Warwick

When trying to click and drag a map on touch enabled panel on tablet using SpaceDesk or Duet, touch is not responsive.

I go into the sim and number my panels but I am getting an error when I hit 'Start Pop Out' which states that MSFS/Simconnect has not been started.

Is simconnect an external piece of software?

Cheers.