John Dowson

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

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

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

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

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

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

Its the xml plugin I am using in the installer - it doesn't add new lines for some reason. Not much I can do about it without removing this plugin and doing it another way, which I just don't have time for.- there is always something more important to be done! John

Thats strange, but a screenshot is no use - I believe you. I would need to see your log file, generated with logging for Input Events enabled. If you close an open the Assignment window, is it then ok? If so, its something strange happening with the pop-up menu population and the log file is probably of no use. No, I don't think this can be the cause. When you get this error, try listing the available Input Events - is it there?

But it looks to be there -- this line: No line feeds are added by FSUIPC, so its all on one line. Thats fine - its Windows-1252, as that is what is defined in the xml file header. John

@WebMaximus I have taken a look at this and it is nothing todo with the contents of the file, its the encoding. Your EXE.xml file is in UTF-8 BOM encoding for some reason. and not standard UTF-8. The BOM encoding (Byte Order Mark) adds 3 bytes to the start of the text stream, and is NOT recommended by the Unicode standard. This is confusing the xml parser which will not load such an encoded file. I suggest you change the file encoding to standard UTF-8. You can do this in Notepad++ if you have this - just load the file, change the encoding vie the Encoding menu, and then save it. Not sure why your file is UTF-8 BOM encoded though. I will ad this information to the Installation and Registration guide. John

Yes, most probably. But I can test and hopefully rectify this with the EXE.xml file you kindly shared. But I am busy at the moment - will take me some time before I can look into this. I will let you know - although I have a suspicion its the long file/path lengths that means the closing xml statement is not being read, hence invalidating the xml, but we'll see.... Cheers, John

Useful for me to see why it failed. Looks ok/valid on a first look, so not sure why its failing. May help me to improve the install process if its failing on a valid xml file. I will look into it further when time permits. Cheers, John

With MSFS2024? Note that there are a lot of issues with the latest SU update that can cause issues - maybe its due to these and the latest APL update is trying to correct for this... Strange...there must be something different. But I really can't comment much without seeing your FSUIPC7.log file. Try saving a copy when it works, and when it fails send me the latest one as well as the working one and I can check for differences. John

FSUIPC checks its a properly formatted xml document - if not, it doesn't update. If its not properly formatted, its usually due to another add-on corrupting it. If you can attached the EXE.xml, here, I cab take a look. Other add-ons probably just treat it as a text file - which is also why it gets corrupted! Great! No problem. You will automatically get a discount when you purchase/check-out if you have bought previous versions. Cheers, John

Look at or show me your InstallFSUIPC7.log file - that should indicate the issue. Usually, if its not updated, it is due to the current EXE.xml being invalid. No - it should always install what is selected. John

Oops - looks like I forgot to update it this month. Its done now - try downloading again. John

Looks like you can also assign the axes in FSUIPC - from the PFC documentation: But FSUIPC needs, of course, to be able to see these axes first....you won't be able to do anything until you get an 'Okay!' next to the Throttle quadrant operation in the PFC Control Connection Check box. Note that I do not have any PFC devices, com or hid, so I can only give advice based upon the documentation. I suggest you read this! John

Also, if is a com device and you are using a com-to-usb adapter cable (in which case you use the com driver), the cable should be used with a driver that maps the USB to a com port and you need to determine which and configure this correctly. If its a pure USB device, you need the hid driver (as I said), but I am not sure if your device is supported. Was this PFC device previously working with FSUIPC, and if so, how?

If it is a com device, then you also need to configure the com port being used and the controls check should say what is available, i.e. what does it say next to 'Throttle Quadrant operation'? And I think you configure your throttle in the Quadrant tab of the PFC driver window (available from the FSUIPC Add-ons menu), not in the FSUIPC axes assignment panel. Please see the PFC driver documentation.

