John Dowson

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

Was this working in 7.5.3? I have attached it if you could try with this (just rename your current FSUIPC.exe) and download this to your FSUIPC7 installation folder): FSUIPC7.exe John

These are new events in MSFS2024. I will look into adding these events (when MSFS2024 is detected), but for now you to define a preset to use these, e.g. Set_Balloon_Vent#$Param (>K:BALLOON_VENT_SET) Set_Burner_Pitch_Axis#$Param (K:AXIS_BURNER_PITCH_SET) To determine the name of the key (K) event, see https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/Key_Events/Key_Events.htm John

This is due to an array access mismatch. It works if you use: wnd.font(disp_AP, 3, 10) (i.e. 3 instead of WND_COURIER, which is mapped to 2). I have corrected this in the attached version. John FSUIPC7.exe

I have also moved this post to the FSUIPC7 / MSFS sub-forum. Please use this sub-forum for all questions and issues with FSUIPC7 / MSFS2020 / MSFS2024. John

You can try FSUIPC to see if is suitable for your needs. Download and install it from https://fsuipc.com/ and then install the trial license, available from a post at the top of this forum. FSUIPC provides facilities for calibrating flaps with specific detents - see page 44 of the FSUIPC7 User guide (the FSUIPC documentation will be installed in your Documents folder), section CALIBRATING FLAPS WITH SPECIFIC DÉTENTES. i don't have the iFly, but I believe it uses the standard Flaps Set control (K event) so that should work. If not, there are other methods you can try. Also make sure that the flaps lever is not assigned in MSFS. There is a learning curve with FSUIPC, as there is with all such control software. Read the documentation and try and assigning your flaps (to the Flaps control using Send direct to FSUIPC calibration) and then calibrate on page 6 of the calibration panel as indicated in the documentation. If you have any difficulties, post again and I will try to help. John

I will take a look in a few days. I had an eye operation today and need a few days for my vision to recover... John

Yes, you can download from fsuipc.com. A trial license is also available from a post at the top of this sub-forum. John

Yes, this will be included as default in the next release, hopefully mid-October or before. As the code that caused this must be for some reason (but well before my time and difficult to deduce why), I tthink I will also add an ini parameter that, when set, will revert to previous behavior. Please also let me know about your product. I am currently working on a new FSUIPC website and support forums (as these will be closing soon). I would like to add a page, with links, to all software that uses/relies/depends on FSUIPC, but that will come post-launch. Cheers, John

This is an FSUIPC issue. Successive axis control events that are masked (i.e. can be calibrated in FSUIPC) using the same parameter are currently ignored. I am not sure why this is (probably for performance issues with some devices), but I have removed this in the attached version. So please try the attached version, 7.5.5e. John FSUIPC7.exe

I have looked into this and can confirm this issue. It looks to be an issue with MSFS, but I will investigate further and report back, and will also raise an issue with Asobo. However, there is a workaround - you can use presets instead. I have tested this in a few aircraft and it works with presets - I have only tested in MSFS2020 but should also work in MSFS2024. Define two presets in your myevents.txt file (create this file if you do not have one): Then assign to these, giving the required parameter to the Throttle Set preset. Note that I have moved your post to the FSUIPC7 / MSFS subforum. John

Those files make no sense. Both are from MSFS2020, and the FSUIPC7.log was attached when FSUIPC7 was still running. Your ini file shows that you have no assignments at all, just some strange calibration entries: You should delete those and try again. Both log files also show strange device scanning activity. What are you trying to do with FSUIPC? As I asked before, if using both MSFS2020 and MSFS2024, are you using the same FSUIPC7 installation for both, or distinct installations? Why are you calibrating in FSUIPC but not assigning? This can work in many aircraft, but not recommended for any advanced aircraft.

This happens due to a Windows virus definition update causing a false positive, and its continually happening. It happened in an update a few days ago, but another definition update the same day fixed the issue. If they don't update to fix this in a day or two, I report it and it tends to get fixed in a subsequent update a day or 2 later. I have just checked and I also now get that here - and there have been 2 updates today. You can use the attached, which isn't compressed (its the compression of the exe that seems to trigger this): FSUIPC7.exe If this isn't fixed by Microsoft in a day or two I will report (again). John

These crashes were related to the logging of the parameter type for input events. According to the documentation, this can be either Float64 or String, but, as far as I know, only Float64 types have currently been implemented/are available. I request the parameter types for all input events received, but it looks like I am only getting a response for some of these, leaving the other unitialised. It is these uninitialised ones thar are causing a memory error/exception due to a buffer overrun. I have corrected this in the attached (by setting the default parameter type to 'Unknown'). As the parameter type is also not really useful for end users (it is always a number!), I have removed the logging for this, unless you have set logging for Extras or Input Events. Please find the updated version attached. Regards, John FSUIPC7.exe

Could you please post in the FSUIPC7 sub-forum for all issues and questions regarding FSUIPC7 for MSFS2020 and MSFS2024. I have moved your post. Are you using the same FSUIPC7 installation for both MSFS2020 and MSFS2024 or separate installations? If using the same installation, I can't see how the calibration values can be different in the same profile. Your calibrated values are also very strange - why do you have such a low upper value set (3312 / 3931)? The lower value is also quite high in the second screenshot. Can you show me / attach your FSUIPC7.ini file please, and your FSUIPC7.log files from MSFS2024 and MSFS2020 (if you run one then the other, you can then attach the FSUIPC7.log and the FSUIPC7_prev.log).