John Dowson

I have corrected the problem in the installer. It will now show a message an exit if it cannot determine where either P3Dv4 or P3Dv5 is installed. However, this will not help you that much as you still won't be able to install FSUIPC6. I need to determine why you don't have the P3D registry keys installed. Could you try re-installing the P3D Client, then download and try the latest installer for FSUIPCv6.0.8 \9installer version 1.2.2) I am going to install the latest 4.5 HF to see if there is an issue there. Thanks, John

Pierluigi, thanks for the pictures, but what I really need is the log. Next time, if the log file isn't produced, can you copy the log text that is displayed when you click the 'Details' button, and paste that for me. But the picture of the small section of the log shows what you issue is: the installer can't determine where your P3D installation is from the registry (or if it is installed at all). I will look into handling this better - the installer should really have aborted (nicely!) and not installed anything, as it cannot find either P3Dv4 or P3Dv5 on your system. This is also why its defaulting to a P3Dv5 folder for your installation. What version of P3Dv4 to you have installed? I've not installed the latest v4.5 HF, maybe they've changed the registry keys used.

Sorry, but what has this got to do with FSUIPC? I think you posted in the wrong forum.

Did you do this manually? Installing/uninstalling FSUIPC will only ever removes files it creates during the installation process, as well as log files. It will not remove .ini or .key files (or any other files, such as .mcro or .lua) so that these can be re-used, and these must be manually removed if needed.

Maybe you could also try only installing the dll (i.e. uncheck the other sections - 'Documentation' and 'Extras'). I need to narrow it down to determine which install section is generating that error. If that works ok, you can then add the others back in, one at a time, to determine which install section is generating that error. Thanks, John

Can you press the 'Next' button, or is that inactive? If its active, please try that. The installation .log file will be in the same folder as the installer - it is only copied to the installation folder at the end of (successful) installation. Could you check to see if you have a .log file there and if so please show it to me. So you still get the pop-up 'Invalid opcode' message, but you can complete the installation? Do you have an installation log for this - if so, please post it. So FSUIPC is actually installed and running via this method? That message is most probably because the installer didn't complete and didn't write the reg keys expected by the uninstaller. It would also be helpful if you attached the full uninstall log, so I can check this. Do you have any anti-virus software running (besides Windows Defender)? If so, maybe also try with this de-activated. Thanks PierLuigi, John

Hi Andrew, thanks for the update. If there is no P3D running, there is no FSUIPC and no offsets to read...! Cheers, John

Yes, that makes more sense! Regards, John

Ok, thanks. So the installer IS running, but it's failing with that message towards the end of the installation process (and before registration). I just wanted to check the size of the installer exe, to verify it is the same as expected. Not needed now though as the installer runs. What happens when you click the 'Ok' - does the installer just exit? Can you see if the installer has generated a log file in the same folder as where you ran the installer - if so, can you please attach. If not, and the installer is still running after the invalid opcode message, you could click the 'Show details' button and copy the contents and paste them here for me to see. It looks like the installer is failing to create the add-on.xml for some reason. Could you also try installing via the dll.xml method instead please - just un-tick the 'add-on.xml' checkbox in the components selection during installation. You can also try running the uninstaller that has been created first.

see

Hi Pierluigi, I currently have no idea what is causing this for a few people. It has been downloaded and used many thousands of times without issues, so this issue must be specific to certain set-ups. And people are providing little information for me to investigate. Could you let me know the following please: - when do you actually get the error - is it produced as soon as you run the installer exe? - what windows version/patch level are you using? - could you provide a screenshot of the properties of the Install_FSUIPC6.exe file please - and make sure you are using the latest version (6.0.8) Thanks, John

Glad its working for you, but deleting your FSUIPC5.ini file would have no affect on FSUIPC6, so I think your problem was elsewhere and this is just a coincidence.

First, you hijacked an unrelated thread. Please do not do this. For FSX, you need FSUIPC4. John

Then why didn't you post there instead of starting a new thread for exactly the same problem? As well as what Thomas has said, make sure that you have unzipped the downloaded package and are not trying to run the installer directly from the zip file. You can also try running the installer as an administrator, as it looks like this error can be caused by incorrectly set permissions on your account.

FSUIPCv6.0.8 has just been released.

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