Why are you exiting and then restarting? Just leave it running. I only said to run first (before starting MSFS) and exit so that you could set the logging so that this would be active when FSUIPC7 is auto-started by MSFS. As this is now set, you can just If its a USB/HID connection, why are you using the com driver? Have you tried with the USB/HID driver (PFChid64.dll)? When this was working, were you using a com port (with the com driver)?

As I previously said, this is a false positive and is always happening, but it is transient and usually fixed with a subsequent Security Intelligence update. I have checked with the latest version (1.437.710, automatically updated this morning) and that exe has no issues. So when this occurs, you need to wait for a subsequent virus definition update to fix this, or add an exception to allow the exe. Thee is no point in reporting this to me - I will just give you the same advice every time. If the exe gets blocked, I also notice this here. And if it isn't fixed within a day or two, I report it to Microsoft. John

The first log file was generated when FSUIPC was not connected to MSFS and therefore shows nothing useful, and was again attached when FSUIPC7 was still running. The second log file has logging for Input Events set but not for Extras, as I asked for, and was also attached when FSUIPC7 was still running. Do you mean the FSUIPC7 icon? This starts MSFS. It is MSFS that starts FSUIPC7. All the log files you attached show that you manually started FSUIPC7. What you are saying doesn't make sense and your log files show something else is going on. Please check things at your end, set the required logging (Extras) and disable other logging (especially for Input Events), and check the log file before attaching it. John

