John Dowson

Thats really not necessary. Thanks for the offer though. John

No. Just uninstall the 2017 and then install the 2015, 2017 and 2019 combined.

This looks a better bet: John

Ok, so there is a problem with you VC++ redistributables. Uninstall the VC++ redistributables (using the windows apps panel) for 2015, 2017 & 2019, and then install the combined packages (both x64 and x86) from https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads Then try again. John

Any crash with MSFS is an issue for Asobo, now that FSUIPC7 runs as a separate executable. If it is the same issue, Asobo are aware and are investigating. However, I think its always worth raising a zendesk bug report when MSFS crashes, including the relevant information from the Windows Event Log. I haven't tried loading a bush trip recently. I'll check this here over the weekend as well. John

Sorry, what says that? What has this got to do with installation? I am having difficulty understanding what you are doing or seeing. Could you please explain in more detail. Did you try what I asked, i.e. selecting a different installation location?

What do you mean? As you previously installed in Desktop, that will be the default location. You can change this - did you try? i.e. click the Browse... button and select a different location?

You cannot just use that script, as thats for rudder/aileron. I recommended you reading that to give you an idea of what sort of thing you need to do in your lua script for this. Did you try writing your own lua, maybe based upon that one? I'm sorry but I'm very busy and don't have time at the moment to write a lua for you, but can help if you come across any issues if you try yourself. John P.S. Just checked that script and its probably not a good idea to base yours on that, you sshould start from scratch but it would be quite difficult if not familiar with lua. Did you try Roman's suggestion, with a negative value for MaxSteerSpeed for example?

Actually, there is something strange in your install log: Did you select to install FSUIPC7 on your desktop? Try installing in a different location.

Install log looks fine. What happens when you try to start FSUIPC7 manually?

It will be in your FSUIPC7 installation folder, along with the FSUIPC7.exe.

There is an issue with registration in the 4.976 installer and this has now been withdrawn. Please download and install Install FSUIPC4.975b . Also, see this note in the Download Links -> Updated Modules section: John

?

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