Jump to content
The simFlight Network Forums

Recommended Posts

Hi,

 

I'm using the latest download of FSUIPC (5.151)  with P3D v4.5 (4.5.11.29713).

For a while I have been having CTD every time I started a flight - menus load okay but as soon as the flight finishes loading I have about 3 seconds before it crashes. In the event viewer, the details are as follows:

 

 

- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2019-05-14T20:21:25.000000000Z" />
  <EventRecordID>14196</EventRecordID>
  <Channel>Application</Channel>
  <Computer>Paul-PC</Computer>
  <Security />
  </System>
- <EventData>
  <Data>Prepar3D.exe</Data>
  <Data>4.5.11.29713</Data>
  <Data>5ca56c53</Data>
  <Data>KERNELBASE.dll</Data>
  <Data>6.1.7601.24417</Data>
  <Data>5caeae18</Data>
  <Data>c0020001</Data>
  <Data>000000000000bdfd</Data>
  <Data>744</Data>
  <Data>01d50a912d1e6cd1</Data>
  <Data>F:\P3Dv4\Prepar3D.exe</Data>
  <Data>C:\Windows\system32\KERNELBASE.dll</Data>
  <Data>d844bc31-7685-11e9-8133-d017c2d495f1</Data>
  </EventData>
  </Event>
 
 

I have fully uninstalled the sim and all addons. Re-installed the sim, it loaded fine and I was able to fly. Installed FSUIPC, registered it, same CTD scenario as before. In the DLL.xml, it is the only addon showing, and setting it to disabled (as below) allows the sim to run. I have tried this multiple times, switching between false and true and every time disabled=false I get the instant CTD.

 

<?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 5</Name>
    <Disabled>True</Disabled>
    <Path>F:\P3Dv4\Modules\FSUIPC5.dll</Path>
   </Launch.Addon>
</SimBase.Document>

 

 

