All Activity

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.

By the way, what do you mean by 'cannot see the flight'? Does it connect to FSUIPC7?

Please use the specific sub-forum for FSUIPC7 for all issues / questions on this product. I have moved your post. There should be no issue running ,multiple FSUIPC7 clients at the same time - at least not with FSUIPC7. What happens when APL2 is running and can see the flight, and then you start your Wingwing MCDU add-on, if possible (whatever that is)? If its a WASM=based add-on, you won't be able to do this though. Can you show me your log files please, with logging for IPC Reads activated. Show me / attach two log files (FSUIPC7.log), one from when APL2 is running and working, and one from when both are running and it isn't working. Also please exit FSUIPC7 before attaching log files. Your attachment limit will be very low - you may need to compress/zip these files. John

*** 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

@paddler Did you make any progress with this issue?

Wilco, thx John

Please read the documentation, section Invalid Key Problems in the Installation and Registration guide You could also search for one of the several hundred other user reports on this issue... If you re-installed windows, your problem will almost certainly be that you need to install the required VC++ redistributables. See the documentation. John

Hi all, i setup my windows new, i did not de-install FSUIPC. The re-install today was telling me my credentials (key) was not valid. It is the exact same as the shop shows. do you need to re-set the key perhaps? cheers from Germany!

Its not that difficult - and I gave you detailed instructions. What don't you understand? No I don't - I don't have the time for this. John

Thank you. Although it’s outside my competance. Do you freelance your services? Thanks Nick

Looks like the latest security intelligence update (1.437.99.0) fixed this issue. John

Good to know, thanks. As this issue was only affecting assignments to virtual buttons, there is probably a better way I could have done this (as I do for standard buttons). I will look into this at some point. If I do change this, I will provide you with another exe to test, but it won't be for a while. John

I managed. Somehow I was fast enough when Defender popped up as I copied the exe to my sim PC. There was a possibility to allow the exe on my system before it was deleted. Anyway, it now works, Input Events bound to virtual buttons work after restarting the sim. Karl

I also submitted to Microsoft to get this rectified:

You should have an 'Actions' button there - don't know why it isn't showing...

Sorry, I don't know how to do it.

You have to go into protection history and restore from there.

It doesn't let me, it deletes it anyway although I tell Defender to allow it on my system.

The uncompressed exe is also now getting flagged/blocked. I have reported to Microsoft. John

Allow it - its a false positive, as always....

Thank you, I'll test it as soon as Defender allows. Karl

This now works. Thank you. Karl

Thats a better log and does show an issue.. When you profile is initially loaded, the input event is not known. The inputs events are received after the profile is loaded, but the loaded profile isn't updated - it is only updated here: and so after this, the assignment to the input event works. I am not sure what caused the profile to be reloaded here, but they are reloaded when you open/close the assignment panels, so that may be it. This also explains the double entries in the menu. When you see this, the input events are loaded (hence visible), but the input event is not linked to the button assignment, so another entry is added. Previously I was reloading assignments when input events are received from MSFS, but this was disabled as it could occasionally write an empty assignments section (basically removing all assignments), so ?i removed this. I have reenabled this in the attached version, and tried to correct the writing of an empty section. So please try this version, but also please take a back-up of your ini file(s), just in case (although you should have a back-up in your backup-ini folder, as inis are now backed-up on re-installation). Like standard events, some aircraft continually emit some inout events. You can ignore these by adding the following to your [Profile.C172_Carenado] section in your FSUIPC7.ini: DontLogTheseIE=VARIABLE_AMBIENT_LIGHT_UPDATE Let me know how it goes with this version, John FSUIPC7.exe

Right, I enabled logs later on. Attached please find a new log where logs were enabled at the beginning. I waited for a long time but the error didn't go away. I then reassigned using the 2nd of the two and it worked. Not sure how long I should wait. (I don't know where the trigger of the ambient light input event comes from that fills up the log). Karl FSUIPC7.zip

You are getting these '' Cannot execute empty Input Event' messages as you are trying to use them before they have been found/received by FSUIPC7. I can't tell from your log when the input events are initially found/received as these messages are not in your log for some reason, e.g. from my log: Not sure why you haven't got his logged - did you set Input Event logging later, after starting FSUIPC7? You will get this message if you try to use an input event before it is known/has been received by FSUIPC7. I just think you need to give it more time before you try and use Input Events - and you can only ever use these (in the assignments window) when an aircraft is loaded and ready )i.e. not when in the menu system). Not sure why there are two entries. I will look into this at some point, but this is low priority I currently have more pressing things to do. I will look into this when time permits. I would like to understand why you aren't getting the other log messages about input events though. If you are getting a 'received' message, this indicates that the input event was found, but this isn't being logged for some reason. John