Jump to content
The simFlight Network Forums

Crash to desktop


Recommended Posts

Hi Pete

I just purchased a new computer (I7, Navidia 460, 6mb, etc) primarily to run FSX. I installed Windows7/64bit and then installed FSX Deluxe (Gold). Flew several flights with various aircraft. It flew terrible which I expected since the service pacs were not installed yet but I wanted to go step by step. I then installed the Acceleration disk and flew several more flights with various aircraft. Everything worked great. My next step was to install It's Your Plane. Prior to installation, I read the instructions and it stated I needed FSUIPS4 and gave instructions on how to download it which I did (ver 4.601a) from your web page last night 2/11/11. After installation a popup occured which stated that the program may have not installed properly. At this point I didn't know there was a users guide included in the download so I clicked install again and the popup stated that the program installed properly. I checked FSX/ modules and found the installation and discovered the install log and documents. The last line of the log says: "All installer tasks completed OK". I thought everything was fine so I cranked up FSX. I saw no changes (add-ons) in the appearance of any FSX pages that says FSUIPC was installed, however. I decided to give it a test flight. About 30 minutes into the flight, the program crashed to desktop. I tried 3 additional flights and got the same result. Now I have seen on other forums that FSX had problems with Win7 caused by "UIAUTOMATIONCORE.DLL FILE CAUSES OTHER DLL FILES TO MALFUNCTION" but since this happen immediately after the FSUIPC install, I'm guessing there is a connection. I don't want to proceed until this issue is resolved. Any help would be appreciated.

Learjet6

Link to comment
Share on other sites

After installation a popup occured which stated that the program may have not installed properly.

I think you'll find that's the normal Windows check for you to confirm whether you think it installed properly or not. Windows has no idea one way or the other.

At this point I didn't know there was a users guide included in the download

so you didn't even look at the Installation guide included in the ZIP, the one which tells you what to do?

I checked FSX/ modules and found the installation and discovered the install log and documents.

Yes, the log is the same one which was displayed in front oof you, live, whilst the program was installing, and all the other files are those listed for you in the Installation guide which you didn';t bother to read.

I thought everything was fine so I cranked up FSX. I saw no changes (add-ons) in the appearance of any FSX pages that says FSUIPC was installed,

If there is no "Add-Ons" menu, the right-most one in the normal FS menu when you are ready to fly, then there is a problem with your installation.

however. I decided to give it a test flight. About 30 minutes into the flight, the program crashed to desktop. I tried 3 additional flights and got the same result. Now I have seen on other forums that FSX had problems with Win7 caused by "UIAUTOMATIONCORE.DLL FILE CAUSES OTHER DLL FILES TO MALFUNCTION" but since this happen immediately after the FSUIPC install, I'm guessing there is a connection.

That is very unlikely. There are lots of possible reasons an FSX installation might crash. Without any other information I couldn't guess. Certainly, depending on the add-ons you run, the UIAutomation problem is one of them. Others often revolve around video driver problems, bad scenery files, bad terrain files, and so on.

I don't want to proceed until this issue is resolved. Any help would be appreciated.

You'll need to supply more information. There is nothing at all in anything FSUIPC does which has ever been able to cause a crash to desktop. However, by all means update the FSUIPC4.DLL to the latest, so you are running the same one as me -- it is version 4.661 and it is available in the Download Links subforum here.

To check if FSUIPC is even running, you should do several things:

1. See if there is an AddOns menu, and if so whether FSUIPC is listed in it. If not, then FSUIPC is not even loading and running.

2. See if there are FSUIPC4.INI and FSUIPC4.LOG files in the FSX Modules folder. If not then FSUIPC has never run. If there is a LOG there, show it to me.

If these show that FSUIPC is not running, then show me the Install log and I'll tell you how to work out why.

Regards

Pete

Link to comment
Share on other sites

so you didn't even look at the Installation guide included in the ZIP, the one which tells you what to do?

True, I didn't look there first because I didn't know it was there until the instructions in IYP told me to check FSX modules to see if FSUIPC was installed in FSX. Sorry Pete, long time pilot (22 yrs military and then airline ATP) but not at all savy with computer matters. Go slow with me :).

Yes, the log is the same one which was displayed in front oof you, live, whilst the program was installing, and all the other files are those listed for you in the Installation guide which you didn';t bother to read.

Like above, it's not that I didn't bother to read it, nothing on your official download page said there was an installation file located at...and to read it upon download. Some of us dummies are not as sharp as you and know we should be looking for such files.

If there is no "Add-Ons" menu, the right-most one in the normal FS menu when you are ready to fly, then there is a problem with your installation.

Found it once I knew where to look. It shows installed in the menu under Add-Ons.

That is very unlikely. There are lots of possible reasons an FSX installation might crash. Without any other information I couldn't guess. Certainly, depending on the add-ons you run, the UIAutomation problem is one of them. Others often revolve around video driver problems, bad scenery files, bad terrain files, and so on.

I have no add-ons to FSX Acceleration other than FSUIPC at this point. So far, this is a clean installation.

You'll need to supply more information. There is nothing at all in anything FSUIPC does which has ever been able to cause a crash to desktop. However, by all means update the FSUIPC4.DLL to the latest, so you are running the same one as me -- it is version 4.661 and it is available in the Download Links subforum here.