I have added the new MSFS2024 key events in the attached version (7.5.5g). These will only be visible when using MSFS2024 (and when FSUIPC7 is not connected to MSFS as the version cannot be determined). The following events have been added: AIRSHIP_VALVE_1_CLOSE AIRSHIP_VALVE_1_OPEN AIRSHIP_VALVE_1_SET AIRSHIP_VALVE_1_TOGGLE AIRSHIP_VALVE_2_CLOSE AIRSHIP_VALVE_2_OPEN AIRSHIP_VALVE_2_SET AIRSHIP_VALVE_2_TOGGLE AIRSHIP_VALVE_3_CLOSE AIRSHIP_VALVE_3_OPEN AIRSHIP_VALVE_3_SET AIRSHIP_VALVE_3_TOGGLE AIRSHIP_VALVE_4_CLOSE AIRSHIP_VALVE_4_OPEN AIRSHIP_VALVE_4_SET AIRSHIP_VALVE_4_TOGGLE AIRSHIP_VALVE_CLOSE AIRSHIP_VALVE_OPEN AIRSHIP_VALVE_SET AIRSHIP_VALVE_TOGGLE AXIS_BURNER_PITCH_SET AXIS_BURNER_ROLL_SET AXIS_THRUST_VECTOR_HORIZONTAL_SET AXIS_THRUST_VECTOR_VERTICAL_SET BALLOON_VENT_CLOSE BALLOON_VENT_OPEN BALLOON_VENT_SET BALLOON_VENT_TOGGLE BURNER_PITCH_DEC BURNER_PITCH_INC BURNER_ROLL_DEC BURNER_ROLL_INC BURNER_VALVE_CLOSE BURNER_VALVE_OPEN BURNER_VALVE_SET BURNER_VALVE_TOGGLE ELECTRICAL_LINE_BREAKER_SET ELECTRICAL_LINE_BREAKER_TOGGLE ELECTRICAL_LINE_CONNECTION_SET ELECTRICAL_LINE_CONNECTION_TOGGLE HYDRAULIC_SWITCH_TOGGLE HYDRAULIC_VALVE_CLOSE HYDRAULIC_VALVE_OPEN HYDRAULIC_VALVE_SET HYDRAULIC_VALVE_TOGGLE LIGHT_AMBIENT_COLOR_SET LIQUID_DROPPING_SYSTEM_DOOR_CLOSE LIQUID_DROPPING_SYSTEM_DOOR_COMMAND_GROUP_CLOSE LIQUID_DROPPING_SYSTEM_DOOR_COMMAND_GROUP_OPEN LIQUID_DROPPING_SYSTEM_DOOR_COMMAND_GROUP_SET LIQUID_DROPPING_SYSTEM_DOOR_COMMAND_GROUP_TOGGLE LIQUID_DROPPING_SYSTEM_DOOR_OPEN LIQUID_DROPPING_SYSTEM_DOOR_SET LIQUID_DROPPING_SYSTEM_DOOR_TOGGLE LIQUID_DROPPING_SYSTEM_SCOOP_CLOSE LIQUID_DROPPING_SYSTEM_SCOOP_OPEN LIQUID_DROPPING_SYSTEM_SCOOP_SET LIQUID_DROPPING_SYSTEM_SCOOP_TOGGLE PNEUMATICS_AREA_TEMPERATURE_DEC PNEUMATICS_AREA_TEMPERATURE_INC PNEUMATICS_AREA_TEMPERATURE_SET PNEUMATICS_FAN_SET PNEUMATICS_JUNCTION_LINE_OPENING_STATUS_SET PNEUMATICS_PACK_FLOW_AUTO_OFF PNEUMATICS_PACK_FLOW_AUTO_ON PNEUMATICS_PACK_FLOW_AUTO_SET PNEUMATICS_PACK_FLOW_MODE_HIGH PNEUMATICS_PACK_FLOW_MODE_LOW PNEUMATICS_PACK_FLOW_MODE_NORM PNEUMATICS_PACK_FLOW_MODE_SET PNEUMATICS_PACK_OFF PNEUMATICS_PACK_ON PNEUMATICS_PACK_SET PNEUMATICS_PACK_TOGGLE PNEUMATICS_PACKS_FLOW_DEC PNEUMATICS_PACKS_FLOW_INC PNEUMATICS_PACKS_FLOW_SET PNEUMATICS_TARGET_CABIN_ALTITUDE_DEC PNEUMATICS_TARGET_CABIN_ALTITUDE_INC PNEUMATICS_TARGET_CABIN_ALTITUDE_SET PNEUMATICS_VALVE_CLOSE PNEUMATICS_VALVE_MODE_AUTO PNEUMATICS_VALVE_MODE_CLOSED PNEUMATICS_VALVE_MODE_OPEN PNEUMATICS_VALVE_MODE_SET PNEUMATICS_VALVE_OPEN PNEUMATICS_VALVE_SET PNEUMATICS_VALVE_TOGGLE SKYDIVE_DOORLIGHTS_DEC SKYDIVE_DOORLIGHTS_GETREADY SKYDIVE_DOORLIGHTS_INC SKYDIVE_DOORLIGHTS_JUMP SKYDIVE_DOORLIGHTS_OFF SPRAY_OFF SPRAY_ON SPRAY_TOGGLE SPRAY_SET Let me know if you have any issues. John FSUIPC7.exe

The log file you attached shows that MSFS was not running. or that FSUIPC was not connected to MSFS. Can you please try once FSUIPC7 is connected to MSFS and also when you have an aircraft loaded and ready to fly. I think at least one of the PFC drivers needs this, but can't remember which off-hand. Also, please always exit FSUIPC before attaching files. Your log shows that it was still running. Also, can you add logging froe Extras for the nest log file please - please run FSUIPC7 and set this, then exit, then start MSFS/FSUIPC7 as usual. John

Can you please use the FSUIPC7 sub-forum for all questions and issues with FSUIPC7 / MSFS2020 / MSFS2024, not the main support forum. I have moved your post. Such issues are usually due to FSUIPC7 not being able to connect to MSFS. Did you check if FSUIPC7 was connected? If not, please do that. If FSUIPC7 cannot connect, check your FSUIPC7.log file, and see the following FAQ entry on how to tune the FSUIPC7 start-up/connection parameters: You can try 7.5.3, but I do not think this will make a difference. Can't you download it from the same post? I have attached it, but if it works for 7.5.3 and not for 7.5.4, which would surprise me, I will need to investigate. John FSUIPC7.exe