Fenix A320 not working about msfs-popout-panel-manager HOT 4 CLOSED

Thanks for the screenshot. I've found a potential weird color detection issue in pop out manager's image recognition code when trying to use the screenshot that you provided to emulate the pop out operation, especially the EFB panel. The EFB panel background color may have sipped through to the menu bar at the top of the panel.

I've created a 'test' package, fenix-a320-fix-test.zip' in the version 3.3.2 release assets and hope this fixes your issue. Please download and extract the entire content of the zip into your pop out manager folder. All your plane profiles in 'userdata' folder should be safe but please do a backup of the entire pop out manager folder just in case.

If this update does work, I'll create an official patch that will roll out to everyone. If not, than something else about Fenix A320 panel is different than all the other planes and more investigation will be needed. You can roll back the update by restoring your backup folder copy or re-download version 3.3.2 manually from github repo and overwrite the test code if my fix does not work.

from msfs-popout-panel-manager.

Reply from FrazapBzh

I couldn’t get Fenix ​​Test Fix to work either, the same problem is recurring. You will find two screenshots below, one with the 2 Ecams and the other with the PFDs. Hope this may help you !

from msfs-popout-panel-manager.

Hi FrazapBzh,

The Fenix issue is baffling me and is only happening to this particular plane. Your screenshot told me a lot. I’ve debugged the code line by line and try to recreate your issue and I can only come up with only 2 scenarios that can produce your result.

First scenario:

As the pop out operation started, the second panel was never popped out and added to the first panel to produce a ‘joined’ panel where pop out manager can separate them. Please see screenshot below for the joined panel. This could be an issue about how the Fenix plane works or some timing problem with my code to pop out the panel initially.

Second scenario:

If the 2nd panel did pop out and a “joined” panel is created, then my code somehow is clicking the “X” icon (circle in red) instead of the “magnifying glass” icon (orange pointer) in the screenshot below. This could mean Fenix is producing a different pop out joined panel image for my app to analyze. Would you be able to re-run your pop out profile again with only 2 panels to help me debug the app by taking notes on observation below?

As the pop out started, you will see the first panel pop out, and the second panel will then pop out into a “joined” panel. This window will then shrink to a size of 800x600 pixels and move to the upper left corner of your screen.

After than, you will see some type of mouse movement and the mouse cursor will try to highlight the “magnifying glass” icon in blue and click it to separate the panels. This movement is very fast and you may not catch it the first time. You can rerun the pop out by clicking the app’s menu item “Restart” and “Start Pop Out” again. Please try to see where the mouse is trying to click.

If the mouse is clicking the “X” icon, then we have our culprit. If the mouse is trying to click somewhere else in the panel or not clicking in the “joined” panel at all, something else is going on.

Thanks for all your help and sorry for not able to fix this issue quickly. Unfortunately without access to the Fenix plane, I am asserting possible code scenarios and debugging in the blind.

scenarios and debugging in the blind.

from msfs-popout-panel-manager.

User resolved issue by running MSFS on main monitor. There is something about Fenix A320 internally which may have caused invalid application behaviors.

from msfs-popout-panel-manager.