Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi,

 

I've just installed FSUIPC4 and it installed successfully into FSX and p3dv3, but when I start p3d it crashes while starting up with fatal error. when I delete the FSUIPC files from modules, p3d starts fine. 

 

here is the windows error log from event viewer,

 

Log Name:      Application
Source:        Application Error
Date:          11/3/2015 3:55:44 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      nick-PC
Description:
Faulting application name: Prepar3D.exe, version: 3.0.10.14945, time stamp: 0x560b4abe
Faulting module name: FSUIPC4.dll, version: 4.9.4.8, time stamp: 0x56378f44
Exception code: 0xc0000005
Fault offset: 0x00015421
Faulting process id: 0x18c8
Faulting application start time: 0x01d116500d4fad7d
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.dll
Report Id: 56ba0523-8243-11e5-93db-382c4abbffdf
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-11-03T15:55:44.000000000Z" />
    <EventRecordID>4452</EventRecordID>
    <Channel>Application</Channel>
    <Computer>nick-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>3.0.10.14945</Data>
    <Data>560b4abe</Data>
    <Data>FSUIPC4.dll</Data>
    <Data>4.9.4.8</Data>
    <Data>56378f44</Data>
    <Data>c0000005</Data>
    <Data>00015421</Data>
    <Data>18c8</Data>
    <Data>01d116500d4fad7d</Data>
    <Data>C:\Program Files\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>
    <Data>C:\Program Files\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.dll</Data>
    <Data>56ba0523-8243-11e5-93db-382c4abbffdf</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
 
And the FSUIPC log,
 
Running inside Prepar3D on Windows 8.0
Module base=185E0000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
      438 System time = 03/11/2015 15:55:39
      438 FLT path = "C:\Users\nick\Documents\Prepar3D v3 Files\"
      438 Trying C:\Program Files\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D.dll
      453 Found it: trying to connect
      469 FS path = "C:\Program Files\Lockheed Martin\Prepar3D v3\"
      484 LogOptions=00000000 00000001
      484 -------------------------------------------------------------------
      484 ------ Setting the hooks and direct calls into the simulator ------
      484 Failed to find CONTROLS timer memory location!
      484 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!
      484     Reason 6: SIM1 base=77C00000
      484     FrictionAddr=77C30108 contains 100FF200
      484     BrakingAddr=77C313C8 contains 8B088B5E
      484 Hook Error: can't find .37 in SIM1.dll
      484 Hook Error: can't find .37 in VISUALFX.dll
 
I'm running Windows 10, 32bit.
 
Any help would be much appreciated,
 
thanks,
 
Nick
 

 

 

Posted

I've just installed FSUIPC4 and it installed successfully into FSX and p3dv3, but when I start p3d it crashes while starting up with fatal error. when I delete the FSUIPC files from modules, p3d starts fine. 

 

The crash is happening because although the main P3D exe program appears to be the correct, the modules which FSUIPC needs to hook into are not the versions which should be installed with P3D. This shows the results of it attempting to hook into P3D:

 

      484 ------ Setting the hooks and direct calls into the simulator ------
      484 Failed to find CONTROLS timer memory location!
      484 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!
      484     Reason 6: SIM1 base=77C00000
      484     FrictionAddr=77C30108 contains 100FF200
      484     BrakingAddr=77C313C8 contains 8B088B5E
      484 Hook Error: can't find .37 in SIM1.dll
      484 Hook Error: can't find .37 in VISUALFX.dll
I don't understand how your installation can be so different. There are lots of folks using FSUIPC quite happily with P3Dv3. Here's part of a normal FSUIPC loading log:for P3Dv3:
     1857 ------ Setting the hooks and direct calls into the simulator ------
     1857 --- CONTROLS timer memory location obtained ok
     1857 --- SIM1 Frictions access gained and basic values patched
     1857 --- FS Controls Table located ok
     1857 --- Installed Mouse Macro hooks ok.
     1857 --- Wind smoothing fix is installed
     1857 --- SimConnect intercept for texts and menus installed ok
     1857 --- All links okay (except older global weather setting method)
I'll see if I can add some extra logging, before the hooks are attempted, to provide the details of the P3D DLL modules it needs to be correct.
 
Meanwhile, perhaps you could check one or two yourself? Go to the main P3Dv3 fold and find these modules:
 
ACONTAIN.DLL
API.DLL
CONTROLS.DLL
FS-TRAFFIC.DLL
SIM1.DLL
VISUALFX.DLL
WEATHER.DLL
WINDOW.DLL
 
Right-click on each and select Properties. Then "Details". Check that they are all shown with File Version 3.0.10.14945.
 
Pete
 
Posted (edited)

Hi Pete,

 

thanks for replying so quickly. I forgot to mention I changed the product version of prepar3d.exe with resource hacker while trying to get fsinn working. I changed it to 10,0,61637,0, but it didn't work so I changed it back to 1,3,3708,0 which was given to me on the forum thread, but it might well have been incorrect as it was from 2012 and I didn't have a copy of the original. If you have the original product version for v3 it would be good to know.  

 

I checked the .dll's you gave me and they were all fine, showing file Version 3.0.10.14945.

 

thanks for your help,

 

Nick

Edited by nick_m42
Posted

thanks for replying so quickly. I forgot to mention I changed the product version of prepar3d.exe with resource hacker while trying to get fsinn working. I changed it to 10,0,61637,0, but it didn't work so I changed it back to 1,3,3708,0 which was given to me on the forum thread, but it might well have been incorrect as it was from 2012 and I didn't have a copy of the original. If you have the original product version for v3 it would be good to know. 

 

Ouch! This would make FSUIPC act as if the FS version it was running inside was something completely different (P3D version 1.3, which it doesn't even support nowadays!). No wonder it crashed!

 

I checked the .dll's you gave me and they were all fine, showing file Version 3.0.10.14945.

 

Okay, and that's the same version for the proper Prepar3D.exe version 3!

 

In the next update of FSUIPC I'm logging these things. Here's an example for a properly installed and unmolested P3Dv3:

 

********* FSUIPC4, Version 4.948a by Pete Dowson *********
Prepar3D.exe version = 3.0.10.14945

...  (other lines, omitted here)

      795 ------ Module Version Check ------
      795        acontain.dll: 3.0.10.14945
      795             api.dll: 3.0.10.14945
      795        controls.dll: 3.0.10.14945
      795      fs-traffic.dll: 3.0.10.14945
      795             G3D.dll: 3.0.10.14945
      795            sim1.dll: 3.0.10.14945
      795        visualfx.dll: 3.0.10.14945
      795         weather.dll: 3.0.10.14945
      795          window.dll: 3.0.10.14945
      795 ----------------------------------
At least, this way, I'll spot such odd things like yours right away!
 
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.