Jump to content
The simFlight Network Forums

fsuipc auto closes out of FSX


Recommended Posts

Hi,

I used to use fsuipc years ago with fsx. Now I just received new heavy duty "cyberpower i220" gamer desktop with 6850 graphics. all has worked well with fsx until today. The fsx works, but when i installed 4.7 version of fsuipc, and then go into fsx, after loading scenery, traffic etc to 100%, instead of the game being on the screen, it just autocloses the program fsx. I have tried everything (tho I am not a computer guy by any stretch). I did get a error from my windows 7 "Program Compatabilty Assistant" though saying "This program might not have installed correctly", even though it got to the registration page (where I clicked cancel). I dont mine paying for the registration, if that's the case. but it did work yesterday. I am using AIRSOURCE . but I tried uninstalling fsx, and reinstalling, tried uninstall, and reinstall fsuipc, and fsx just does not want to work when I have fsuipc running. It did work yesterday briefly.

this below, is copied and pasted from my computer file of installing fsuipc: please help.

thx

Mike

"""""Installer for FSUIPC4.DLL version 4.758

Looking in registry for FSX install path:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"AppPath"

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

Looking in registry for ESP install path:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

Not there, so looking in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D

Parameter"AppPath"

Not there, so looking in:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

Parameter"SetupPath"

... NOT found! ...

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

INSTALLATION FOR FSX:

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

Checking version of FSX.EXE:

... Version 10.0.60905.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

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

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

... Version 4.758 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\Mike\AppData\Roaming"

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

Looking in "C:\Users\All Users\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\Mike\AppData\Roaming"

Found FSX.CFG in "C:\Users\Mike\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.

... 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 already exists.

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 controls.pdf" okay

Installed "GlobalSign Root.exe" 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

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed.

*************** End of Install Log ********

Link to comment
Share on other sites

I used to use fsuipc years ago with fsx. Now I just received new heavy duty "cyberpower i220" gamer desktop with 6850 graphics. all has worked well with fsx until today. The fsx works, but when i installed 4.7 version of fsuipc, and then go into fsx, after loading scenery, traffic etc to 100%, instead of the game being on the screen, it just autocloses the program fsx.

You supplied the Install log, but isn't there a Run-Time log (FSUIPC4.LOG)? I'd need to see that.

If FSX is loading to the 100% mark it sounds like a corrupted weather file (WX file in your Documents Flight Simulator X Files folder), or maybe the wxstationlist.bin file in the same folder as your FSX.CFG (i.e. in C:\Users\Mike\AppData\Roaming\Microsoft\FSX). Try deleting that and rpelacing it with the default one in the FSX Weather folder.

Otherwise I need to see the FSUIPC4 log please.

Incidentally, the Install log shows this:

Checking version of FSX.EXE:

... Version 10.0.60905.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

which means you are using the original buggy version of FSX. I would strongly advise you to download and install the SP1 and SP2 updates. There were lots of problems in the original release which are fixed by these updates.

Regards

Pete

Link to comment
Share on other sites

Pete,

thanks for quick response.... I wasted 8 hours messing with this. Come to find out, had I read your forum posts prior to, I would have saved alot of stress. I did install service pack 1, then sp2, and that seems to have fixed the problem. Though I've only quickly checked it, but I loaded a flight, including flight plan, and airsource flight, and all seemed hunky dorey. Hopefully that was the fix. again, thanks and sorry for wasting your time. It looks like you are busy here.

again, thanks buddy.

Mike

Link to comment
Share on other sites

actually, I ran one flight with myaas, and sp1 and 2 installed. Everything was perfect. Then on the return flight I was 70 minutes into an eighty minute flight when an error msg came on and said fsuipc has stopped working and caused a fatal error in fsx. The game didnt save my flight like fsuipc should, and when I reloaded the game fsx, it was back at the original screen Friday harbor with the Trike craft flying, and also the joystick buttons I programmed into it, all had to be redone, as they went back to default as well.

please help.

thx

Mike

Link to comment
Share on other sites

Pete, I didnt see a fsuipc4 LOG file

so I found 2 others I could open with notepad. They are 1:

TCASrange=40

AxisCalibration=No

DirectAxesToCalibs=No

ShowMultilineWindow=Yes

SuppressSingleline=No

SuppressMultilineFS=No

AxisIntercepts=No

DontResetAxes=No

InitDelay=0

GetNearestAirports=Yes

WeatherReadFactor=2

WeatherRewriteSeconds=1

CustomWeatherModify=No

SimConnectStallTime=1

LuaRerunDelay=66

FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0

SimConnectUsed=10.0.61259.0

Console=No

[JoyNames]

AutoAssignLetters=No

0=Saitek ST290 Pro

0.GUID={EAD8ACC0-41FF-11E1-8001-444553540000}

[WideServer]

WideFSenabled=Yes

[sounds]

Path=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\

Device1=Primary Sound Driver

Device2=Speakers (Realtek High Definition Audio)

Device3=Realtek Digital Output (Realtek High Definition Audio)

Device4=Realtek Digital Output(Optical) (Realtek High Definition Audio)

-----------------------------------------------------------------------------------------------------------------------------------------------

AND ACTUALY THIS MAY BE THE ONE OF INTEREST TO YOU

********* FSUIPC4, Version 4.758 by Pete Dowson *********

User Name="Mike McCarthy"

User Addr="mmccarthy53@hotmail.com"

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7

Module base=61000000

32 System time = 25/01/2012 22:41:48

32 FLT path = "C:\Users\Mike\Documents\Flight Simulator X Files\"

63 Trying to connect to SimConnect Acc/SP2 Oct07 ...

63 FS path = "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

359 LogOptions=00000000 00000001

359 Wind smoothing fix is fully installed

359 G3D.DLL fix attempt installed ok

359 SimConnect_Open succeeded: waiting to check version okay

359 Trying to use SimConnect Acc/SP2 Oct07

1623 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

1623 Initialising SimConnect data requests now

1623 FSUIPC Menu entry added

1638 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

1638 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

21997 System time = 25/01/2012 22:42:09

21997 *** FSUIPC log file being closed

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

Memory managed: 2 Allocs, 2 Freed

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

-------------------------------------------------------------------------------------------------------------------------------------------------

ANY HELP IN THIS MATTER OF WHY FSUIPC SHUT DOWN FSX AND CAUSED A FATAL ERROR WOULD BE APPRECIATED.

thanks

Mike

Link to comment
Share on other sites

actually, I ran one flight with myaas, and sp1 and 2 installed. Everything was perfect. Then on the return flight I was 70 minutes into an eighty minute flight when an error msg came on and said fsuipc has stopped working and caused a fatal error in fsx.

It certainly sounds like something you have got added into fSX is using FSUIPC wrongly. Either that or there is something very wrong with your FSX installation.

Please, I can't help without details. Find the Windows error log entry for the crash. Right clcik on "My Computer" and select Manage, then look in the Event viewer -- Windows Logs - Application, find FSX and the details. It should confirm FSUIPC4.DLL and provde a crash code and a module offset.

The game didnt save my flight like fsuipc should, and when I reloaded the game fsx, it was back at the original screen Friday harbor with the Trike craft flying, and also the joystick buttons I programmed into it, all had to be redone, as they went back to default as well.

FSUIPC always saves the options when you change them, so it never loses them. Unfortunately FS isn't as well behaved.

Pete, I didnt see a fsuipc4 LOG file

so I found 2 others I could open with notepad.

You have Windows set to hide filenames from you and instead simply tell you they are text files or configuration files. A log file is a text file, with the filename FSUIPC4.LOG. The configuration file s FSUIPC4.INI.

The log file sohws a perfectly normal run, no crash. It terminated correctly. However, the session the log relates to only lasted 21 seconds. It also shows that you haven't registered it, so I'm now wondering why it is installed. What programs or add-ons are you using which requires it? An unregistered FSUIPC is really doing nothing much at all unless it is there to support some application.

Naturally, the log which would be more interesting and useful is the one which is available AFTER the session where you got a crash.

ANY HELP IN THIS MATTER OF WHY FSUIPC SHUT DOWN FSX AND CAUSED A FATAL ERROR WOULD BE APPRECIATED.

Why are you now SHOUTING? That isn't warranted.

An FS session which crashes after 70 minutes is most likely cras hing because of things like memory failure, overheating, or, possibly, corruptin in memory due to bad or corrupted scenery elements. Maybe your crash is more related to the area you arrived into at that time. Crashes caused by memory failure or corruption are notoriously difficult to locate, and can cause a crash in almost any part of the FSX program, including FSUIPC which is merely operating as another FSX module.

Without more details, as I mention, the only way to narrow down your crash problems is by a process of elimination. As you haven't registered FSUIPC you don't have access to its Autosave facility which would have enabled a repeat of the few minutes leading up to the cradh, to determine whether it is locality-related or time-related. Maybe you can try to re-create that point in any case?

Regards

Pete

Link to comment
Share on other sites

I will register today. at sim mart, correct????

I wasnt shouting with CAP letters... I was just showing where it was me talking AFTER the long run of computerese writings. Just to differentiate the end of the computer copy and paste, and where I started talking again.

thx buddy... hopefully by registering it may help some

Mike

Link to comment
Share on other sites

I will register today. at sim mart, correct????

Please don't purchase FSUIPC unless you actually want to use any of its facilities. Browse through the user guide (installed in your FS Modules\FSUIPC Documents folder) first, to see if it is worth your money. Registering it won't necessarily fix any problem you've got -- we don't know why your system is crashing after 70 minutes in any case. Certainly an unregistered FSUIPC is doing far less than a registered version would be.

If you want, instead, to determine the reason for the crash there are other steps to take, as i tried to explain last time.

One other possibility, for instance, is a corrupted weather download -- if you are using FS's real weather facilities. One of the few things FSUIPC is doing when unregistered is getting weather data from FS in case any application program wants to read it.

Unless some add-on you are using actually uses FSUIPC for anything, it is doing virtually nothing else, just sitting in a loop reading weather once or twice per second.

Regards

Pete

Link to comment
Share on other sites

OK... I was able to copy and paste an XML (whatever that is) of the time last night when it crashed. Hopefully this means something:

<
Event
xmlns
="
">

<
System
>

<
Provider
Name
="
Application Error
" />

<
EventID Qualifiers
="
0
">
1000
</
EventID
>

<
Level
>
2
</
Level
>

<
Task
>
100
</
Task
>

<
Keywords
>
0x80000000000000
</
Keywords
>

<
TimeCreated
SystemTime
="
2012-01-26T06:34:21.000000000Z
" />

<
EventRecordID
>
2701
</
EventRecordID
>

<
Channel
>
Application
</
Channel
>

<
Computer
>
Mike-PC
</
Computer
>

<
Security
/>

</System>

<
EventData
>

<
Data
>
fsx.exe
</
Data
>

<
Data
>
10.0.61472.0
</
Data
>

<
Data
>
475e17d3
</
Data
>

<
Data
>
uiautomationcore.dll
</
Data
>

<
Data
>
7.0.0.0
</
Data
>

<
Data
>
4a5bdb1d
</
Data
>

<
Data
>
c0000005
</
Data
>

<
Data
>
0000e52a
</
Data
>

<
Data
>
13e0
</
Data
>

<
Data
>
01ccdbe7cd87698d
</
Data
>

<
Data
>
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
</
Data
>

<
Data
>
C:\Windows\system32\uiautomationcore.dll
</
Data
>

<
Data
>
c75086ed-47e7-11e1-8569-5404a6c27fae
</
Data
>

</EventData>

</Event>

Does anything stand out there?

Link to comment
Share on other sites

<
Data
>
uiautomationcore.dll
</
Data
>

...

<
Data
>
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
</
Data
>

<
Data
>
C:\Windows\system32\uiautomationcore.dll
</
Data
>

Does anything stand out there?

Yes: this is nothing whatsoever to do with FSUIPC, but it is the well-known problem of the Windows 7 version of UIAUTOMATIONCORE.DLL not being compatible with FSX. You'll find solutions over on AVSIM's FSX Forum where this has been a recurrent theme. For example:

http://forum.avsim.net/topic/360394-fsx-ctd/page__p__2233535__hl__uiautomationcoredll__fromsearch__1#entry2233535

and

http://forum.avsim.net/topic/334306-fsx-fatal-error/page__hl__uiautomationcoredll__fromsearch__1

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.