Jump to content
The simFlight Network Forums

Recommended Posts

Posted (edited)

Hello!

When I start P3D i am able to load into the aircraft, but after a few seconds it crashes to desktop without any warnings or error messages. I looked at Event viewer and found that FSUIPC is crashing the sim. This is what the event viewer says:

Faulting application name: Prepar3D.exe, version: 5.2.22.27615, time stamp: 0x60db69bf
Faulting module name: FSUIPC6.dll, version: 6.1.0.5, time stamp: 0x613a4dfa
Exception code: 0xc0000409
Fault offset: 0x00000000000ebad4
Faulting process id: 0x5330
Faulting application start time: 0x01d7cff1edf656bb
Faulting application path: G:\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\Users\Klaus\Documents\Prepar3D v5 Add-ons\FSUIPC6\FSUIPC6.dll
Report Id: b0111cf0-8c93-4b7f-9a7b-262540866702
Faulting package full name: 
Faulting package-relative application ID: 

In the FAQ I found the part about the wxstations.bin file - I tried it with the "NoWeatherAtAll=Yes" in the [General] section of the FSUIPC4.INI file - without success. (Removed after trying)

I found that I had no wxstations.bin file at all in the "APPDATA/ROAMING/LOCKHEED MARTIN/PREPAR3D" folder. I never deleted anything from there. Also after restarting the file was not created. I tried to copy it over from the "LOCKHEED MARTIN/PREPAR3D/WEATHER" folder - without success.

What can I do now?

Thank you very much!

EDIT - I attached the log and ini file.

FSUIPC6.log FSUIPC6.ini

Edited by Rhinozherous
Posted
9 minutes ago, Rhinozherous said:

I found that I had no wxstations.bin file at all in the "APPDATA/ROAMING/LOCKHEED MARTIN/PREPAR3D" folder

I don't think the file is needed/copied there any more in 5.2 - I do not have one there...

10 minutes ago, Rhinozherous said:

I tried to copy it over from the "LOCKHEED MARTIN/PREPAR3D/WEATHER" folder - without success.

No need to do this.

10 minutes ago, Rhinozherous said:

What can I do now?

Can you show me/attach your FSUIPC6.log and FSUIPC6.ini files and I will take a look.

John

Posted
1 minute ago, John Dowson said:

I don't think the file is needed/copied there any more in 5.2 - I do not have one there...

No need to do this.

Can you show me/attach your FSUIPC6.log and FSUIPC6.ini files and I will take a look.

John

I already found the culprit - in the FSUIPC ini i recently installed the "Pilot monitoring callout" addon for the FsLabs airbus and forgot about it... it requires to add this line in the FSUIPC6.ini:

 [Auto] ;if section not exists, create yourself
    1=Lua PMCO ;add this to the list of your [Auto] section, check numbering

In the ini file in my first post (I attached them via Edit earlier) you can see it at the end of the code. After removing this all worked normal again!

Thank you for the very fast response! 

  • Rhinozherous changed the title to [SOLVED] FSUIPC6 crashing P3D v5 - not wxstations related
Posted
9 minutes ago, Rhinozherous said:

I already found the culprit - in the FSUIPC ini i recently installed the "Pilot monitoring callout" addon for the FsLabs airbus and forgot about it... it requires to add this line in the FSUIPC6.ini:

 [Auto] ;if section not exists, create yourself
    1=Lua PMCO ;add this to the list of your [Auto] section, check numbering

In the ini file in my first post (I attached them via Edit earlier) you can see it at the end of the code. After removing this all worked normal again!

Thank you for the very fast response! 

Ok. I don't think comments are allowed in an auto line, but I am surprised that would crash FSUIPC....

 Try just:
    [Auto]
    1=Lua PMCO

John

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.