John Dowson

I need to do it the other way around as I don't currently have access to the key generation facilities for FSUIPC4, so PM me your FSUIPC4 details and I'll generate a new WideFS7 key for you using those. John

What error? If you are talking about FSFK, then you need to contact their support. If you have an issue with FSUIPC, please explain what the issue is. John

For FSUIPC4, the name must be the same. This is not required in FSUIPC5 or FSUIPC6. If you could PM me (do not post publicly!) your WideFS7 registration details, I'll generate a new FSUIPC4 key for you using the same email/address. John

We need to see your FSUIPC4.log file, not your .ini or DLL.xml as these are not relevant. Also, please try adding NoWeatherAtAll=Yes to the [General] section of your FSUIPC4.ini file to see if it makes a difference, as it still may be a weather issue. John

First, you posted in the FAQ sub-forum, where it states 'NOT for support requests'! I have moved your post for you, but please post in the correct forum, which is almost always the main Support Forum, unless it relates to the dll client for .net. Your problem has also been reported many times and there are solutions in the FAQ sub-forum where you posted. Please see the following FAQ posts: The latest version of FSUIPC4 is also now 4.975 - please update.

For FSUIPC5, you can just delete (or rename) the FSUIPC5.DLL file, which will prevent it from being loaded. With that, P3D will try to start FSUIPC but won't as it can't find the dll. This is not an issue. However, if you want to remove it completely (or just stop the 2nd version from running), then check your DLL.XML file from your <user>\AppData\Roaming\Lockheed Martin\Prepar3D v4 folder. If you have 2 copies running, there are probably 2 entries in that file. You can delete one to prevent your message (if you still want to use FSUIPC), or both entries if not needed. You can also completely remove your Modules folder if you want to get rid of it completely. John

