Jump to content
The simFlight Network Forums

FSX Crashing to Desktop with FSUIPC


Recommended Posts

Hello, its my first post here.
When I start my FSX, it crashes, but when I set FSUIPC4.dll to "true" in dll.xml, my game works fine.
What is causing this error?

Log:

********* FSUIPC4, Version 4.948 by Pete Dowson *********
Reading options from "D:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 8.0
Module base=576B0000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
      484 System time = 08/12/2015 13:45:15
      484 FLT path = "C:\Users\Umar Ali\Documents\Flight Simulator X Files\"
      516 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      594 FS path = "D:\FSX\"
      594 LogOptions=00000000 00000001
      594 -------------------------------------------------------------------
      594 ------ Setting the hooks and direct calls into the simulator ------
      594 --- CONTROLS timer memory location obtained ok
      594 --- SIM1 Frictions access gained
      594 --- FS Controls Table located ok
      594 --- Installed Mouse Macro hooks ok.
      594 --- Wind smoothing fix is fully installed
      594 --- G3D.DLL fix attempt installed ok
      594 --- All links checked okay
      594 -------------------------------------------------------------------
      594 SimConnect_Open succeeded: waiting to check version okay
      594 Trying to use SimConnect Acc/SP2 Oct07
     3438 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     3438 Initialising SimConnect data requests now
     3438 FSUIPC Menu entry added
     3453 D:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     3453 D:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    29953 System time = 08/12/2015 13:45:44, Simulator time = 13:45:18 (21:45Z)
    30922 Starting everything now ...
    35281 System time = 08/12/2015 13:45:50, Simulator time = 13:45:20 (21:45Z)
    35281 *** FSUIPC log file being closed
Minimum frame rate was 21.6 fps, Maximum was 21.6 fps
Minimum available memory recorded was 32768Mb
Average frame rate for running time of 3 secs = 18.9 fps
G3D fix: Passes 7846, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
Ini file:
[General]
UpdatedByVersion=4948
History=GJG62LGWVO4TPQQ7IKEZ6
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
OOMcheck=Yes
OOMcheckInterval=10
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0
SimConnectUsed=10.0.61259.0
Console=No
 
[WideServer]
WideFSenabled=Yes


There is no event in event viewer about FSX.

 

Link to comment
Share on other sites

When I start my FSX, it crashes, but when I set FSUIPC4.dll to "true" in dll.xml, my game works fine.

What is causing this error?

Log

 

The log shows a normal completion to the FS session.  Look:

 

    29953 System time = 08/12/2015 13:45:44, Simulator time = 13:45:18 (21:45Z)
    30922 Starting everything now ...
    35281 System time = 08/12/2015 13:45:50, Simulator time = 13:45:20 (21:45Z)
    35281 *** FSUIPC log file being closed
Minimum frame rate was 21.6 fps, Maximum was 21.6 fps
Minimum available memory recorded was 32768Mb
Average frame rate for running time of 3 secs = 18.9 fps
G3D fix: Passes 7846, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
 
Something you have is closing FS as soon as it runs. It isn't a crash but a normal termination. 
 
Your INI file is incomplete. CAn you post the whole thing not a fragment, please?
 
Pete
Link to comment
Share on other sites

Yeah, I think my FSX is terminated by FSUIPC 4, when I delete FSUIPC or set it to true in dll.xml, my FSX works fine perfectly.

.INI file is complete btw, just recreated it.

 

Okay. So you have no joysticks being recognised and nothing being tun by Lua or Auto sections. But, you have WideFS enabled. Are you aware of that? Maybe it's a Network problem. Try changing the WideFSenabled line to say 'No'.

 

If that does nothing we'll need to add some logging lines to get more data. FSUIPC certainly cannot cause FSX to terminate normally without being told somehow.

 

