No issue here either with AM running first. I would think almost everyone has their panels on monitors that are not sim monitors so I doubt that is a concern also.
POPM opens and separates my popouts on a different monitor than my main sim monitor. Itās not an issue for me because itās not on my AM monitors. But if itās opening it for them on their AM monitors and AM is āalways on topā, that could indeed be a problem.
Not sure how that works and how POPM selects which monitor it opens popouts on and does the separation before playing.
Oh ok. I was under the impression that it first pops them out to the sim monitor always simply because mine has always behaved like that. In my case the main windows monitor is the main sim monitor. Perhaps POPM uses the main windows monitor?
POPM pops out instrumentation panels to your Windows primary monitor, to the upper left corner of the monitor at coordinate x:0/y:0 and then tries to click on the panel to separate them.
If youāve Air Manager on your primary monitor and have it set to always on top, and MSFS is run on secondary monitor(s), then I believe there may be a conflict that when instrumentation panel is initially popped out, POPM wonāt be able to click on it since Air Manager is always on top. Iāll do some testing in the next couple days to see if this is an issue.
If it is, Iāll try to fix the issue and create a beta test build for anyone who may be experiencing this issue to test. Since this is not something common to POPM users, thatās probably why I didnāt consider this particular use case. Also, Iām thinking if multiple applications (Air Manager and MSFS/POPM) try to set their window to be always on top, the fix canāt be guarantee either. Iāll do as much testing as I can to see if I can resolve this potential conflict.
Stanley
As I suspected. An easy fix really for a user, just change your PC to make the main windows monitor not an AM one.
1 Like
Hello @RoastGnu !
As Iām building a hardware home cockpit I started to play with the Ā« home cockpit mode Ā» in msfs camera settings. As de gauges are out of sight on my screen and this mode fixed the camera and prevent any moves POPM canāt do his job anymore.
Is there any way your software can go around this? Or automatically set the settings off while itās piping out panels and set it on again once done?
Thanks for your help!
Hi Bradesna2,
Iāve tested with the new multi-window feature in SU10 and it seems to work with my test case. Using PMDG 737, Iāve the following set:
- 3 monitors (Left - 1080p, Center - 1440p, Right - 1080p)
- The center monitor is the center cockpit view and also Windows Primary monitor (this maybe important)
- As I created the profile, I used my mouse to pan down the center display in order to select 737 CDU (which is hidden from view from default camera angle) in addition to PFD and other panels.
- When I clicked āStart pop outā, the auto panning feature in my app panned down to the set camera angle to pop out the hidden CDU panel correctly.
Would you please see if you can replicate my use case for your aircraft? SU10 multi-window feature should not disable the movement of custom camera view.
Stanley
Hi, I think we misunderstood. I have no problem with multi view; the problem is with Ā« home cockpit mode Ā» you will find it in the camera menu, wich disable camera move (itās made for this) and so POPM canāt pan anymore to place the panel in the field view.
My AM panels are on monitors that MSFS doesnāt use.
POPM puts the popped out panels onto a monitor that is devoted to AM.
Perhaps thereās a way to change this.
Ah, that makes sense. MSFS doesnāt run on my primary display: AM does. The primary display on thie PC is too big and āin your faceā for anything but playing aeroplanes.
Ahhhhā¦ā¦ sorry for the misunderstanding. I will look into the home cockpit setting and see if there is any I can do from my program code perspective.
Hi Bradsena2,
Just tried the home cockpit mode setting on SU10. On both PMDG 737 and Kodiak, it doesnāt seem to do anything other than centering the cockpit view but also disable mouse to perform free look (which is required by POPM). This feature is supposed to remove the virtual cockpit rendering and it doesnāt. From reading other posts in the forum regarding this mode, it looks like Asobo did not implement this particular feature yet.
Is there something you try to do in home cockpit mode that a custom camera angle cannot achieve?
We have established that itās not about what monitor the sim is on but what one is your main windows monitor. Itās easy to change the main windows monitor to be one that doesnāt have an AM panel on it. Do this and you will be good.
it works on one monitor but not on surround?, very oddā¦
Couldnāt pop out in Multi monitor because of the zoom factor. I solved it by doing the pop out before activating Experimental. It seemed to work, the panels finished up on my AM screen where they were supposed to be.
Iāve noticed that the zoom operation (using the mouse wheel to zoom in or out) before making panel selections, which is also used by POPM to save the custom camera angle for auto panning, is not as accurate in SU10 compare to SU9 and earlier. This may cause the number circles to be off compare to where you first defined them in the profile. I hope Asobo will fix this issue in SU11. Unfortunately, Iāve no control of zoom operation of the game in POPM.
With mine its now workingā¦the ONLY change i made was to move the main popout manager window away from the selection zone (e.g. middle of left monitor) and this fixed my issueā¦no idea why??
Popout manager %userprofile%\Documents\MSFS Pop Out Manager folder/files not created
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ā ?
Windows 10, 16 Gb RAM, I9700, RTX 3060ti
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.
I do not have Sizer or Windows PowerToys installed.
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
Hi TarmacMoon77549,
The profile setting folder should be inside your Windows login account folder. So ā%userprofile%\Documents\MSFS Pop Out Managerā should be āC:\users\XXXX\Documents\MSFS Pop Out Managerā where XXXX is your user login account id. If the folder cannot be created, then it looks like something in your system is preventing the creation of this folder such as antivirus software.
Would you please try creating the above folder manually? Once it has been created, start Pop out manager. You should immediately see a file āappsettingdata.jsonā gets created. If it does, then everything should be OK. If not, then there is something restricting read/write access to your Documents folder.
Hi
Thank you for your reply.
As suggested, I tried to create manually the folder, but did not worked.
I am not presently at my computer, but will be on Friday. Then, I will look into my antivirus software to see if it is restricting access.
I will come back to you on my success or failure.
Regards.