Jump to content
The simFlight Network Forums

Recommended Posts

Posted (edited)

Hi,

I was using FSUIPC for at least a few months now, and I never experienced any issues with it, however today, out of the blue, I've been getting CTD's as soon as i load into a flight in P3D. If I remove all the FSUIPC files from the modules folder in Prepar3d it works, so I'm not sure where I'm going wrong. 

If anyone wants any logs, or event viewer reports, then let me know.

Regards,

Hubert

Edited by Hubert Gaszewski
Posted

Hi,

as always, and described top of the forum, the actual FSUIPC4.log file is minimum needed. Just copy its FULL content and paste it into your message here. Same for the Event Viewer report.

Pete is away for couple days but just in case.

Btw- out of the blue, no changes to P3D at all, nothing will change. Just check what did you maybe change, added like hardware, installed or updated last since.

Thomas

Posted

Okay, sorry about that.

Here's my log:

Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 3.3.5.17625
Running inside Prepar3D v3 on Windows 10
Module base=24860000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
        0 System time = 19/03/2017 18:10:24
        0 FLT path = "C:\Users\Hubert\Documents\Prepar3D v3 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 3.3.5.17625
        0             api.dll: 3.3.3.17556
        0        controls.dll: 3.3.5.17625
        0      fs-traffic.dll: 3.3.5.17625
        0             G3D.dll: 3.3.5.17625
        0        language.dll: 3.3.5.17625
        0            sim1.dll: 3.3.5.17625
        0        visualfx.dll: 3.3.5.17625
        0         weather.dll: 3.3.5.17625
        0          window.dll: 3.3.5.17625
        0 ----------------------------------
        0 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D3.dll
        0 Found it: trying to connect
        0 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\"
       15 LogOptions=00000000 00000001
       15 -------------------------------------------------------------------
       15 ------ Setting the hooks and direct calls into the simulator ------
       15 --- CONTROLS timer memory location obtained ok
       15 --- SIM1 Frictions access gained
       15 --- FS Controls Table located ok
       15 --- Installed Mouse Macro hooks ok.
       15 --- Wind smoothing fix is installed
       15 --- SimConnect intercept for texts and menus option is off
       15 --- All links okay (except older global weather setting method)
       15 -------------------------------------------------------------------
       15 SimConnect_Open succeeded: waiting to check version okay
       15 Trying to use SimConnect Prepar3D
       15 Opened separate AI Traffic client okay
    29000 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.3.3.3 (SimConnect: 3.3.0.0)
    29000 Initialising SimConnect data requests now
    29000 FSUIPC Menu entry added
    29015 C:\Users\Hubert\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
    29015 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    54046 Weather Mode now = Global
    56031 C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air
    98687 Aircraft loaded: running normally now ...
    98687 User Aircraft ID 4 supplied, now being used
    99265 System time = 19/03/2017 18:12:04, Simulator time = 18:11:17 (17:11Z)
   117500 Starting everything now ...
   117671 Advanced Weather Interface Enabled
 

As for the changes, I did try to load up an autosave, and then the issues began. I also saved the panel state in the PMDG NGX just in-case the autosave failed but i doubt that had anything to do with it.

Thanks

Hubert

Posted

Hi,

the first line of the Log file is missing, as I said please copy the FULL content.

It might be that the weather file is corrupt (.wx) and that might have messed up the wxstationlist.bin file, located where you find the Prepar3D.cfg file. Delete both, p3d will create a new wxstationlist.bin file automatically and the .wx is created new when you save that loaded flight again.

Thomas

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.