John Dowson

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.

Those logs are from 3rd Feb and 8th March, and the ini's are probably just as old. So it looks likeyou have installed in another folder to your original installation folder. You need to determine where you have actually installed v6.1.1. The best way to do this is to use the Open Folder button in the logging tab. But, probably the best thing to do is to just re-install again. This will uninstall your current version, and allow you to select the installation folder. Make sure that you select your old installation folder - the one where your .mcro files are located. A re-install into the correct folder should fix his issues, but you can certainly continue with this if the OP has more issues, thanks.

Sorry, but could you also attach your FSUIPC6.log and InstallFSUIPC6.log files please.

Did you read the Installation and Registration guide? Did you check the forums, as this question has been asked hundreds of times already? Did you click the Register button during registration? 95% id uses are due to this not being done. If you did do this, what did the pop-up say? Have you installed in a non-windows protected folder?

Lvars are, by default, 8 bytes (64 bits). If the strings aren't null terminated, ipc.writeSTR will write 8 bytes. There are two things you could try - specifying the length of the string in the ipc.writeSTR function call, e.g. ipc.writeSTR (0x6950, value, 4) You could also try logging the value, to see what is actually being received and written to the offsets, e.g. function md_ipc_fuelleft (varname, value) ipc.log("md_ipc_fuelleft: received value '" .. value .. "' for lvar " .. varname) ipc.writeSTR (0x6950, value, 4) end Later: and this: should probably be: event.Lvar ("md_ipc_fueltotal", lvps, "md_ipc_fueltotal") - (string) | offset = 0x695C | type = string | size = STR, 5 | substring 0 - 5 BUT, you are also using an offset area that is not documented as free for general use - it is Reserved. Try with offsets free for general use, e.g. try from 66C0 or A000.

In your FSUIPC7 installation folder, along with your FSUIPC7.log and FSUIPC7.ini files, which I would also like to see. Have you 'enabled' wide server (using the WideFS -> Enable menu option) from FSUIPC7? You only need to do this only once.

Please also show me your WideServer.log & FSUIPC7.ini files, and I will take a look (tomorrow now). Also, try removing the Protocol from your WideClient.ini and and use ProtocolPreferred ini parameter in your FSUIPC7.ini ([WideServer] section). And try using ServerName rather than ServerIPAddr, if not done already. However, these issues are usually always caused by firewall or workgroup settings, so please double-check.

Have you checked your windows workgroups and firewall settings, as indicated in the WideFS user Guide?

Ah, the trim wheel uses buttons! Sorry, I had assumed that was an axis... Have you tried adjusting the PollInterval (to read the button states faster) or the ButtonRepeat ini parameters (to control the repeat rate)? You can usually achieve acceptable results adjusting these together with the timings in your lua. See the Advanced User guide for details on these ini parameters. Yes, its the same SDK for the various FSUIPC versions. Note that this is also installed (if selected) in an SDK folder under your FSUIPC7 installation folder. But I would persist with lua for the time being and try those ini parameters if not done already, before looking at the SDK.

Do you have a steam or MS Store version? The installer thinks you have a steam version, but cannot open this file: The strange thing is that that file is detected as being present, but cannot be opened for reading. Maybe check the permissions on that file. Do you run MSFS using admin privileges? Alternatively, you can use the following - just unzip in your MSFS Community folder and it should be picked-ip the next time you run FSUIPC7: fsuipc-lvar-module.zip

One of the rotaries is the mode selector which has 5 different buttons/positions, so I guess you just need to control the 2-button inc/dec rotary, no? You can usually achieve acceptable performance using both methods, especially if you assign to the offset increment/decrement controls and tune the inc/dec amount. However, being a two button rotary, its performance will be limited. I don't know that library so can't really comment (although it seems more of a multi-media library than for device handling), but not sure how you would interface that to FSUIPC. The FSUIPC lua library is not available to external lua programs, i.e those not ran by FSUIPC. You would have to use the FSUIPC SDK to feed the input back to FSUIPC. You use the FSUIPC SDK (available for various languages) in an external program to write/read to/from FSUIPC offsets. As indicated in that post you referenced (and was what the OP did), you could using another button (or key) as a type of latching switch, so when pressed/active the rotary would be performing fast in/dec, and when not the in/dec would be slow. You could even have different increments for different keys/buttons. You acieve this via compound button assignments (see the Advanced User guide). John

Ok, thanks for reporting back.

Yes, that is correct. I have explained this in a few posts, but yes, you are right - I should add this to the documentation. See or

I don't know what this means. but it needs to be saved as a .mcro file, as I have said...if its not saving with the correct extension, change by using 'save as...' or simply rename the file (right clickin windows explorer and select Rename). Then you cannot use direct assignments. You will have to use either the lua com library or MobiFlight.