Wondering if FSUIPC installed into P3D v2.1.1 correctly

[Paul K]

First off:

 

Windows 7 Pro 64 bit

 

P3D Version 2.1.9936.0

 

FSUIPC version 4.929

 

P3D has been run several times prior to installing FSUIPC

 

During installation, I had several messages pop up, which I show below in sequence. At the end of the process, it appears that both P3D is working correctly, and the FSUIPC interface is available in the sim under the Add Ons menu. All appears normal, and pretty much as I remember it in FSX. However, there is still a gnawing doubt; why all the error messages ?

 

Anyway, here's what happened after I right clicked on FSUIPC Installer.exe and ran it as administrator...

 

Picture 1

 

 

 

 

 

 

 

 

 

I clicked on the OK button in the picture above, and then I got this in Picture 2. To reiterate what I said at the beginning of this post, I have run P3D several times prior to this installing of FSUIPC. Honest !

 

Picture 2

 

 

 

 

 

 

 

 

I clicked on the OK button in the above picture, and I think it was at this point that I was asked to find P3D.exe myself, which I did. Things proceeded from there, as can be seen in Picture 3

 

Picture 3

 

 

 

 

 

 

 

 

I clicked on YES in the picture above, and then I have this appear in Picture 4

 

Picture 4

 

 

 

 

 

 

 

After clicking on the OK botton in the picture above, I arrive at the usual registration option as shown in Picture 5

 

Picture 5

 

 

 

 

 

 

 

 

 

At the end of all this, I decided to run the installer once again, just to see if it went normally ( I think I got the same message in Picture 4 again ). Anyway, here is the Install log :-

 

 

Installer for FSUIPC4.DLL version 4.929

Looking in registry for FSX install path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
Parameter"SetupPath"
Not there, so looking in:
HKEY_CURRENT_USER\FSX
Parameter"AppPath"
... NOT found! ...
Looking in registry for ESP install path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0
Parameter"SetupPath"
Not there, so looking in:
HKEY_CURRENT_USER\ESP
Parameter"AppPath"
... NOT found! ...
Looking in registry for Prepar3D install path:
HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
Parameter"SetupPath"
... >>> OK! FOUND Prepar3D! <<< ...
Looking in registry for Prepar3D v2 install path:
HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
Parameter"SetupPath"
... >>> OK! FOUND Prepar3D v2! <<< ...
===========================================================

