Jump to content
The simFlight Network Forums

Latest FSUIPC installed into P3D 3.1 but missing in the drop down menu


Recommended Posts

Hi Pete,

 

I installed and registered FSUIPC and it created the Modules folder and I think is everything that is supposed to be in it including SimConnectP3D2.dll which the log file says it can't find.  So far P3D 3.1 has been a royal PITA so may get my money back and continue w/ 2.3 which was flawless and I adjusted fine to its VAS limits for 2.7y.  The Saitek Cessna Trim wheel conflicts w/ 3.1 and never did w/ 2.3.  FWIW and maybe this is material when I wiped my drive and started w/ a fresh Win 7 SP1 install I decided not to install any Windows Updates whatsoever as this is how I had 2.3 installed for 2.7y.  This drive is isolated from web surfing or other use beyond P3D so didn't find a need for A/V software or other.

 

Anyway, what next please and thanks in advance.  

 

********* FSUIPC4, Version 4.949f by Pete Dowson *********

Prepar3D.exe version = 3.1.2.15831
Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 7
Module base=60F70000
User Name="Noel Phares"
User Addr="ncp10@pacbell.net"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 04/03/2016 07:33:53
        0 FLT path = "C:\Users\NoelPhares\Documents\Prepar3D v3 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 3.1.2.15831
        0             api.dll: 3.1.2.15831
        0        controls.dll: 3.1.2.15831
        0      fs-traffic.dll: 3.1.2.15831
        0             G3D.dll: 3.1.2.15831
        0        language.dll: 3.1.2.15831
        0            sim1.dll: 3.1.2.15831
        0        visualfx.dll: 3.1.2.15831
        0         weather.dll: 3.1.2.15831
        0          window.dll: 3.1.2.15831
        0 ----------------------------------
        0 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll
       16 !!! Error 126: The specified module could not be found. 
      328 NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.
      359 NOTE: SimConnect SP1 May07 is supported, but it isn't installed.
      374 NOTE: SimConnect Original is supported, but it isn't installed.
      374 FATAL ERROR: FSUIPC4 cannot connect to any supported version of SimConnect!
      390 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\"
      686 ---------------------- Joystick Device Scan -----------------------
      686 Product= Pro Flight Cessna Yoke
      686    Manufacturer= Saitek 
      686    Vendor=06A3, Product=0BD3 (Version 1.22)
      686    Serial Number= RD002340
      686 -------------------------------------------------------------------
      702 LogOptions=00000000 00000001
      702 -------------------------------------------------------------------
      702 ------ Setting the hooks and direct calls into the simulator ------
      702 --- CONTROLS timer memory location obtained ok
      702 --- SIM1 Frictions access gained
      702 --- FS Controls Table located ok
      702 --- Installed Mouse Macro hooks ok.
      702 --- Wind smoothing fix is installed
      702 --- All links okay (except older global weather setting method)
      702 -------------------------------------------------------------------
      702 Could not link to all needed SimConnect facilities
      702 Trying to use SimConnect Original
    15740 ... Now trying to connect to another version of SimConnect ...
    15740 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll
    15740 !!! Error 126: The specified module could not be found. 
    30779 ... Now trying to connect to another version of SimConnect ...
    30779 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll
    30779 !!! Error 126: The specified module could not be found. 
    50669 System time = 04/03/2016 07:34:44
    50669 *** FSUIPC log file being closed
Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps
Minimum available memory recorded was 32768Mb
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
 
 
<?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>
Link to comment
Share on other sites

I installed and registered FSUIPC and it created the Modules folder and I think is everything that is supposed to be in it including SimConnectP3D2.dll which the log file says it can't find. 

 

The answer is to actually install SimConnect yourself, as pointed out in the pinned topic

"P3D Version 3: FSUIPC menu entry not appearing" at the top of this forum.

 

Pete

Link to comment
Share on other sites

The answer is to actually install SimConnect yourself, as pointed out in the pinned topic

"P3D Version 3: FSUIPC menu entry not appearing" at the top of this forum.

 

Pete

OK thanks, was guessing maybe this was figured out since the post was back in Oct but apparently not.  I assume it's just a case of executing the .msi?  Then do I reinstall FSUIPC4 again?  Maybe just try re-loading P3D...

 

Thanks as you would know--all's well ;o)

Link to comment
Share on other sites

OK thanks, was guessing maybe this was figured out since the post was back in Oct but apparently not.  I assume it's just a case of executing the .msi?  Then do I reinstall FSUIPC4 again?  Maybe just try re-loading P3D...

 

No, don't reinstall anything. Just run one or more of the SimConnect.msi's. L-M don't seem to be bothered at all about FSX SimConnect add-ons and P3D doesn't install ANY FSX SimConnect versions by default, it only supplies them for you to install. You should probably install both the SP1 and the SP2/Acc versions for best support of FSX add-ons.

 

I've no idea why my work-around, supplying and installing my own DLL, doesn't work on some folks' systems. The file is there but Windows simply doesn't see it or doesn't allow access to it! 

 

Pete

Link to comment
Share on other sites

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.