Able to get to work with FSX-SE but not P3Dv2.4

[Andrew Roberts]

same computer

installer installs into fsx then gives me a warning that my P3D is newer and it may not install correctly, installs. 

I am trying to get my foreflight to work with it, works just fine with fsx not connecting with P3D, determined FSUIPC is the problem,

 

Any suggestions? 

 

thank you

[Pete Dowson]

same computer

installer installs into fsx then gives me a warning that my P3D is newer and it may not install correctly, installs. 

I am trying to get my foreflight to work with it, works just fine with fsx not connecting with P3D, determined FSUIPC is the problem,

 

Sorry, there's not enough information here. You don't even say what version of FSUIPC you are talking about. And your title talks about FSX-SE yet your text refers to FSX.

 

Please find the Installer log in the Modules folder and paste its contents into a message here. The reason the log is made is so that such install problems can be readily diagnosed!

 

Pete

[Andrew Roberts]

Okay I'm new to all this, below is the Installer. I have the Steam Edition FSX. That is the first one. FSUIPC works perfect on that. The second set is Prepar3d v2.4, it isn't working for that one. looks like the version I am trying to install is 4.938b. 

 

I really appreciate your help. Thank you

 

 

Installer for FSUIPC4.DLL version 4.938b

 

Looking in registry for FSX install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

     Parameter"SetupPath"

... >>>  OK! FOUND FSX!  <<< ...

     SetupPath=E:\SteamLibrary\steamapps\common\FSX

Looking in registry for FSX-SE install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0

     Parameter"SetupPath"

Not there, so looking in:

     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0

     Parameter"AppPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

     Parameter"SetupPath"

Not there, so looking in:

     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D

     Parameter"AppPath"

... NOT found! ...

Looking in registry for Prepar3D v2 install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2

     Parameter"SetupPath"

... >>>  OK! FOUND Prepar3D v2!  <<< ...

     SetupPath=F:\Program Files (x86)\Lockheed Martin\Prepar3D v2\

===========================================================

 

INSTALLATION FOR FSX:

SetupPath="E:\SteamLibrary\steamapps\common\FSX"

Checking version of the FSX EXE:

... Version 10.0.62607.0  (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

    Found SimConnect build 60905 (Original)

    Found SimConnect build 62607 (Steam Dec14)

    Found SimConnect build 61242 (SP1 May07)

    Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

       E:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.DLL

... Version 4.938b found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "E:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path: 

... found as "C:\Users\Owner\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\All Users\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Owner\AppData\Roaming"

Found FSX.CFG in "C:\Users\Owner\AppData\Roaming\Microsoft\FSX\FSX.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 FSX.CFG there

"Modules\FSUIPC Documents" folder already exists.

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 "ASN WX Radar facilities in FSUIPC4.pdf" okay

   Installed "Offset Mapping for PMDG 737NGX.pdf" okay

   Installed "FSUIPC4 Offsets Status.pdf" okay

   Installed "Profiles in Separate Files.pdf" okay

===========================================================

 

INSTALLATION FOR Prepar3D v2:

SetupPath="F:\Program Files (x86)\Lockheed Martin\Prepar3D v2\"

Checking version of the Prepar3D v2 EXE:

... Version 10.0.61637.0  (Need at least 1.0.677.0)

!! WARNING !! This version of Prepar3D is later than any known by this FSUIPC4.

   There may be problems. Please check for a later version of FSUIPC4!

Checking if there's already a version of FSUIPC4 installed in:

       F:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL

... No previous valid version found.

Prepar3D v2 Modules folder already exists.

Okay -- installed FSUIPC4 into "F:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path: 

... found as "C:\Users\Owner\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\Owner\AppData\Roaming"

Found Prepar3D.CFG in "C:\Users\Owner\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4_Loader section already exists but will be replaced.

     (with FSUIPC4_Loader entry)

... 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 created okay!

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 "ASN WX Radar facilities in FSUIPC4.pdf" okay

   Installed "Offset Mapping for PMDG 737NGX.pdf" okay

   Installed "FSUIPC4 Offsets Status.pdf" okay

   Installed "Profiles in Separate Files.pdf" okay

===========================================================

 

All installer tasks completed.

 

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

[Pete Dowson]

you appear to have a version of the Microsoft FSX.EXE renamed as Prepar3D,EXE in your P3D folder.

 

SetupPath="F:\Program Files (x86)\Lockheed Martin\Prepar3D v2\"

Checking version of the Prepar3D v2 EXE:

... Version 10.0.61637.0  (Need at least 1.0.677.0)

!! WARNING !! This version of Prepar3D is later than any known by this FSUIPC4.

 

 

 

Please right click on the Prepar3D.exe file and check Properties, check the version number and copyright details.

 

FSUIPC4 has actually installed for P2Dv2, but if the EXE actually being run is NOT P3D then things will go wrong, of course. That's why you get the warning.

 

In a normal P3Dv2 install there will only be one EXE, and that is the Prepar3D,exe and it has a version number like 2.4.11570.0, certainly not 10.0.61637.0, which is certainly FSX, not P3D.

 

Pete

[Andrew Roberts]

Pete, so I think I discovered the root of my problem finding the EXE, 

I had the estonia migration tool. 

I disabled fsx from in the tool, uninstalled the migration tool, and got rid of all exe files suggesting fsx in the Prepar3dv2. I then cleared out the modules folder and re-installed. 

It still says it can only find the fsx version. The only exe I have in there is 2.4.11570.0

Do you think this is the problem? Do you know where else I can look to find that fsx.exe? I don't use anything anymore that needs the migration tool, so I'm done with that. 

[Pete Dowson]

Pete, so I think I discovered the root of my problem finding the EXE, 

I had the estonia migration tool. 

I disabled fsx from in the tool, uninstalled the migration tool, and got rid of all exe files suggesting fsx in the Prepar3dv2. I then cleared out the modules folder and re-installed. 

It still says it can only find the fsx version. The only exe I have in there is 2.4.11570.0

Do you think this is the problem? Do you know where else I can look to find that fsx.exe? I don't use anything anymore that needs the migration tool, so I'm done with that. 

 

You don't want FSX.EXE for Prepar3D at all! The exe is Prepar3D.exe, and, yes, for 2.4 it should be 2.4.11570.0.

 

If you've changed things and re-run the FSUIPC installer, you'll need to show me the Install log again. I can't see your computer from here and can't determine what the problem is without a log.

 

These migration tools are a pain, because they try to make things look like something they are not. Therefore installers which know what they are doing cannot do the right thing. A proper migration tool would only make the changes temporarily, whilst you install the things that need it, then revert the installation back to its proper form.

 

Pete

[Andrew Roberts]

I Got It! This is going to sound totally off the wall though. 

I re-installed the Estonia Migration tool. Then I replaced the new Prepar3D Exe with P3D_Original and renamed it Prepar3D. 

Reinstalled FSUIPC, and it is working!

 

I don't know why but it is. I really appreciate your help. What you have put together is way above my comprehension and your skills make the flight simulation experience worlds better.

 

Thank you