INSTALLATION FOR Prepar3D:
SetupPath="D:\Lockheed Martin\Prepar3D v2"
Checking version of the Prepar3D EXE:
... Version 2.1.9936.0 (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Found SimConnect build 60905 (Original)
Found SimConnect build 195 (ESP Orig)
Found SimConnect build 61242 (SP1 May07)
Checking if there's already a version of FSUIPC4 installed in:
D:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
... Version 4.929 found.
Prepar3D Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Paul\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Paul\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
... No Prepar3D.CFG there
Cannot edit the DLL.XML file to activate FSUIPC.
===========================================================

INSTALLATION FOR Prepar3D v2:
SetupPath="D:\Lockheed Martin\Prepar3D v2\"
Checking version of the Prepar3D v2 EXE:
... Version 2.1.9936.0 (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Found SimConnect build 60905 (Original)
Found SimConnect build 195 (ESP Orig)
Found SimConnect build 61242 (SP1 May07)
Checking if there's already a version of FSUIPC4 installed in:
D:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
... Version 4.929 found.
Prepar3D v2 Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Paul\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
... No Prepar3D.CFG there
Looking in "C:\Users\Paul\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Paul\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
(for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Public\AppData\Roaming"
... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
Installed "SimConnectP3D2.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
Installed "FSUIPC4 User Guide.pdf" okay
Installed "FSUIPC4 for Advanced Users.pdf" okay
Installed "FSUIPC4 History.pdf" okay
Installed "List of FSX and P3D controls.pdf" okay
Installed "FSUIPC Lua Library.pdf" okay
Installed "FSUIPC Lua Plug-Ins.pdf" okay
Installed "Lua License.pdf" okay
Installed "Lua Plugins for VRInsight Devices.pdf" okay
Installed "LuaFileSystem.pdf" okay
Installed "Example LUA plugins.zip" okay
Installed "Offset Mapping for PMDG 737NGX.pdf" okay
Installed "FSUIPC4 Offsets Status.pdf" okay
===========================================================

All installer tasks completed.

*************** End of Install Log ***************

 

 

 

And here is a copy of DLL.XML which is located in C:\Users\Paul\AppData\Roaming\Lockheed Martin\Prepar3D v2 :-

 

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>

 

As I say, both P3D and FSUIPC seem to be running fine, so everthing might be okay and I'm worrying about nothing. All I need is a 'Yes, that all looks okay' ... or help with whatever might be wrong.

 

Many thanks in anticipation

[Pete Dowson]

As I say, both P3D and FSUIPC seem to be running fine, so everthing might be okay and I'm worrying about nothing. All I need is a 'Yes, that all looks okay' ... or help with whatever might be wrong.

 

 

Yes, it is all okay. All the errors are for the installation of FSUIPC for P3D version 1. You appear to have version 1.4 entries in your registry now pointing to the same place as P3D v2. I suspect you uninstalled V1 incorrectly, so registry entries were still left pointing to the wrong place. Then when you pointed the Installer to your V2 EXE file after it couldn't find the V1 EXE there, it updated the V1 path to point to V2. See this part of the final log which is referring to P3D v1 not V2 (which follows successfully, later in the log).

INSTALLATION FOR Prepar3D:
SetupPath="D:\Lockheed Martin\Prepar3D v2"
Checking version of the Prepar3D EXE:
... Version 2.1.9936.0 (Need at least 1.0.677.0)

Pete

[Paul K]

Pete, thanks hugely for the help. It really is appreciated.  :)

 

This business with uninstalling P3D v1... I had similar errors when installing FSUIPC into v2.0 last year, and read a thread here where someone had had the same problem. You advised him about the incorrect uninstall of v1, and so I decided to uninstall v2.0, ran Ccleaner, and then went through the registry 'by hand' so to speak, deleting every reference to Lockheed Martin that I could find, so ensuring ( I hoped ) that there was nothing remaining that referred to v1 or v2.0.

 

At that time I deleted both the folders you see here, in HKEY_CURRENT_USER / Software. Both folders reappeared after installing P3D v2.1. Is that correct ...what I mean is, should there still be two Lockheed Martin folders as shown ? I know you are a busy bloke, and I don't want to put you to any further trouble on my behalf...but if having two Lockheed Martin folders is correct, could you tell me where else the references to v1 might be in my registry ? 

 

 

 

[Pete Dowson]

At that time I deleted both the folders you see here, in HKEY_CURRENT_USER / Software. Both folders reappeared after installing P3D v2.1. Is that correct ...what I mean is, should there still be two Lockheed Martin folders as shown ? I know you are a busy bloke, and I don't want to put you to any further trouble on my behalf...but if having two Lockheed Martin folders is correct, could you tell me where else the references to v1 might be in my registry ? 

 

The "LockheedMartin" subfolder "Prepar3D" is for version 1. It seems you didn't really delete it, because installing version 2 or 2.1 will not add back in entries for Version 1.

 

It won't do any real harm as far as I know, it will just cause spurious error messages and double installs like you saw. There's no where else I know of the entries might be.

 

Pete

[Paul K]

Okay Pete, well, if and when I next uninstall P3DV2.1, I'll take some screenies of the registry before, during and after. I swear I uninstalled both v1.0 and v2 correctly -  I don't suppose there could be a remnant of the 1.4 installer thats been left inside the 2.0 installer by Lockheed Martin, is there ? Something that reintroduces that spurious v1.0 folder when you install v2.0? Just a bit of uninformed speculation on my part.

 

Anyway Pete, thanks again for your time and help. Very much appreciated.  :)

[Ian P]

Paul,

 

The uninstallation routine for P3D v1.4 didn't remove a significant amount of the sim - especially registry entries - on my PC. I had to spend some time removing all traces manually before I was able to successfully install P3Dv2. I believe a lot of other people fell foul of this, too.

 

Ian P.

[Paul K]

Ah, thanks for that Ian. If I ever have to do yet another reinstall of P3D, I might come back to this thread and pick your brains on that. Its certainly reassuring to know I'm not alone. Thanks again !

 

By the way, a bit off topic, but thanks for doing RAF East Wretham. I used to drive past it every day going from Thetford to Watton. Its a neat little Army camp now, for troops using the nearby STANTA battle area. Much enjoyed it in FSX. :)