that I found from reading the forum. it occurred when I began to use spot plane during video replay mode after a lengthy flight. it was jerky, so as i did a right click to choose fixed spot, FSX crashed with the uiautomation.dll error. anyone know why? (http://forum.avsim.net/topic/340889-black-screen-after-long-flight/page__hl__black+screen__fromsearch__1 0) I hadn't had a fatal error in FSX before, on this roughly week long installation. Secondly, when i got to my destination (heathrow) progressive taxi didn't turn on when I selected it. ideas? btw I'm using DX10.

Hi,Progressive taxi doesn't work correctly in DX10 as it was (DX10) released as a preview, and not a finished product. On the uiautomation.dll, yep, just drop it in the FSX folder and the sim will use it instead of the system file of the same name.

Hi, Progressive taxi doesn't work correctly in DX10 as it was (DX10) released as a preview, and not a finished product. On the uiautomation.dll, yep, just drop it in the FSX folder and the sim will use it instead of the system file of the same name.

that's what I had done today, and less than an hour later, I got my first fatal error in FSX. :) and the error message mentioned that file. I only installed it (and registered it) because of a black screen I had gotten this afternoon--also a first. sigh.

that's what I had done today, and less than an hour later, I got my first fatal error in FSX. :) and the error message mentioned that file. I only installed it (and registered it) because of a black screen I had gotten this afternoon--also a first. sigh.

Sigh? Really. No offense, but if those have been the extent of your woes with FSX then, can I respectfully suggest, to simply quit "chasing the grail" of tweaking and just fly. (and maybe just turn a slider or two down a notch.)

that's what I had done today, and less than an hour later, I got my first fatal error in FSX. :) and the error message mentioned that file. I only installed it (and registered it) because of a black screen I had gotten this afternoon--also a first. sigh.

You should not have "registered" it. FSX will automatically load and use that copy of the uiautomationcore.dll when loaded. By "registering" that copy Win7 will now try to use that (older) version all the time instead of the one written for Win7...

You should not have "registered" it. FSX will automatically load and use that copy of the uiautomationcore.dll when loaded. By "registering" that copy Win7 will now try to use that (older) version all the time instead of the one written for Win7...

so u are saying that the explicit instructions in the other thread are wrong? who to trust? who to trust? LOL!! I need to go google how to unregister it. we'll see if that helps. thanks for the idea. EDIT: looks like "-u" command-line parameter does it. EDIT2: I got a error when trying to unregister it. Only thing I could think of was to register the dll that's in system32. then I renamed the one in the FSX folder pending any further action with that file if someone comes up with a better plan.

You should not have "registered" it. FSX will automatically load and use that copy of the uiautomationcore.dll when loaded. By "registering" that copy Win7 will now try to use that (older) version all the time instead of the one written for Win7...

The folks on MS Technet disagree, Bill - but I believe you are correct. There should be no need to register it if it's dropped into the FSX root folder. I personally had never registered it until I found the recommendation to register it elsewhere - and, that being said - I have had no issues before - or after doing so, and using the 6.0.5840.16386 version. That Dave got a fatal error after he put it in may well implicate that file - but that does not necessarily mean that it absolutely was the cause, as, if that was the case - everyone else would be having this same fatal error. Something else was going on here. To answer Dave's comment "Who to trust?". Well - I'm sure Bill will back me up here -if you don't trust anyone, Dave - you'll never get FSX running right, and almost all pc & server users will screw up something at some time: the operating system is a pretty complex beast; your pc is a pretty complex beast, and you are a pretty complex beast person! At any time a user can blunder into a situation which has an outcome quite different to the expected outcome - and it can happen in a moment of inattention; through inexperience; through being in over your head, etc., and one has no idea why "this mess" should have happened. "I didn't do anything" is the most used Tech Support phrase I've ever heard. The 32-bit UIAutomationCore.dll. v 6.0.5840.16386, which is the one which has worked flawlessly for my pc for probably two years, should be dropped into the root folder of FSX. That's all. FSX.exe will see it and will use it. It should not cause a fatal error. Period. Even registering it will not cause FSX to have a fatal error.

The folks on MS Technet disagree, Bill - but I believe you are correct. There should be no need to register it if it's dropped into the FSX root folder. I personally had never registered it until I found the recommendation to register it elsewhere - and, that being said - I have had no issues before - or after doing so, and using the 6.0.5840.16386 version. That Dave got a fatal error after he put it in may well implicate that file - but that does not necessarily mean that it absolutely was the cause, as, if that was the case - everyone else would be having this same fatal error. Something else was going on here. To answer Dave's comment "Who to trust?". Well - I'm sure Bill will back me up here -if you don't trust anyone, Dave - you'll never get FSX running right, and almost all pc & server users will screw up something at some time: the operating system is a pretty complex beast; your pc is a pretty complex beast, and you are a pretty complex beast person! At any time a user can blunder into a situation which has an outcome quite different to the expected outcome - and it can happen in a moment of inattention; through inexperience; through being in over your head, etc., and one has no idea why "this mess" should have happened. "I didn't do anything" is the most used Tech Support phrase I've ever heard. The 32-bit UIAutomationCore.dll. v 6.0.5840.16386, which is the one which has worked flawlessly for my pc for probably two years, should be dropped into the root folder of FSX. That's all. FSX.exe will see it and will use it. It should not cause a fatal error. Period. Even registering it will not cause FSX to have a fatal error.

thanks. yup, that's the one I have (don't take my comment about trust too seriously! :) ) I'm just frustrated at a variation in what is the correct procedure for dealing with black screens or crashes) TIA

just got another fatal error. after the error, I went ahead and renamed that dll file in my FSX folder so that it won't be used, and I'll see how FSX responds.

I understand, Dave; it's just an unfortunate fact in dealing with FSX: it has been so modified, patched and upgraded over the years, always with built-in backward compatibility, while simultaneously trying to cater to future hardware - and supporting drivers and other software which hadn't been developed when even SP2 was released. Not only are modern gpu's using 2gig of memory, it's DDR-3, or it's SLI, or PCI-x or PCI-e. No more bus mastering. 3-Channel system memory: three new OS's since Windows 98... 64-bit.. It is a miracle to me that devs like Bill can keep up - let alone the average user.

I haven't had much luck with the solution. I have the stated version in the FSX folder. In my case FSX crashes upon invoking the ground crew menu in the Level-D B767. All I gather is that this "strange behavior" happens to some, but not to others.

I haven't had much luck with the solution. I have the stated version in the FSX folder. In my case FSX crashes upon invoking the ground crew menu in the Level-D B767. All I gather is that this "strange behavior" happens to some, but not to others.

I did the things (choosing different views points) that caused the fatal error, and had no problem, once I removed the dll from the FSX folder. I think I'll just sim w/o that file. :) If I get more show stoppers, then I'll come back for more ideas.

I haven't had much luck with the solution. I have the stated version in the FSX folder. In my case FSX crashes upon invoking the ground crew menu in the Level-D B767. All I gather is that this "strange behavior" happens to some, but not to others.

If it's only happaning with the Level-D menu, you may also want to check the relevant forum. Cheers, Geraldhttp://www.multicrewxp.com

Gerald, thank you. Did before posting here. Regards,

uiautomationcore error today.Can I copy the one from my Win7-64bit system and put it into the FSX folder or ...I have my old PC with Win Vista 32 bit would that work? Update ... I found the link to the correct file .. will test it.