(Edit: having just read the 'please read before posting' sticky, here is the install log:

 

 

Installer for FSUIPC5.DLL version 5.151


Looking in registry for Prepar3D v4 install path:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4
     Parameter"AppPath"
... >>>  OK! FOUND Prepar3D v4!  <<< ...
     AppPath=F:\P3Dv4\
===========================================================

INSTALLATION FOR Prepar3D v4:
AppPath="F:\P3Dv4\"
Checking version of the Prepar3D v4 EXE:
... Version 4.5.11.29713  (Need at least 4.1.0.0)
Checking if there's already a version of FSUIPC5 installed as:
       F:\P3Dv4\Modules\FSUIPC5.DLL
... Version 5.151 found.
F:\P3Dv4\Modules folder already exists.
Okay -- installed FSUIPC5 into "F:\P3Dv4\Modules\FSUIPC5.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Paul\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v4\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\Admin\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Admin\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC5 section.
... FSUIPC5 section already exists but will be replaced.
... FSUIPC5 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\Paul\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Paul\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC5 section.
... FSUIPC5 section already exists but will be replaced.
... FSUIPC5 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.
   Removed "FSUIPC4 Offsets Status.pdf" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC5 User Guide.pdf" okay
   Installed "FSUIPC5 for Advanced Users.pdf" okay
   Installed "The 2016 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 "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "FSUIPC5 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC5 History.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC REGISTER
Providing FSUIPC registration dialogue ...
Registration for FSUIPC5 was successful! (result code 00)

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

 

 

and here is the log:

 

 

 

********* FSUIPC5, Version 5.151 (21st February 2019) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FECD1F0000
Windows 7 Professional 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1)
Prepar3D.exe version = 4.5.11.29713
Reading options from "F:\P3Dv4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="Paul Frimston"
User Addr="p.frimston@btinternet.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 14/05/2019 21:11:16
        0 FLT path = "C:\Users\Paul\Documents\Prepar3D v4 Files\"
        0 Using DialogMode
       16 FS path = "F:\P3Dv4\"
       94 ---------------------- Joystick Device Scan -----------------------
       94 Product= Joystick - HOTAS Warthog
       94    Manufacturer= Thustmaster
       94    Vendor=044F, Product=0402 (Version 1.0)
      109    GUIDs returned for product: VID_044F&PID_0402:
      109       GUID= {F6E1DF00-1439-11E9-8001-444553540000}
      109       Details: Btns=19, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X65535,Y65535,Z0
      109 Product= Throttle - HOTAS Warthog
      109    Manufacturer= Thrustmaster
      109    Vendor=044F, Product=0404 (Version 1.0)
      109    GUIDs returned for product: VID_044F&PID_0404:
      109       GUID= {F6E20610-1439-11E9-8002-444553540000}
      109       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R16383,U1023,V0,X1023,Y1023,Z16383
      125 Product= Saitek Pro Flight Rudder Pedals
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0763 (Version 1.0)
      125    GUIDs returned for product: VID_06A3&PID_0763:
      125       GUID= {F6E25430-1439-11E9-8006-444553540000}
      125       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      125 -------------------------------------------------------------------
      140 Device acquired for use:
      140    Joystick ID = 0 (Registry okay)
      140    0=Joystick - HOTAS Warthog
      140    0.GUID={F6E1DF00-1439-11E9-8001-444553540000}
      140 Device acquired for use:
      140    Joystick ID = 1 (Registry okay)
      140    1=Throttle - HOTAS Warthog
      140    1.GUID={F6E20610-1439-11E9-8002-444553540000}
      140 Device acquired for use:
      140    Joystick ID = 2 (Registry okay)
      140    2=Saitek Pro Flight Rudder Pedals
      140    2.GUID={F6E25430-1439-11E9-8006-444553540000}
      140 -------------------------------------------------------------------
      140 LogOptions=00000000 00000001
      140 -------------------------------------------------------------------
      140 SimConnect_Open succeeded: waiting to check version okay
      140 Opened separate AI Traffic client okay
      140 ### PDKmodeHelper callback registered
      655 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.11.29713 (SimConnect: 4.5.0.0)
      655 Initialising SimConnect data requests now
      655 FSUIPC Menu entry added
      655 ... Using Prepar3D with Academic License
      671 C:\Users\Paul\Documents\Prepar3D v4 Files\Lightning Saints.fxml
   473292 F:\P3Dv4\.air
   545582 F:\P3Dv4\SimObjects\Airplanes\Carenado Commander 114\Car_Commander114.air
   545598 ### The user object is 'AC11 Commander 114 - Orange'
   545598 ### Mode is NORMAL
   545754 ### Mode: PAUSE on
   597952 Loading Complete ...
   597968 ### Mode is NORMAL
   598888 Aircraft loaded: running normally now ...
   598950 User Aircraft ID 1 supplied, now being used
   599387 System time = 14/05/2019 21:21:15, Simulator time = 19:19:10 (18:19Z)
   599387 Aircraft="AC11 Commander 114 - Orange"
   606376 -------------------- Starting everything now ----------------------

 

 

 

I have since started adding in both scenery and aircraft addons one-by-one, the CTD still only occurs when FSUIPC has been enabled,  it is the same reference in the event viewer. Any help would be seriously appreciated at this point in time!

Cheers,

Paul.

Edited by Delta558

Share this post


Link to post
Share on other sites

Hi Paul,

when you 'fully uninstalled the sim', did you also remove 'generated content', as explained in the P3D Download and Installation Directions' (last page)?

I ask as your symptoms sound  like it could be a corrupt weather file, probably the wxstationlist.bin. Usually this would cause P3D to crash as soon as SimConnect is asked to read the weather. Can you check your user Appdata\roaming P3D4 folder, where your PREPAR3D.cfg file is. If the file is there, please delete it - it will be re-generated when you next start P3D. FSUIPC now removes this file automatically when it  shuts down correctly.

If that doesn't sort your problem, it could be one of the other wx files. Please make a safe copy of the .wx files in your P3D files folder, in Documents, then delete one at a time, testing after each. Before that, you could try disabling weather completely by adding the following to the [general] section of the ini file:

NoWeatherAtAll=Yes

Let me know how these tests go.

Regards,

John

 

 

Share this post


Link to post
Share on other sites

Hello John,

Thanks very much for the info - it appears the culprit was the wxstationlist.bin file, your first suggestion. I've gradually been adding back in the addons I'm working on at the moment and there have been no further instances so far, FSUIPC is up and running (and still probably the single most important addon even though it just ticks along in the background!)

 

Best wishes,

Paul.

Share this post


Link to post
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

×

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.