John Dowson

Sorry, I don't know how you would get that information on Android. FSUIPC does not run/is not supported on Android. If Skydemon has access to this, maybe ask on their support forums. Unless anyone else has an idea....?

@Tony Goswell Could you try the attached dll please, v6.1.2a. Hopefully this will fix your issue. FSUIPC6.dll

I've added it in the attached dll if you would like to try it, v6.1.2a: FSUIPC6.dll You can also use this new control when auto-save is disabled. The new control is called Trigger Auto-save. Later: I have updated the dll with a minor change (the control number has changed), so please download again if already downloaded

No this is currently not possible. However, it is something that is relatively easy to add and is useful so, I will add an additional FSUIPC control that manually triggers an auto-save call. This will be for FSUIPC6 (and FSUIPC7) only (FSUIPC5 is now closed for further development). I will look into this in the coming weeks.

Are you using the same assignments in v4 both and v5? Maybe try logging buttons and keys, events and axes controls on both v4 and v5 and compare the logs on the two versions to see if there is any difference.

Please try running the installer again (do not manually uninstall first - let the installer do that). Hopefully it should work the second time. If not, you can download and install manually. For details on this issue, please see: Also, please check for similar posts before creating a new topic in future.

where did you get the WASMClient.exe from? Uoi should download the zip package, which includes the WASM. Please see the announcement page: for details: Note if you are using FSUIPC7 (registered), you don't need to use the WASMClient. Most of the functions are available directly in FSUIPC7.

Thanks for reporting this. Not sure what is causing this at the moment, but there was an update in those versions relating to the logging of ATC_MENO_OPEN/CLOSE events, and I am wondering if this is affecting the event.textmenu call. To test, could you try the attached dll please. If that has the same issue, I will look into this in more detail later this week. John FSUIPC6.dll

I've updated the installer and done some more tests, and it seems that the UserCfg.opt file could not be opened for reading on a clean installation in any circumstances. I don't understand why. However, if I try a second time to read the file, it works ok. Its very strange, but I have updated the installer to handle this. I will release this with 7.1.1 in a few days.

Can you check your FSUIPC7.log file. The console just displays the contents of this file. If that file is empty, then you have probably installed in a protected folder - show me your InstallFSUIPC7.log, or try installing in a different folder.

Yes, I think this is the issue i.e. LocalCache being a link/junction (and onto a different drive). But they should be the same when accessed through windows, or I would assume so, but this doesn't seem to be the case, as you say. That's interesting but I don't understand why it succeeded the third time. The difference when uninstalling first is that your current installation settings (i.e. previous installation folder and auto-start method) will not be preserved. However, this shouldn't affect determining the location of your Community folder. Unfortunately I don't think there is much I can do about this. I check if the file exists, and if it does I open it to read the location of the Community folder. I can update to show a message to the user when this error occurs, and I'll add some information on this issue and how to resolve to the Installation and Registration manual. Thanks, John

Have you installed the WASM? Did you have an aircraft loaded and 'ready-to-fly? If you have done both, please activate Debug level logging in both the WASM module and client and show them to me. I haven't updated the WASM package/zip in a while. I'll update to the latest versions (and add version information) in the next few days.

What, the problem that is now solved? Did you read the README.txt? What have you tried? Did you un-install and then re-install the VC++ redistributables?

I'm not sure if you problem is with "self-loading cargo" (whatever that is) or FSUIPC. If the former, you need their support. If you mean the FSUIPC7 is unable to start, then you should read the README.txt file included (the hint is in the name!), where you will find: And why did you raise the same question twice? I will delete the other topic you created.

If you have previously registered. there is no need to re-register. Just use the key file that was previously created. If you installed in the same folder, your previous registration details will be picked-up and populated, and you can just skip the registration. If you have installed in a different folder, then copy your FSUIPC7.key (as well as other FSUIPC files you may want to keep, such as you FSUIPC7.ini file) across to the new location. Any further problems with registration, please check one of the many support requests where I have detailed the reasons for this and what you need to do.

This indicates that there is no FSUIPC6.key file in your installation folder. As I have already said, you can create this manually, as indicated. I do not know why the installer isn't creating this file for you. Just create it manually as advised. You only need to do this once, so just do that.

The installer (well, windows) will automatically request admin rights when you run it. The problem looks to be with the permissions on your UserCfg.opt file.

That shouldn't be a problem - that is quite a standard set-up - same as mine in fact! You do have the same issue though - your Community folder location could not be determined as it found your UsrCfg.opt file but could not open it: Did you load an aircraft and get to the 'ready-to-fly' state? The WASM menu entries are not enabled when in the menu system.

Sorry, but those files are not in your installation folder, they are in the downloadable zip file. To be clear, you download a zip file. You should extract the contents to a folder somewhere. Do not try to run the installer from within the zip file. Once you have extracted, you will have three files: an installation and registration document (pdf) - (please read this document), a txt file detailing the latest changes, and the installer itself. When you run the installer, that installs FSUIPC 6 into a different folder, the one you selected (or accepted) during this installation process. Please take note of this - change if necessary (and usually recommended). This is also the folder where your FSUIPC files are located, including the key file previously mentioned.

This is because you installed it into a different location where the macro (.mcro) files were not present. Uninstalling via the windows app panel runs the generated FSUIPC uninstaller. The only difference running it manually (rather than letting the installer run it for you) is that the default installation location will be different. When you run the installer an it first uninstalls, when you come to install again the default installation location will be the previous installation location. If you uninstall manually first, when you run the installer the installation location will default to either C:\FSUIPC6 or your P3Dv5 add-on xml folder (depending on if you install for just P3Dv5 or P3Fv4). You should really take note of your installation folder (and change it if needed) when you install. Your issues were due to the fact that you installed in a different folder, and all the files you posted were from your original installation folder and so were out-of-date / not relevant to your issue. I suggest that you read the Installation and Registration manual which will tell you how the installer works and where files are installed. And remember that you can always use the 'Open Folder' button to determine where your installation folder is, and where the files that we request will be located. John

It is better installed outside of the P3D folder really. Do you have an FSUIPC6.key file in your FSUIPC6 installation folder? This file should be created when you click the Register button. If it doesn't exist, you can create it manually. The contents are: replacing the parts in bold with the relevant details.

Can you run FSUIPC7? Skip the registration and try running it unregistered. If it won't run, you need to update your VC++ redistributables - see the provided REASME.txt. If it does run, and you are using the details EXACTLY as written in your SimMarket purchase email/account, then please let me know your order number and I will check your details.

Ok. Next time it occurs, check you FSUIPC7.log file. If it looks like it closed down correctly, it will be MSFS that crashed. If this is repeatable, you should report to Asobo.

If it was FSUIPC that CTD, it would/should not cause MSFS to CTD. Anyway, your FSUIPC7.log file (from the crash session) should tell us. And a description of what you were doing, what was running, is always helpful, as Pete says. Usually (well, in all occasions so far encountered!) when this occurs, its MSFS that has crashed, which generates a fault in FSUIPC7 but FSUIPC7 still runs but closes and exits normally, due to the 'Exit with FS' option being selected. Check your windows event viewer again and see if there are any exceptions for MSFS logged.

Yes, I hadn't noticed that (thanks Milan): You must extract the contents of the zip before running the installer.