Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi, Im trying to install fsuipc on my P3dV2.2 + hotfix install

 

I waited for the v493 release and I installed it, but now P3D wont start

 

Install log below, please help

 

Installer for FSUIPC4.DLL version 4.93


Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
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 FSX:
SetupPath="C:\Lockheed Martin\Prepar3D\"
Checking version of the FSX EXE:
Couldn't obtain Version Info! Asking user to find FSX.EXE ...
User aborted attempt to find FSX. Installation failed.
===========================================================


INSTALLATION FOR Prepar3D:
SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D v2"
Checking version of the Prepar3D EXE:
... Version 2.2.10438.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 compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 195 (ESP Orig)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
... Version 4.930 found.
Prepar3D Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Adam\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\Adam\AppData\Roaming"
 ... No Prepar3D.CFG there
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\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Cannot edit the DLL.XML file to activate FSUIPC.
===========================================================


INSTALLATION FOR Prepar3D v2:
SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D v2"
Checking version of the Prepar3D v2 EXE:
... Version 2.2.10438.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 compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 195 (ESP Orig)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
... Version 4.930 found.
Prepar3D v2 Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Adam\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\Adam\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Adam\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\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\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 "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay

 

Posted
I waited for the v493 release and I installed it, but now P3D wont start

 

 

What happens? Have you any crash data, eg, from the Windows event viewer? Is an FSUIPC4.LOG file produced in the Modules folder? Is so please show it to me.

 

I notice some oddities on your system but not ones which would affect this:

 

Looking in registry for FSX install path:

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

     Parameter"SetupPath"

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

 

 .....SetupPath="C:\Lockheed Martin\Prepar3D\"

Checking version of the FSX EXE:

Couldn't obtain Version Info! Asking user to find FSX.EXE ...

User aborted attempt to find FSX. Installation failed.

 

 

 

You appear to have removed FSX without properly uninstalling it. Not only that but its install path is pointing to Prepar3D!!!

You should really remove the remnants now in the Registry. i.e. the section 

 

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

 

Further, you have installation entries for both Prepar3D v1 and v2 both pointing to the same place! You do really need to do complete uninstalls if you are going to keep installing in one folder. You should remove this section too:

 

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

 

However, despite all these oddities your P3D should start okay. I really need more data on that.

 

Pete

Posted

I notice you have a later release of P3D 2.2 that I:

 

... Version 2.2.10438.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!

 
Mine is build 10437. Strange. I downloaded mine on moday! If they've updated it aghain I may have a lot more work to do....:-(
 
Pete
Posted (edited)

Thanks for the support Pete and getting into the detail with those regsitry items I appreciate it

 

Ok, so your points:

 

1. LM compiled a new build to deal with a regression bug that crept into v2.2 which caused CTDs with the flight planner. LM released it as a hotfix with just the binaries and advised users to manually install the new binaries. Heres their forum post about it:

 

http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=6453

 

2. I was forced into a hard delete of FSX due to problems with the FSX uninstall utility. I had some trouble finding the path in the registry for it but after searching I eventually found it under WOW64:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\flight simulator\10.0

 

Thanks for that I deleted those keys

 

3. I deleted the old P3D v1.xx keys thanks again for that, also eventually found those under the WOW64 entries in the registry. Strange, with 1.xx I did uninstall it using LM's program and it gave no error on completion. Maybe they see it as cruft that doesnt matter? Anyway its gone now.

 

4. Heres the log output from FSUIPC4.log when P3D crashes

 

********* FSUIPC4, Version 4.93 by Pete Dowson *********
Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.ini"
Running inside Prepar3D v2 on Windows 8
Module base=54E50000

I searched through the event viewer but there is no captured errors relating to P3D in any of the logs, not even info level entries. Or am I looking in the wrong logs is it obscure somewhere for application level P3D event messages?

 

The crash behaviour is the user tries to enter runtime, the p3d splash graphic appears, then it crashes without further dialogue windows or apparent problems - just a usual CTD.

 

As an aside Im running windows 8.1 not 8 like the log entry states

 

5. Unfortunately I tried again to run P3D post the registry key changes and P3D still CTDs like before, like you advised me.

 

