John Dowson

If you are using the free version to support third party applications, there is no need to purchase a license. That error is from FSEconomy, not FSUIPC. It looks like FSUIPC isn't being started with MSFS. Can you show me your InstallFSUIPC7.log file please. Also, you can try starting FSUIPC7 manually after starting MSFS - just double-click the FSUIPC7.exe file. John

Also, this is the latest version - can you see if you can run it: FSUIPC7.exe

Me neither at the moment, but could you show me the Event Viewer crash report (not the crash log file name), under Windows Logs -> Application. Could you try uninstalling your VC++ redistributables 2015, 2017 and 2019, and then install the combined packages from https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads (both x64 and x86 versions) and try again.

Most probably due to this issue: However, as you haven't provided any relevant information its hard to tell. Note that all MSFS CTDs should be reported to Asobo via zendesk with the crash log included. John Also reported here:

Most probably due to this issue: However, as you haven't provided any relevant information its hard to tell. Note that all MSFS CTDs should be reported to Asobo via zendesk with the crash log included. John Also reported here: John

Yes, but only if if you have previously registered ok as that would have generated your FSUIPC4.key file.

But as Pete said, did you try skipping registration and just using your existing FSUIPC4.key file? Presumably you have used FSUIPC4 since its purchase on the 22/05/2020, so you know your registration is valid....

This was a limit imposed by early design decisions, and when DirectInput only supported up to 32 buttons. DirectInput now supports up to 128 buttons. We are working on an update to enable 128 buttons for assignment without Lua. John

No, the AP events aren't available. I've removed that version from my previous post as its not valid. John

@Dominik Sorry, I was sending the wrong event on write - I was sending the ALTITUDE SLOT INDEX control, rather than the AP ALTITUDE_SLOT_INDEX one (and similar for the others). I've changed to send the AP ones in the attached version, v7.0.5d, if you would like to try: But I'm not sure on the difference between these controls, so please try the updated version and let me know. John Later... No, sorry - that won't work. The AP versions of those controls are not recognized by SimConnect - or weren't ptrviously. I'll re-activate them to see if available...

Yes, that work-around is mentioned earlier in this thread. Using this option reduces the amount of data going through simconnect and so seems to delay the CTD, often enough for many flights (but not all!) to be completed. Some users have had more success with this than others, but the main fix must come from Asobo. John

Ah, ok. Thanks for reporting back. John

All the FSUIPC documentation is installed (optionally for FSUIPC6/7) when you install FSUIPC. If usingFSUIPC6 or 7, then they will be under your windows documents folder in an FSUIPC6/7 subfolder (v7.0.4 also creates a link to this location under your installation directory). For FSUIPC4/5, the documents will be under an FSUIPC Documents sub-folder of your FSUIPC installation folder. The FSUIPC documentation is also available for download as a separate package here (although these won't be up-to-date): John

I cannot help as you do not supply any information, such as your FSUIPC7.log file. However, if MSFS is crashing then you are probsbly experiencing this issue: Asobo are aware of this and we are waiting a fix. Please check for similar problems before creating a new post/topic. John

Please see this topic: Asobo are aware of the issue and we are awaiting a fix. This topic is now locked. John

@imagecrafting There is an updated FSUIPC4.dll attached to the last comment in this post, if you could try that to see if it works with your joysticks disconnected: John

I see Pete has responded. The button presses in your log are assigned to toggle a lua flag for that script, which is why they aren't working. Correct that script and try again. John

There are several posts topics on this now, and still nothing has changed. Please check for existing topics for the same issue before posting a new topic. For example, see or John

In the latest version of FSUIPC7, v7.0.4, FSUIPC7 is started from the MSFS EXE.xml file. If you don't want it to start with MSFS, edit that file and remove the section that starts FSUIPC7. If you don't use it to start any other programs, you can remove the file completely. For MS Store installs, it should be located under your AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\ folder. For Steam installs, its under AppData\Roaming\Microsoft Flight Simulator. John

Yes, sorry - forgot to attach. Here it is: FSUIPC4.ini John

Note that there is now a new version, v7.0.5c and the offsets for these new items has changed slightly. Please see the following for details and to download the new version: John

Ok, then thats the correct driver for your device, but you have probably placed it into the wrong installation, unless 'FSUIPC for MSFS' is your FSUIPC installation folder. If you are not sure where you installed FSUIPC7, you can use the File -> Open Installation Folder option from FSUIPC, which should show you the folder where the PFCcom64.dll should go. Yes, please download from www.fsuipc.com. Also check that you are using the latest version of FSUIPC7, which is v7.0.4. I see Pete has also replied... Not quite true. It is loaded during FSUIPC initialisation even without MSFS running, and you should see this in your log file after the LogOptions are logged: 703 Loaded PFCcom64.DLL okay! However, the PFC menu entry and initial dialog box will not be displayed until connected to MSFS AND you have an aircraft loaded. John

Can you check that again please - I get 1 or 2 in that offset directly... In the attached version, v7.0.5c, you have (note the offset changes!): 0x0290 4Bytes AUTOPILOT ALTITUDE SLOT INDEX Read/Write 0x0294 4Bytes AUTOPILOT HEADING SLOT INDEX Read/Write 0x0298 4Bytes AUTOPILOT SPEED SLOT INDEX Read/Write 0x029D 1 Byte APU SWITCH Read Only FSUIPC7.exe Do you know if there a control/event I can use for this? If so, I can make 0x029D also writable. I've previously read that its tricky to do this, but some have had success with lua. e.g. from here: John

@mermoz33 I have noticed the following in this post: Maybe try that, or ask the OP how he did this via lua. John

But the CTD is for MSFS, not FSUIPC7. This is why you need to report to Asobo. not me. I cannot do anything with MSFS crash reports. FSUIPC7 is an exe, and should not cause MSFS to crash - if it does, its a problem with MSFS. Of course, if it was a CTD of FSUIPC7, then I would investigate. So, Asobo are aware and are looking into it. There isn't anything i can do. John