Jump to content
The simFlight Network Forums

Prepar3d v4 crashes when loading a flight


Recommended Posts

That's the thing, I purchased the FSUIPC6 product a few minutes ago (installed and registered as specified the readme file) but it shuts down my prepar3d inmediately, I can't even operate de menu...

 

Please help me.

Edited by malarmao
Link to comment
Share on other sites

11 hours ago, malarmao said:

but it shuts down my prepar3d inmediately, I can't even operate de menu...

This seems to contradict the title of this post ('crashes when loading flight') - does it crash when you start P3D, or when you load a flight?
Do you have a crash log in the  windows event viewer? If so, can you please show me that. Also, you should always attach your FSUIPC6.log file when you have such issues.

Having said that, P3D crashes on start-up are usually due to a corrupt weather file, usually the wxstationlist.bin file or your start-up scenario *.wx file.  If you want to check whether or not it is down to corrupted weather files you can try adding 

NoWeatherAtAll=Yes

to the [General] section of the INI file. If it is a weather file, you should first try deleting the wxstationlist.bin file from your AppData\Roaming\Lockheed Martin\Prepar3D v4 folder (it will be regenerated when you run P3D). If you still have issues, try removing the  *.wx files in your  Prepar3D documents folder (the folder where your saved flights are).

If its not a weather issue, please show me your FSUIPC6.log file and check the event viewer for a crash event and also show me that.

John
 

Link to comment
Share on other sites

Hi John,

Thank you very much for your quick reply.

I will try to explain it properly:

Right after installing and registering I started Prepar3d v4 and seemed to work normally, It loaded the Startup and I select my default flight (running Aerosoft a320 at LFPO Justsim), the aircraft and the scenery loaded totally and suddenly, the frame counter stops and Prepar3d shut down.

I am not an expert in software but my default flight is loaded without any weather info (clear skies), I use P3DWX freeware that I start before preparing the aircraft, I mean that prepar3d is shutting down before connecting the weather app.

Should I tried what you explained after this info?

Thanks!

 

BR,

 

Rafa

 

 

 

 

Edited by malarmao
Link to comment
Share on other sites

51 minutes ago, malarmao said:

I am not an expert in software but my default flight is loaded without any weather info (clear skies)

The only way to stop weather info being loaded is to delete all the .wx files beforehand. The .wx files contain all the world's weather and accompany every saved flight including the default one.

If you've never saved a flight then the default .wx file is probably ok, so the most likely candidate for corruption is the wxstationlist.bin file. 

53 minutes ago, malarmao said:

I use P3DWX freeware that I start before preparing the aircraft, I mean that prepar3d is shutting down before connecting the weather app.

Most of the weather crash issues we've had reported do come from such add-ons. It won't be when it attached this time, but what it did the last time you ran it. If you'd like to supply your wxstationlist.bin file (ZIP it first) then we can check it, but really your best bet id to delete it before running P3D again.  It will be replaced automatically by P3D. 

Find the wxstationlist.bin file in your C:\Users\<your name>\Appdata\Roaming\Lockheed Martin\Prepar3D v4 folder.

58 minutes ago, malarmao said:

Should I tried what you explained after this info?

Yes, most certainly!

Pete

 

Link to comment
Share on other sites

Hi again,

 

I delted the file but it happens again. Here is my log file...

 

 

 