EDIT: Include detail of registry changes not resolving the CTD

Edited by nullack
Posted (edited)

Hi again Pete, I just grabbed your new build 4.931 thanks for the fast turn around

 

FSUIPC is loading in P3D ok now, it operates

 

I did get some warnings during install despite doing the registry cleans that were suggested. One about registry with P3D and the other about not editing the xml file. I've attached logs below, its late night here I'll need to try to make sense of it with a clear head after sleep. The install seems to think p3d 1.xxx is installed but its absolutely not installed. 1.xxx and 2.xxx use different sub directories anyway.

 

Installer for FSUIPC4.DLL version 4.931


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"
Not there, so looking in:
     HKEY_CURRENT_USER\Prepar3D
     Parameter"AppPath"
... >>>  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="C:\Lockheed Martin\Prepar3D\"
Checking version of the Prepar3D EXE:
Couldn't obtain Version Info! Asking user to find Prepar3D.EXE ...
User identified path:
   "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2"
Checking version of the Prepar3D EXE:
... Version 2.2.10438.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)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
... Version 4.930 found.
Prepar3D Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Adam\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\Adam\AppData\Roaming"
 ... No Prepar3D.CFG there
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\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Cannot edit the DLL.XML file to activate FSUIPC.
===========================================================


INSTALLATION FOR Prepar3D v2:
SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D v2"
Checking version of the Prepar3D v2 EXE:
... Version 2.2.10438.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)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
... Version 4.931 found.
Prepar3D v2 Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Adam\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\Adam\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Adam\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\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\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 "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
===========================================================


All installer tasks completed.


*************** End of Install Log ***************
 
********* FSUIPC4, Version 4.931 by Pete Dowson *********
Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.ini"
Running inside Prepar3D v2 on Windows 8
Module base=54C50000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
       47 System time = 17/04/2014 23:08:42
       47 FLT path = "C:\Users\Adam\Documents\Prepar3D v2 Files\"
       47 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\SimConnectP3D2.dll
       47 Found it: trying to connect
       63 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\"
      375 LogOptions=00000000 00000001
      375 SIM1 Frictions access gained
      375 Wind smoothing fix is fully installed
      375 SimConnect_Open succeeded: waiting to check version okay
      375 Trying to use SimConnect Prepar3D
     5719 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.2.10438.0 (SimConnect: 2.2.0.0)
     5719 Initialising SimConnect data requests now
     5719 FSUIPC Menu entry added
     5719 C:\Users\Adam\Documents\Prepar3D v2 Files\Adams.FXML
     5719 C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\SimObjects\Airplanes\Mooney_Acclaim\Mooney_Acclaim.AIR
    28203 System time = 17/04/2014 23:09:10, Simulator time = 10:46:40 (01:46Z)
    29109 Starting everything now ...
    30438 Advanced Weather Interface Enabled
    56859 System time = 17/04/2014 23:09:39, Simulator time = 10:46:45 (01:46Z)
    56859 *** FSUIPC log file being closed
Average frame rate for running time of 9 secs = 34.9 fps
Memory managed: 8 Allocs, 8 Freed
********* FSUIPC Log file closed ***********

Edited by nullack
Posted

As an aside Im running windows 8.1 not 8 like the log entry states

 

FSUIPC treats them the same. 8.1 is merely an increment over 8.0, like the SP's on the Win XP, Vista and Win7 version(s).

 

I did get some warnings during install despite doing the registry cleans that were suggested. One about registry with P3D and the other about not editing the xml file. I've attached logs below, its late night here I'll need to try to make sense of it with a clear head after sleep. The install seems to think p3d 1.xxx is installed but its absolutely not installed. 1.xxx and 2.xxx use different sub directories anyway.

 

 

he warnings don't really matter in the end, but they are definitely occurring because there are entries in the Registry pointing to a non-existent P3D v1. It is looking it here:

 

SetupPath="C:\Lockheed Martin\Prepar3D\"

 

because of the Registry entry at:

 

     HKEY_CURRENT_USER\Prepar3D

     Parameter"AppPath"

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

 
Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.