Rileydemooij

Hi John, I have performed the tests: the first test with only APL2, and the second test with both software programs. I have also put the logs (143 KB) in a zip file and enabled FSUIPC IPC Reads. By “cannot see the flight,” I mean that A Pilot’s Life v2 starts and connects to MSFS/FSUIPC7, but it does not detect that a flight has started. It just stays on “flight not started,” even when I am in the cockpit in a cold and dark state and the flight is in progress. APL2 does connect to MSFS, but it does not link to my active flight. I am also at the correct airport and gate as required by the flight briefing. When I run only APL2, it works fine and the flight is detected correctly. The problem appears only when both APL2 and the Winwing MCDU are running at the same time. The log file is already zipped (143 KB). I noticed it should normally be around 20 KB, but in my case it is larger. If needed, I can provide a download link or share it via Google Drive. Please let me know if there is another preferred way to send it.

*** Moved to FSUIPC7 support sub-forum *** Hello, I’ve run into a problem in MSFS 2020 where A Pilot’s Life v2 does not detect my flights correctly when I use it together with my Winwing MCDU addon. Both APL2 and the MCDU seem to use FSUIPC and when they are running at the same time, APL2 cannot see the flight. If I only run APL2 without the MCDU, it works fine. If I only run the MCDU, it also works fine. The conflict appears only when both are active together through FSUIPC. Is there a way to configure FSUIPC so that both applications can run side by side without interfering with each other? Maybe something in the FSUIPC7.ini that I should adjust? Thank you for your help! Best regards, Riley