Bloody

Hello all, I recently decided to do a clean Windows install on my PC and now I am asking, whether to install the MS FSX or the FSX-Steam version for my new installation. Previously I only used the MS Gold (I own the Steam version though) and was neither happy nor unhappy and now I am not sure which version works better at the moment. I'm on Windows 10, my addons I will reinstall are: -OrbX Global -OrbX OpenLC Europe -ASN -GSX -PMDG 737 NGX -UT2 -Some smaller scenery/aircraft addons Is it advised to install the Steam Edition as it is newer and potentially still getting updates or is the MS version working better with the addons? Or doesn't it matter at all? Thanks in advance! Eric

I could uninstall and completely reinstall the NGX without entering the activation code. Also wasn't asked for it when loading the plane.

Had exactly the same problem last night, but I downloaded it with full speed just an hour ago, not sure where the problem was. Maybe just try it again later.

Hey all, a friend of mine are flying lots and lots of hours in Multiplayer using the shared-cockpit Feature. As not many aircraft support it, I would like to get information of every payware plane that supports it. We currently have the Beechcraft Turbo Duke and Lotus L39 Albatros, both work perfectly. I know that the Maddog support Multicrew too, but we didnt try it yet - the VC looks...quite awfully, but we might give it a try if there arent any more planes. I also read that the Fokker F70/100 supports shared cockpit, but as it has no VC, it is no option. Are there any other planes which can be used in multiplayer using shared cockpit? What about some none-complex payware models like the DHC6 Twin Otter?

During my research on the internet I felt that the UIAutomationCore.dll fix solved the problem for everyone except me...good that it works for both of us now though. :)I always update it whenever there is a new version, currently I'm on AMD Catalyst 12.1 :)

Jahman: Did that alot of times :/ANYWAY:Seems I got my solution! I found this post again after I tried it with 3 different vista uiautomationcore.dll files. Because I got nothing to lose I deleted all the files again on my PC and - I am NOT able to reproduce my problem within 20 minutes of just rightclicking on the screen and highlighting menu-entrys. I even tried to add the uiautomationcore.dll to the FSX directory and it didnt take me 2 minutes to get a CDS again. So I think dotnet has to live without this file from now on. Im going to install all my addons and will do some long testing later that evening. Would be awesome to enjoy FSX without crashing after clicking in the menu sometime in the flight.I hope not to be disappointed by that solution; lets see what happens with longer testing. At least I didnt notice any disadvantage from having no u..dll.Thanks for your help again!

Hey firehawk, thanks for that detailed reply!I do understand that uiautomationcore.dll is not meant to be deleted, but I wanted to try it anyways, just for testing purposes. DO I have to do that? The screen that activates on every vista boot tells me already that I have 8GB of RAM. Is it still needed? I used a version of vista where SP2 was already included. Probably is it installed already? So you think the reason it works now is because I installed FSX on another partition and nothing else? I didnt explicitly try that, but it doesnt sound...reasonable to me. What do you recommend on getting it working on Win7? Format C and reinstall FSX on another partition? Wouldnt like that solution, but in case it works I would prefer it than switching the OS all the time. I will have another look at this soon. The XMP-1600 Settings are a little different to my current settings, I will change them. Most of the posts there refer to uiautomationcore, but I will have another look there.Again thanks for your reply, in case you got anymore hints please feel free to share them with me. :)

Alright, I installed Win Vista x32 as a second OS today and couldnt reproduce the CTD anymore. This makes me really believe that it is no hardwareissue, more a 64-Bit problem. Since it only happens when using the menus the symptoms have a 100% match to the uiautomationcore.dll problem.Sadly all the fixes on the internet aint working here. Does anyone have another idea? Having it working under Vista is great, but its still not comfortable to switch the OS if I just want to fly a little.

Hey,followed every single step in this thread, even the different .dlls. Sadly I'm still able to reproduce this problem, so it didnt help....Any other ideas?

Hey all...I cant really enjoy FSX since I suffer from CTDs. They always appear (sometimes after 5, sometimes after 10 minutes of trying to reproduce or around 60 minutes of flying) when using the menu ingame. I got a 100% reproduce-rate when rightclicking ingame and selecting all the elements, pressing alt, selecting the elements there, clicking on one of them and repeat that until it crashes.It happens with addons or with an absolute-fresh-install, no sp, with sp2, with acc. exp pack...I dont think that this is related to any fsx mods so.My current system:Board: Asus M5A99X EvoCPU: AMD Phenom 2 X6 6x,3.2GHZRAM: G.Skill DIMM 8 GB DDR3-1333 KitGraphic: ATI HD4870OS: Win7 x64 with automatic updatesFirst of all: I updated my PC a few months ago, had a AMD X2 2x2,7ghz CPU and 4GB of RAM with a different Mainboard (can find that out if it matters) and Win7 x32, and I dont remember experiencing those CTDs. After updating the PC I began to play FSX again a few weeks ago and suffer from those CTDs since then. Most of the time it says the failing module is uiautomationcore.dll. I found a lot entrys about uiautomationcore.dll and Win 7 x64, all reported that the solution should be to use a vista uiautomationcore.dll and place it in the FSX directory. Sadly it doesnt change anything, it still crashes with this module (although the module version number has the one from vista). I tried with simple inserting it in the directory, registering the dll and even deleting all the uiautomationcore.dll from Win7 in sys32 and the other folder.When I delete all the uiautomationcore.dll from my PC it still crashes, the failing module is simply "unknown" afterwards. I tried reinstalling FSX (with deleting everything related to FSX on my PC), even changing the RAM Mode from ungaged to gaged because I read it somewhere here in the forum. Since I have no ideas anymore (and cant find any tips on the internet anymore) I will install Win Vista x32 tomorrow, just for FSX to try if it changes anything.I appreciate any help and really hope someone has a clue what I could do, because even if the second OS trick worked I wouldnt like switching the OS ever when I want to use FSX. I read some posts about changing RAM/CPU settings, maybe I should work there? Could it be wrong RAM timings for example? I have really no explanation anymore...If there is any information missing please feel free to ask!Thanks in Advance, Bloody