John Dowson

There is no problem the registration validation in FSUIPC4, its only an issue in the FSUIPC4 installer. Therefore we have temporarily removed validation of the key from the installer, the installer will still generate a key file and this is validated by FSUIPC4 when ran.

The 'Main menu' is the initial (main) menu and the one that you go back to when you end a flight, containing access to the various features with the WELCOME page, the World map, Flight Training, etc. When connected to MSFS, you are either in the 'main menus' or are in a flight (which can be paused of course).

What happens when you try to run the FSUIPC7.exe manually? You probably get the following error (or something similar): The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem. This is explained in the README.txt file. You need to uninstall your VC++ 2015, 2017 and 2019 redistributable packages (any that are installed, using with windows app management panel), and then re-install the combined redistributables (both x86 and x64 versions) from https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads John

Please read the Installation and Registration guide, as well as the README.txt, that comes in the zip file you downloaded. Other than that, I do not understand what your issue is. Please read the provided documentation. If you think there is an issue, please atttachh appropriate information/files (e.g. installation log, or FSUIPC7.log, or both). John

There are various offsets that you can use/monitor to determine the state of MSFS (connected or not, pause state, in main menu) and the aircraft state. Please check the documentation. If you need an aircraft loaded and ready before your program sends its lat, lon, etc (and to whatever that applies!), then you probably want to monitor the ready-to-fly indicator in offset 0x3364. Also see 0x03365. John

Yes, just remove the lines from the ini (take a backup first, just in case!). You won't see them in the interface if the device is not connected/doesnt exist. Thanks. We appreciate happy customers! Its mainly Pete though (previously, now me) - I'm a relative newbie having only been involved for the past 2-3 years. I've still till a lot to learn! Regards, John

Yes, they are in now and I'll leave them.

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