Check the logs for any antivirus software that you may have installed and try disabling that. You can also maybe try with a different extractor (but I can't see how that would make a difference!). Other than that, you need to determine what the window that displays for a short time is saying. Maybe by recording it and playing it back slowly would help - think you can do this via the screen recorder in the windows game bar. John

I can only suggest that you download again and re-try. When you run the installer, you should initially get a windows screen asking you to give permission for the installer to make changes to your system. Do you not see that?

Please see You will need to purchase a new key for FSUIPC6 from SimMarket. You will get the discount automatically applied on checkout. John

The free and registered versions are the same - the additional functionality provided by a licensed version is activated when you register during the installation process. This contradicts your previous statement when you said that you had 'paid for a REGISTERED VERSION V6 of FSUIIPC'. For details on FSUIPC6 & FSUIPC5 licenses, see John P.S. You posted in the FAQ sub-forum - I've moved your post, but please post all support requests here in the main forum.

See the Advanced User Guide, in section AUTOSAVE: INI-file only options. the AlsoManage ini parameter. John

If you have FSUIPC6, you do not need FSUIPC5. Did you see this: https://www.avsim.com/forums/topic/573578-new-linda-325-p3dv5fsuipc6-compatible-2-jun-2020/ John

FYI, FSInterrogate2 is included in the SDK for FSUIPC, and I think is also now one of the 'extras' for installation in FSUIPC6, outside of the SDK.

Just search the FSUIPC Offset Status manual - for elevator trim, see - 0BC0: Elevator trim control input: –16383 to +16383 - 0BC2: Elevator trim indicator (follows input) - 2EA0: Elevator trim deflection, in radians, as a double (FLOAT64). Up positive, down negative. - 3338: Elevator Trim Axis input value, post calibration, just before being applied to the simulation (if allowed to by the byte at offset 310A). And if its a PFC trim wheel and you are using the provided PFC driver, then also see offset 3370/3BA8 John

Hi Roger, copying and renaming your FSIOPC5.ini together with any other files (e.g. .lua, .mcro) you may use to the new installation directory is the way to use your FSUIPC5 settings with FSUIPC6. See the Installation and Registration guide. You can also use FSUIPC6 for P3Dv4, either the same or a separate installation. It is recommended to install outside of the main FS directory, especially if you have P3D installed under the Programs folder. It is also better to select a directory outside of the Prepare3D v5 Add-ons folder as this should really be just where the add-on.xml file is located. For example, I have it installed in d:\FlightSim\P3D Add-ons\FSUIPC6. There is no reason. The lua interface in FSUIPC6 is the same as that in FSUIPC5 and so should not need to be adapted (unless maybe the Aircraft has changed in some way that would necessitate a change, e.g. if using an lvar whose name had changed or been removed). Cheers, John

For all versions of FSUIPC, your settings are in the ini file - FSUIPC4,ini for FSUIPC4, FSUIPC5.ini for FSUIP5 and FSUIPC6.ini for FSUIPC6. They have nothing to do with the Prepar3d.cfg file. This will not affect FSUIPC. However, if you previously had controllers disabled in P3D, restoring a default P3D cfg file will re-enable controllers. That is the default installation folder for FSUIPC5, where your FSUIPC5.ini will be. If you re-installed P3D completely, this may/will have removed the entry to start FSUIPC, in the dlll.xml file. To add this again, just re-run the FSUIPC5 installer. Skip registration, as you already have a .key file, and you settings/.ini is also preserved on re-installation. John

FSUIPC offsets to control elevator/aileron/rudder (i.e. yoke axis) are 0BB2/0BB6/0BBA. See the provided FSUIPC Offset Status document. Are you using the provided SDK for MFC? if you are using C++, you can also do this directly using the SimConnect API (which is what FSUIPC uses).

@Pete Dowson No apologies needed, I am also perplexed and do not see any issues. I think it's a misunderstanding between what the 'installation' folder is and what the 'add-on.xml' folder is.

Correct. The Modules sub-folder. However, this is only the default location mandated by the FSUIPC5 installer. You can manually change this. For example, I have FSUIPC5 installed under D:\Prepare3D v4 Add-ons\FSUIPC5, and use the add-on.xml method with this and so also have an add-on.xml file under C:\Users\...\Documents\Prepar3D v4 Add-ons\FSUIPC5. No. It is ALWAYS looking in the same location, the FSUIPC6 installation directory. End of story. Previously you seemed to be asking for files to be installed in the FSUIPC6 add-ons directory... You can certainly suggest this but it's not going to happen. Why would I enforce something that is not recommended, i.e. to install files under the FS folder (i.e. in the Modules folder) or in the documents/add-ons folder. Nothing prevents you selecting either of these locations during the installation process, if you so wish, but as I say, this is not recommended. Enforcing this would be a step backwards. If the location and purpose of the P3D "add-ons" folder is confusing you, just use the old dll installation method (by unchecking the 'add-on.xml' checkbox during installation). Doing this, and selecting your old 'Modules' folder for installation, will result in the same install as done by FSUIPC5. FSUIPC6 is more flexible. John

No, this is not correct. You are confusing the FSUIPC6 installation location (the folder you select during the installation process, regardless of whether the add-on.xml method of installation is selected or not) and the location of the add-ons.xml file, which is pre-determined by P3D to the add-on folder location (and MUST be in a subdirectory of this folder, which I naturally call FSUIPC6). The add-ons folder subdirectory 'FSUIPC6' is NOT the installation location, although it can be. As I keep stating, NOTHING has changed. FSUIPC looks for files in its "installation" directory. The only thing that has changed is that this is now user-selectable, and not necessarily the 'Modules' folder, although you can still install there if you wish. John P.S. If you want everything to be installed in the FSUIPC6 add-ons folder, you can just select that during installation, and then you will have everything related to FSUIPC6 in the same place as the add-on.xml file.

Hi Andrew, I am slightly confused by your posts. Nothing has changed in the location of files between FSUIPC5 and FSUIPC6 - .MCRO files need to be in the FSUIPC5/6 installation directory. Thats it. In FSUIPC5 it always defaulted to the Modules folder (but you could manually change this if desired), and in FSUIPC6 it is the installation folder, the folder you select during the install process. This defaults to the P3D add-ons/FSUIPC6 folder, but should be changed. The add-on.xml file is always created in the add-ons/FSUIPC6 folder, as it needs to be there to be recognised by P3D. John

Hi Andrew, I've tested ipc.macro to call a mouse macro and its working ok. Is the macro in the correct place, i.e. in your installation folder (P3D v5 Addons) not in /FSUIPC6? Did the same and it works. Did you try lua logging? You are missing the ending quotes....could that be your problem, or just a typo? John

Make sure you have 'Enable Advanced Mouse Controls' unchecked in P3D (in 'Other Controls'). This should improve things, but there still seem to be issues related to P3Dv5. I will look into it.

That offset is in a reserved area, presumably reserved for IvAp use. You may be better off asking in the IvAp forum/support. In FSUIPC, the COM1/COM2 frequencies in BCD format are in offsets 034E/3118 and don't support 8 1/3KHz frequencies. There are also offsets 05C4/05C8 for active COM1/COM2 (read/write) that 4 byte ints and support the 8 1/3 frequencies, although I'm not sure these are available in FSUIPC4 (which I don't currently have) - please check the provided documentation.

You should try lua debug/trace logging to find errors in your lua scripts. The problem is in the quotes you are using: event.button(1,1,3, “Taxi_Test”) should be event.button(1,1,3, "Taxi_Test") Also, you can drop the ';': function Taxi_Test(a,b,c) ipc.writeSTR(0x3380, " TAXI ") ipc.writeSW(0x32FA, 4) ipc.sleep(4000) return end-- Main programipc.writeSTR(0x3380, " Loaded ") ipc.writeSW(0x32FA, 3)ipc.sleep(3000) event.button(1,1,3, "Taxi_Test")