Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Every time I install FSUIPC Fatal error occurs. It's fine on the start up but as soon  as I choose an aircraft and load it up a fatar error occurs and I get sent back to the desktop. I have had FSUIPC before but now it doesn't work for some reason. I have also reinstalled FSX, and FSUIPC but nothing works. I can't upload what the config said though

 

 

Posted

Every time I install FSUIPC Fatal error occurs. It's fine on the start up but as soon  as I choose an aircraft and load it up a fatar error occurs and I get sent back to the desktop. I have had FSUIPC before but now it doesn't work for some reason. I have also reinstalled FSX, and FSUIPC but nothing works. I can't upload what the config said though

 

I'm afraid I need more information.

 

Don't try "uploading" stuff here. All the information I'd need is textual -- just paste it into a message.

 

Info needed:

 

* Windows error information for the "fatal error" from the Windows event viewer.

* FSUIPC4 log, as far as it went (from the FS Modules folder

* List of other add-ons being used.

 

Pete

Posted
 

 

I don't have a log file. When I start fsx up, I have about 5 seconds before a fatal error occurs. 

The only addons I have are GSX and the IFLY 737.

I have included the log I get on install. Not sure if this will help though.

Thanks!

 

 

Installer for FSUIPC4.DLL version 4.929

 

 

Looking in registry for FSX install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

     Parameter"SetupPath"

... >>>  OK! FOUND FSX!  <<< ...

Looking in registry for ESP install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

     Parameter"SetupPath"

Not there, so looking in:

     HKEY_CURRENT_USER\ESP

     Parameter"AppPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

     Parameter"SetupPath"

Not there, so looking in:

     HKEY_CURRENT_USER\Prepar3D

     Parameter"AppPath"

... NOT found! ...

Looking in registry for Prepar3D v2 install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2

     Parameter"SetupPath"

Not there, so looking in:

     HKEY_CURRENT_USER\Prepar3D v2

     Parameter"AppPath"

... NOT found! ...

===========================================================

 

INSTALLATION FOR FSX:

SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of the FSX EXE:

... Version 10.0.61637.0  (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

    Found SimConnect build 60905 (Original)

    Found SimConnect build 61242 (SP1 May07)

    Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

       C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... No previous valid version found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\Patene\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\Administrator\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\All Users\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\AppData\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Brenda\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Kids\AppData\Roaming"

Found FSX.CFG in "C:\Users\Kids\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

     (for FSUIPC4, without Loader)

... FSUIPC4 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\Patene\AppData\Roaming"

Found FSX.CFG in "C:\Users\Patene\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

     (for FSUIPC4, without Loader)

... FSUIPC4 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 FSX.CFG there

"Modules\FSUIPC Documents" folder created okay!

Now installing additional files into the "Modules\FSUIPC Documents" folder:

   Installed "FSUIPC4 User Guide.pdf" okay

   Installed "FSUIPC4 for Advanced Users.pdf" okay

   Installed "FSUIPC4 History.pdf" okay

   Installed "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 "Lua Plugins for VRInsight Devices.pdf" okay

   Installed "LuaFileSystem.pdf" okay

   Installed "Example LUA plugins.zip" okay

   Installed "Offset Mapping for PMDG 737NGX.pdf" okay

   Installed "FSUIPC4 Offsets Status.pdf" okay

Posted

I don't have a log file. When I start fsx up, I have about 5 seconds before a fatal error occurs. 

 

If FSUIPC is not producing a run-time log, then it is not being run as that is the first thing it does. Earlier you said

 

 It's fine on the start up but as soon  as I choose an aircraft and load it up a fatar error occurs

 

 

which is completely different to what you say now. Which is it?

 

Pete

Posted

What happens is when I start FSX With FSUIPC installed, the start up works fine, I get to choose an aircraft, load up and everything. But once I load up and the aircraft is on the ground, I get the fatal error. I hope this clears up some confusion.

Thanks!

Posted

What happens is when I start FSX With FSUIPC installed, the start up works fine, I get to choose an aircraft, load up and everything. But once I load up and the aircraft is on the ground, I get the fatal error. I hope this clears up some confusion.

 

Not really, because you contradicted yourself completely earlier -- you said no log is produced because "when I start fsx up, I have about 5 seconds before a fatal error occurs". Obviously you cannot have FS loaded and choose an aircraft in that time 

 

So, I repeat. If FS is running with FSUIPC installed then there will be a run-time log file. It is that I need to see. I cannot help you otherwise. It is impossible to help anyone with zero information, surely you can see that?

 

You also need to find the data about this fatal error from the Windows event viewer. That tells me where the error occurs and what sort of error it is. I did ask for this information 4 days ago!

 

Pete

Posted

Sorry for the confusion. Here is what is happening. I get fsx loaded up and I choose the aircraft, load it and then it crashes.

 

Here is the log file.

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: weather.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
Fault offset: 0x0001542f
Faulting process id: 0x17a4
Faulting application start time: 0x01cf45fe2afce19a
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll
Report Id: c433b299-b1f3-11e3-bfb8-8fcd07bee207
 
 
 
 
 
And here is the FSX Log 
********* FSUIPC4, Version 4.929 by Pete Dowson *********
Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"
Running inside FSX on Windows 7
Module base=5A530000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
     1436 System time = 22/03/2014 14:59:44
     1436 FLT path = "C:\Users\Patene\Documents\Flight Simulator X Files\"
     1529 Trying to connect to SimConnect Acc/SP2 Oct07 ...
     1545 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"
     3495 LogOptions=00000000 00000001
     3495 SIM1 Frictions access gained
     3495 Wind smoothing fix is fully installed
     3495 G3D.DLL fix attempt installed ok
     3495 SimConnect_Open succeeded: waiting to check version okay
     3495 Trying to use SimConnect Acc/SP2 Oct07
    11903 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
    11903 Initialising SimConnect data requests now
    11903 FSUIPC Menu entry added
    12262 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT
    12262 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    37425 System time = 22/03/2014 15:00:20
    37425 *** FSUIPC log file being closed
G3D fix: Passes 1097, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
Posted

 

Sorry for the confusion. Here is what is happening. I get fsx loaded up and I choose the aircraft, load it and then it crashes.

 

Here is the log file.

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: weather.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
 

 

There you go. The weather file is corrupt. FSUIPC isn't causing the crash, it's just reading the weather

 

Cheers!

Luke

Posted

Sorry for the confusion. Here is what is happening. I get fsx loaded up and I choose the aircraft, load it and then it crashes.

 

Actually it's the Windows crash report, and as Luke says, it shows the culprit is WEATHER.DLL, not FSUIPC4.DLL. Look again:

 

 

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

 

Faulting module name: weather.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
Fault offset: 0x0001542f
Faulting process id: 0x17a4
Faulting application start time: 0x01cf45fe2afce19a
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll
Report Id: c433b299-b1f3-11e3-bfb8-8fcd07bee207
 
The other log you supplied is NOT the "FSX.LOG" but an FSUIP4.LOG, and it actually shows a completely successful session and a normal close as you can surely see:
 
    37425 *** FSUIPC log file being closed

G3D fix: Passes 1097, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 4 Allocs, 4 Freed

********* FSUIPC Log file closed ***********

 

 

The crash is because SimConnect is not resilient to corrupted weather data, and this makes itself felt when FSUIPC is running because it is reading the weather data from Simconnect at regular intervals so it can feed it to client applications.

 

I see you aren't actually using FSUIPC4 for anything yourself -- it isn't registered! So either remove it so it doesn't read weather, or change the WeatherReadFactor in its INI file to zero so it doesn't read weather, or try fixing your weather system. I suspect you have a corrupt file -- maybe wxstationlist.bin in the same folder as your FSX.CFG, or more likely one of the .WX files in your documents\Flight Simulator X files folder. Try deleting them all. 

 

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.