John Dowson

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")

Blimey, how did you discover that? I see its not documented and didn't know about this! I'll check and update the documentation. Not possible at the moment I'm afraid. I could make the DELAY option take a parameter (i.e. DELAY=<n>) in the Run/RunIf options. However, we're pretty busy at the moment and it will take a while fo me to get around to this. I've flagged this and will look into it when time permits. Cheers, John

No. First install FSUIPC6. When you do this, it will automatically detect your FSUIPC5 installation and uninstall this. It will only remove the dll, documents and .log files. During the installation process, take care to select your new installation directory - it will default to the old one (i.e. the P3D Modules folder). Change this. After you have installed, copy your FSUIPC5.ini file from your old Modules folder to the new installation folder, renaming it to FSUIPC6.ini. Then move all other files you want to preserve to your new installation folder - the .lua files, .pdf and your Lua and PMCO_Sounds folder. After that, you can remove your Modules folder, although I would suggest keeping it for the time being, at least until you have everything set-up and working in the new location. Well, not everything. Only for your new joystick - if you have any other devices, they will be preserved. It is possible to manually hack the .ini to switch your settings from your old joystick to the new one, but this is difficult as you do not know what the button numbers are. You would have to use FSUIPC to see the joystick id and button numbers, so you may as well redo your assignments there. The calibration details, if using that facility, would also be different for a new joystick, so always better to re-calibrate.

If you choose to install FSUIPC6 in the same location as FSUIPC5 (i.e. the Modules folder), then just renaming your FSUIPC5.ini to FSUIPC6.ini should work. Alternatively (and recommended) you can install FSUIPC6 outside of your sim folder, in which case you need to move as well as rename the FSUIPC5.ini, as well as any auxiliary files that you use. Updating from FSUIPC5 to FSUIPC6 is covered in the provided Installation and Registration manual. Please see that for details. The easiest/cleanest way is to just set this up as a new joystick - i.e. redo your assignments and calibration for that joystick.

Your install log shows that you installed FSUIPC6 in C:\Users\Prepar3D\Documents\Prepar3D v5 Add-ons\FSUIPC6. So that is where your .lua files need to go. With FSUIPC6, it is no longer necessary to install FSUIPC into a Modules folder, although you can do if you wish. You choose the installation folder during the installation process, and it looks like you accepted the default location for a new installation, which is the location of the add-ons.xml file. It is recommended to select a different location. Please see the provided installation guide.

Standard fromat, as specified by P3D. You could just re-run the installer and uncheck the 'add-on.xml' entry to install via the dll method. Your first line is not correct: fsuipcp3d<?xml version="1.0" encoding="UTF-8"?>

There is XPUIPC for X-Plane, by a different developer. See http://www.schiratti.com/xpuipc.html

You forgot to add the .log file to the zip archive. You are also using FUIPC6 v6.0.7 - please also update to the latest version, v6.0.8.

As I have said, this is because that folder was empty. It did not contain your key file. Just look at your uninstall log - notice this: Delete file: C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC6.dll This tells me that you installed FSUIPC6 into your P3Dv4 Modules folder. As I said, this will be the default location if you install FSUIPC6 to replace an FSUIPC5 installation. When you installed here (and using the add-on.xml install method), the installer will also create the FSUIPC6 folder and add-on.xml file here (from where it was removed): Delete file: C:\Users\sergi\OneDrive\Documents\Prepar3D v4 Add-ons\FSUIPC6\add-on.xml Remove folder: C:\Users\sergi\OneDrive\Documents\Prepar3D v4 Add-ons\FSUIPC6\ Nothing else is created (or should be) in that folder. When you uninstall FSUIPC6, it will be removed. So, your FSUIPC6.key file would have been created in your installation directory, i.e. in C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\ It won't happen again and it didn't happen in the first place. You just did not know where you installed. The installer for this version is very different from previous installers - it has been completely re-written, as FSUIPC6 now supports multiple simulator versions (i.e. P3Dv4 and P3Dv5), and also gives you the flexibility to have one installation for both sim versions, or separate installations.

There is only a discount if you have already purchased FSUIPC5, which is applied automatically via SimMarket in checkout. No discount for FSUIPC4 license holders.

You can zip it up and then attach. We also need to see your FSUIPC6.ini file. Did you rename your FSUIPC5.ini file to FSUIPC6.ini (and also move it to the new installation folder, if you changed that)?

No Check the provided documentation. There is also an example lua script provided, called HidDemo.lua (in the Documentation, in the Example Lua plugins.zip. John

Yes - read this: You need to either buy or request (if you purchased your FSUIPC5 license on or after 01/02/2020) a new key. John

You can use the Lua interface (HiD functions in com library) to program more than 32 buttons.

Yes, it removes the FSUIPC6 folder from your v4 add-ons directory as you uninstalled and this folder is empty, after the add-on.xml file is removed. Its empty as you installed FSUIPC6 into your P3Dv4 Modules folder. It did this as this is the default location when installing FSUIPC6 if you previously had FSUIPC5 installed, and you just blindly accepted this location rather than choosing another. If the registration fields were empty (in the registration page during installation) then this is because there is no key file in the folder where you installed. You just need to copy your previous FSUIPC6.key file from where it was originally registered (i.e. your P3Dv4 Modules folder) to the new installation location. Please read the installation manual.

FSUIPC6 is installed in the folder that YOU SELECT during the installation process. It has a default location (it has to!) which is: - if an existing version of FSUIPC5 or 6 is found for the sim you are installing into, it will default to the same folder - for a new/clean installation, it defaults to the P3D defined default add-on.xml location. It is recommended to change this So, in your case, as you previously had FSUIPC5 installed in the P3Dv4 Modules folder, it will default to this. You should have changed this during the installation process. Basically, it has been designed to install wherever you want. You just have to pay attention during the install process and choose the location to install rather than blindly accepting the default value. This is all explained in the provided Installation and Registration guide. If you want to move it to a different location, just re-run the installer, and this time select the folder in which you want to install. Also note, that you can have one installation for P3Dv4 and P3Dv5 if you like (i.e. one folder for both sims), or you can have separate installations for each sim, by running the installer twice. Again, all explained in the Installation manual.

No, this shouldn't cause your issue. However, if you have re-connected your USB devices in any way, the joystick Ids could have changed if you are not using the 'JoyLetters' facility (see User manual for details). You can try activating this by setting AutoAssignLetters=Yes in the [JoyNames] section of your ini. Then start the sim. If the quadrants are still the wrong way around, you can close the sim, open the ini and swap the assigned letters around (for both entries, descriptive and GUID), save the ini and then restart the sim to check.