My FSX used to work fine few days ago with FSUIPC :( I was on cruise and it crashed to desktop, its happening since then.

 

Something might have got corrupted in FSX. Maybe you need to try repairing it or reinstalling.

 

Pete

Link to comment
Share on other sites

Yup. It crashes, I set WideFSEnabled to NO

 

It isn't crashing. it is terminating normally. I already told you that!

 

Something is telling FS to terminate as soon as FS is ready to service applications. So the first thing to do is list all the add-ons you have installed.

 

Then enable some logging. Add these lines to the [General] section of the FSUIPC4.INI file:

 

LogEvents=Yes

DebugLua=Yes

LogExtras=Yes

LogWrites=Yes

 

and run it again.

 

Can you help me?

 

Er .... What do you think I'm trying to do?

 

And you can't expect a reply within minutes every time!!! I had to go to the Doctors, soon I have to go out again. It may sometimes be minutes, sometimes hours, rarely a day or two.

 

Pete

Link to comment
Share on other sites

ENB

MOGWAI SHADES
EZDOK
FSWATERCONFIG
HDE V2
PMDG 737
IVAO MTL
FSXWX (now doesnt work, becuase it needs FSUIPC)

 

Of those, is FSXWX the only user of FSUIPC?  What is HDE V2?

 

When is FSXWX started?

 

Are you going to do the log and show it to me as I suggested?

 

Pete

Link to comment
Share on other sites

http://www.plane-pics.de/fsxwx/instructions.htmCheck this link. I got wxmapping here, which was corrupt and was causing FSX to terminate

 

Ah, the wxmapping.bin file. Yes, that can get corrupted if FSX crashes, and like corrupt WX files, will cause Simconnect to crash FSX when FSUIPC asks for weather data.

 

I thought you meant a program called wxmapping.

 

FSUIPC doesn't read any weather files directly -- it just uses standard SimConnect weather requests. The trouble is both wxmapping.bin and WX files (those with flight files) are binary files with no checks whatsoever, and SimConnect doesn't check them. Corruption causes crashes. It often only crashes if a Registered FSUIPC is running, because it is reading weather data as soon as FS is "ready to fly".

 

Pete

Link to comment
Share on other sites

  • 6 years later...
2 hours ago, trisho0 said:

How to do or where to add this instruction?

Are you even using WideFS? If so, I doubt very much this has do do with FSX crashing...

2 hours ago, trisho0 said:

I have the same Fsuipc behavior the FSX does CTD if load the sim with Fsuipc.

This is usually due to a corrupt weather file.  Try disabling weather by setting 

NoWeatherAtAll=Yes

to the [General] section of your FSUIPC4.INI file. If this solves it then either your wxstationlist.bin file is corrupt, or one of the .wx files saved with scenarios is bad.
To resolve this, delete all of the .WX files from your FS Documents folder (where your flights are stored), and the file "wxstationlist.bin" in your <user>\AppData\Roaming folder for FSX.

John

Link to comment
Share on other sites

Dear John, thanks for helping me on this "nightmare". FSUIPC has been "off" for almost over than a year due to CTD from unknown reason.

NoWeatherAtAll=Yes instruction didn't help.

I will explain here, I launch FSX SP2 and it pops up the typical Microsoft Simulator X screen and then it shows "Free Flight" page you know the default.

Next, I don't touch anything just leaving such screen opened. Suddenly, FSX closes with no error message at all.

Is it possible to make a different FSUIPC to handle the sim in a different way? I mean, it could be isolating some instructions via INI file to prevent CTD.

I noticed from INI file Fsuipc detects Windows 10 instead of Windows 11. This detection I don't think is the issue because the problem started with Windows 10 anyway.

I have to mention a reinstallation of FSX didn't help.

Regards,

Patricio Valdes

FSUIPC4.ini FSUIPC4.log FSUIPC4_prev.log

Link to comment
Share on other sites

2 hours ago, trisho0 said:

Is it possible to make a different FSUIPC to handle the sim in a different way?

No. FSUIPC4 has been closed for development for several years...

2 hours ago, trisho0 said:

I mean, it could be isolating some instructions via INI file to prevent CTD.

There is nothing in the ini file that would cause a CTD.

2 hours ago, trisho0 said:

I noticed from INI file Fsuipc detects Windows 10 instead of Windows 11.

This is normal. Windows 11 is still windows 10 in the windows registry, the source of this information.

2 hours ago, trisho0 said:

I launch FSX SP2

Are you sure you have installed SP1 and SP2 when you re-installed FSX? Your version is reported as:
      fsx.exe version = 10.0.61637.0
However, I see:
    fsx.exe version = 10.0.62615.0
?

Can you run FSX without FSUIPC? If you haven't tried that, please do - just temporarily rename your FSUIPC4.dll to FSUIPC4.dll.unused (for example) so that it is not loaded.

If it runs without FSUIPC, and you are running with SP1 and SP2 (the version numbers may be different if not using steam, I'm not sure...) then we can add more logging to try and get more info...

John

Link to comment
Share on other sites

I am using FSX without FSUIPC for over than a year as posted here because of the problem in question.

Yes, I can run FSX without any issues with FSUIPC "Off".

Attached is FSX "About" showing the sim version. I remember, installed the FSX SP1 first which is the original and then installed the SP2 which is the Acceleration Pack.

The FSX is not the Steam but the first original. I had been using FSX since built and it was working with FSUIPC just fine until it started a year ago with FSX CTD.

I know it has to be a fix but no ideas.

Regards,

Patricio Valdes

FSX About.jpg

Link to comment
Share on other sites

12 hours ago, trisho0 said:

I remember, installed the FSX SP1 first which is the original and then installed the SP2 which is the Acceleration Pack.

I think SP2 and the Acceleration pack are different, but the Acceleration pack includes SP2 (i.e. you don't need to install SP2 if you install the Acceleration pack).
What SDKs did you install? You also need to install (in the following order):
   - FSX SDK 1
  - FSX SDK SP1a
  - then the FSX SDK XPack off of FSX Acceleration.

12 hours ago, trisho0 said:

it was working with FSUIPC just fine until it started a year ago with FSX CTD.

What changed from working fine to the CTDs started? How come you have only just reported if this started a year ago?

John

Link to comment
Share on other sites

Ok. forget the above...I just found your previous post with the same problem: 

 

You should have continued in that topic rather than starting a new one....

What vc++ redistributables do you have installed? Maybe try uninstalling any of the following if installed: 2015, 2017, 2019 & 2022. Then install the latest combined package from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170.

John

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.