John Dowson

Just release v6.0.8, available from the usual places. John

Hi Marc, I will be releasing FSUIPC v6.0.8 which is compatible with the Active Sky Beta a little later today. Cheers, John

No Need. FSUIPC3 is now free (as well as WideFS6) - please see the www.fsupic.com for license details. John.

First, you have posted in the FSUIPC client DLL forum - is this a question about the .net client dll, or a general FSUIPC question? P3Dv5 HF1? There will be a new FSUIPC6 released shortly (probably tomorrow now) that is compatible with ActiveSky for P3Dv5. John

Sorry, just checked the add-on.xml I provided and it was incorrectly specifying your add-on in a folder for v5. If you want to use the add-on.xml install method, you can try again with the following add-on.xml: add-on.xml

So you got the pop-up asking you if you wanted to activate FSUIPC6 (so it recognised the add-on.xml), you approved (clicked 'Yes'), but there was still no FSUIPC entry in your add-ons menu? If that is the case, its very strange and I would have to see your SimConnect log to resolve this. But if you are happy using the dll.xml install method, just go with that. John

0x3C00 does contain the AIR file - from the documentation: Flt sim path is in offset 0x3E00: I cannot see how offset 0x3124 can be empty - it is set directly after the P3D version is reported. Please try the following dll - this just contains an extra logging statement when offset 0x3124 is set: FSUIPC6.dll John

The problem is this: Cannot determine location of P3Dv4 add-on folder This is due to the fact that the installer cannot determine the location of your Documents folder from the registry (i.e. some standard windows registry entries are missing). You have two options: 1. Manually create the required add-on.xml file. Place the following file under C:\Users\KYH\Documents\Prepar3D v4 Add-ons\FSUIPC6 : add-on.xml This should work IF P3D still recognises your add-ons folder under Documents. 2. Re-run the installer but this time uncheck the 'add-on.xml' checkbox. This will then install FSUIPC6 using the older dll.xml install method.

In P3Dv4.5, P3Dv5 or both? There is no Modules folder with FSUIPC6, unless that is the folder you selected during the installation process. Please see the provided Installation and Registration manual for details on installation options and file locations. Then I need to see your installation log. No, it doesn't matter where P3D is installed. Suggest you read the provided installation manual and try again. If you still have problems, please post your installation log. John

Please see the Installation and Registration manual - it explains what is installed and where. Documents are now installed in a folder called FSUIPC6, located under your windows Documents folder. John

This has now been corrected in release 6.0.7.

Confirmed. The correction for when using the LuaPath ini parameter released last night introduced this problem. Sorry about that - I will look into it. As a temporary work-around, add the following to the [LuaFiles] section of your .ini file: LuaPath=<your installation directory>

Yes, it's a lot easier to sort out problems when this is done. If you are using a new rig, then the GUIDs could have changed, as well as the ids. It should be possible to sort this out though. Please post your .ini and .log files as well, and I'll take a look. Cheers, John

Hi Steve. yes, it's possible. When you run the installer it will ask which version of P3D you would like to install FSUIPC into. Just untick the P3Dv4 checkbox and it will install into v5 and leave your v4 installation as-is. Please see the provided Installation and Registration manual. Cheers, John

Hi Claudio, you can use them via any method: using the provided offset controls, via the provided lua scripting interface, or using one of the provided SDK libraries (for various programming languages). Regards, John

What further documentation do you expect? It is just what it says, an offset area of size 64 bytes starting at offset 66C0 that is free for general use. You can write/read any values you want/need in that offset range.

This should now be corrected in v6.0.6, just released.

That is a very old version of FSUIPC4 you are using. The latest is 4.974 - first please download and try this version, available from the Download Links -> Updated Modules section, or over on www.fsuipc.com. If you still have issues after this, suggest you first check the forums for similar issues (there are many posts regarding start-up issues with FSX!), and only if you cannot find a solution in a previous post, then post again and include your .log file and further information - just saying 'I am not able to run FSUIPC4' doesn't give us any information to enable us to help you. John

Confirmed. The next pointer is not being initialised correctly on re-start. I will fix this in the next patch release.

No, not possible at the moment, sorry. John

Hi Philippe, we are currently very busy looking into trying to provide an FSUIPC version for the upcoming MSFS, and investigation into minor issues with offsets is on hold for the time being. I have flagged this and will look into it when time permits. John

Yes, you can do that. You could also check the DLL.xml file and remove the entry for FSUIPC5 to remove it completely, as well as the FSUIPC Documents folder.

Hi Cesar, for Project Magenta, you really need to contact their support. For setting/changing bits in a byte offset in FSUIPC, see the controls 'Offset Byte Setbits' and 'Offset Byte Togglebits'. Cheers, John P.S. You posted in the FAQ sub-forum. Please post requests in the main support forum - I have moved your post this time.

Sorry, I guess your problem is fixed! Maybe better to have added that after your support request, or as a separate comment. I still recommend that you update though!

First, could you download and install the latest version of FSUIPC6, v6.0.5. Once done, please attach your new log together with your ini file - Joyscan.csv is not needed. Thanks, John P.S. If using the dll.xml install method, there was a problem in the uninstaller generated by the installer in previous versions, which had the affect of leaving multiple FSUIPC6 entries in the DLL.xml file. If you are using this install method, best to check this file after install and remove any duplicate entries.