Ok, I found the new version (4.661) on this site. Do I have to delete anything from the previous setup or will the download simply update the old dlls?

To check if FSUIPC is even running, you should do several things:

1. See if there is an AddOns menu, and if so whether FSUIPC is listed in it. If not, then FSUIPC is not even loading and running.

2. See if there are FSUIPC4.INI and FSUIPC4.LOG files in the FSX Modules folder. If not then FSUIPC has never run. If there is a LOG there, show it to me.

If these show that FSUIPC is not running, then show me the Install log and I'll tell you how to work out why.

1. It's listed in the menu add-on.

2. Can't find FSUIPC4.ini. Where do I look for it? I see Documents, Install log, dll, .config. settings, text document.

I tried to add my log as an attachment but it said I wasn't permitted to upload this kind of file so here's the log.

Installer for FSUIPC4.DLL version 4.60a

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\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

... NOT found! ...

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

INSTALLATION FOR FSX:

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

Checking version of 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

... Version 4.600 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\Art1\AppData\Roaming"

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

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

Found FSX.CFG in "C:\Users\Art1\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\Art1\Application Data\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Contacts\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Cookies\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Desktop\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Documents\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Downloads\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Favorites\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Links\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Local Settings\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Music\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\My Documents\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\NetHood\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Pictures\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\PrintHood\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Recent\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Saved Games\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Searches\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\SendTo\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Start Menu\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Templates\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Art1\Videos\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 "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 okay!

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

Sorry, I'm not very computer savy but I'm trying :).

Thanks again for the help.

Cheers

Art

Learjet6

Link to comment
Share on other sites

Like above, it's not that I didn't bother to read it, nothing on your official download page said there was an installation file located at...and to read it upon download.

Er ... there should be no need! The ZIP file contains the Installer program and a PDF entitled "Installing and Registering FSUIPC". Surely that's enough of a Hint? Do you really need ANOTHER document in there saying "READ THE OTHER DOCUMENT FIRST".

There is no Installing and Registering document INSTALLED, only the full user guides and other things. If you'd bothered to read the Installation guide you'd have seen all this explained.

Some of us dummies are not as sharp as you and know we should be looking for such files.

You don't have to look far when it was in the ZIP next to the program you extracted and ran! Where else do you expect me to put it?

I have no add-ons to FSX Acceleration other than FSUIPC at this point. So far, this is a clean installation.

So nothing is using FSUIPC4 for anything? I thought you installed it because some add-on requested it?

Ok, I found the new version (4.661) on this site. Do I have to delete anything from the previous setup or will the download simply update the old dlls?

Just downloading it does nothing at all. You copy it into the FSX modules folder, exactly as it says next to the place you clicked to download it. That's what explanations are for!

2. Can't find FSUIPC4.ini. Where do I look for it?

As I said."See if there are FSUIPC4.INI and FSUIPC4.LOG files in the FSX Modules folder." You seem to be ignoring or skipping over a lot of stuff put here to help! :-(

I see Documents, Install log, dll, .config. settings, text document.

you have Windows Explorer set to hide the full filenames from you, for those file types it things it knows. You should really change that or you will have problems with lots of addons. Explorer folder options, uncheck "hide file types" or whatever it is called.

Anyway, an INI file is a type of "config settings" file. All CFG and INI files will list like that. And a LOG file is a type of text file.

I tried to add my log as an attachment but it said I wasn't permitted to upload this kind of file so here's the log.

Yes, it's best to paste text files like logs into messages. Anyway, since FSUIPC is evidently running I don't need to see the Install log. Maybe the run-time log (FSUIPC4.LOG) would tell me something, but it is doubtful.

If you are not running anything that needs to use FSUIPC, and you haven't purchased and registered FSUIPC4, then FSUIPC4 is really doing nothing at all, it is just sitting there receiving information from SimConnect (part of FSX).

The only time I've known any crash happen just by receiving data from SimConnect is when there's a faulty weather file or bad WXSTATIONLIST.BIN file. This causes the crash in WEATHER.DLL, not in FSUIPC, and would happen in the same circumstances if anything read the weather. This sort of corruption can sometimes arise if you use the FSX default real weather downloads, because it seems these are not checked adequately by FS and can arrive corrupted from the website. The only way I could tell that is by getting you to make a SimConnect. logfile, but i think that is beyond your capabilities for now. If you've not used the real weather downloads since you installed FSX then it's not likely in any case. A way for you to check would be to delete all of the .WX files from the Flight Simulator X Files folder in your Documents folder, and also the WXSTATIONLIST.BIN file from here:

C:\Users\Art1\AppData\Roaming\Microsoft\FSX

Then run FSX. Next time you download real weather the latter file will be rebuilt.

Regards

Pete

Link to comment
Share on other sites

Hi Pete

Problem solved. I added the 32bit UIAUTOMATIONCORE.DLL file to the FSX directory last night. Today I flew from Orlando (my home town) to St. Louis and then on to Los Angeles without a hickup. That must have been the problem. Thanks for your time and patience by answering my questions, however. It did point me in the right direction.

Now all I have to figure out is how much a Euro is these days so I can register your software and start adding other ADD-ONS to FSX :).

Art

Learjet6

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.