********* FSUIPC6, Version 6.0.11 (26th November 2020) by Pete & John Dowson *********
Prepar3D.exe version = 4.5.11.29713
Running inside Prepar3D v4
Module base=7FFA5B120000
Windows 10 Home 64 Bit reported as Build 19041, Release ID: 2004 (OS 10.0)
Reading options from "C:\Users\Usuario\Documents\Prepar3D v4 Add-ons\FSUIPC6\FSUIPC6.ini"
Checking the Registrations now ...
User Name="personal details hidden"
User Addr="personal details hidden"
FSUIPC6 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 15/12/2020 00:00:03
        0 FLT path = "C:\Users\Usuario\OneDrive\Documentos\Prepar3D v4 Files\"
        0 Using DialogMode
       16 FS path = "C:\Program Files\Lockheed Martin\Prepar3D v4\"
       16 ---------------------- Joystick Device Scan -----------------------
       16 Product= T.A320 Pilot
       16    Manufacturer= Thrustmaster
       16    Serial Number= 1
       16    Vendor=044F, Product=0405 (Version 2.0)
       16    GUIDs returned for product: VID_044F&PID_0405:
       16       GUID= {306C5E70-1A01-11EB-8001-444553540000}
       16       Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255
       16 Product= TCA Q-Eng 1&2
       16    Manufacturer= Thrustmaster
       16    Serial Number= 00000000001A
       16    Vendor=044F, Product=0407 (Version 2.0)
       16    GUIDs returned for product: VID_044F&PID_0407:
       16       GUID= {306C8580-1A01-11EB-8002-444553540000}
       16       Details: Btns=31, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R65535,U65535,V65535,X65535,Y65535,Z65535
       16 -------------------------------------------------------------------
       31 Device acquired for use:
       31    Joystick ID = 1 (Registry okay)
       31    1=T.A320 Pilot
       31    1.GUID={306C5E70-1A01-11EB-8001-444553540000}
       31 Device acquired for use:
       31    Joystick ID = 0 (Registry okay)
       31    0=TCA Q-Eng 1&2
       31    0.GUID={306C8580-1A01-11EB-8002-444553540000}
       31 -------------------------------------------------------------------
       47 Controllers are set to ON, using RawInput within P3D
       47 LogOptions=00000000 00000001
       47 -------------------------------------------------------------------
       63 SimConnect_Open succeeded: waiting to check version okay
       63 Opened separate AI Traffic client okay
   125172 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.11.29713 (SimConnect: 4.5.0.0)
   125172 Initialising SimConnect data requests now
   125172 FSUIPC Menu entry added
   125172 ... Using Prepar3D with Professional Plus License
   125188 C:\Users\Usuario\OneDrive\Documentos\Prepar3D v4 Files\Defecto.fxml
   125188 C:\Users\Usuario\Documents\Aerosoft\Aerosoft A320-A321 Professional\SimObjects\Airplanes\Aerosoft A320 IAE Professional\A320.air
   165094 ### The user object is 'Aerosoft A320 professional VUELING EC-LUO'
   165094 ### Mode is NORMAL
   165438 ### Mode: PAUSE on
   183719 Loading Complete ...
   183735 ### Mode is NORMAL
   184328 Aircraft loaded: running normally now ...
   184360 User Aircraft ID 2 supplied, now being used
   184531 System time = 15/12/2020 00:03:07, Simulator time = 00:02:09 (05:02Z)
   184531 Aircraft="Aerosoft A320 professional VUELING EC-LUO"
   191531 -------------------- Starting everything now ----------------------

 

Edited by malarmao
Link to comment
Share on other sites

You are not loading the default P3D flight, but a previously saved one, which you have presumably marked for default loading:

C:\Users\Usuario\OneDrive\Documentos\Prepar3D v4 Files\Defecto.fxml

This means a possibly corrupt .wx file is being loaded. You should have deleted all the .wx files in that folder too. 

But for the proof that it is a weather corruption you should really have followed John's instructions. Specifically this:

7 hours ago, John Dowson said:

If you want to check whether or not it is down to corrupted weather files you can try adding 

NoWeatherAtAll=Yes

to the [General] section of the INI file.

Also, whilst you posted the .Log file (thank you) which also points to a weather file problem, you needed to also post the details of the crash from the Event Viewer, as John also requested.

Incidentally, we have had a number of weather file related crash reports and the freeware P3DWX program seems to be a common factor. You might like to view the solution in this thread:

Seems that he found that starting P3DWX before P3D solved the problem.

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.