After about a week of dealing with Microsoft Flight Simulator X giving me fatal error messages I figure I would remove it from my hard drive.... once again... and try another route. I've been reading and doing my homework. I have found that Windows 7 64bit and FSX just don't get along, causing things to become unstable and crash for some as in my case here. But others have no issues with it what so ever. Some say to install Flight Sim on a completely separate hard drive altogether. Well for me this isn't going to work because I'm a broke s.o.b. and simply don't have the funding to add another hard drive to my computer so I took a different approach today. Instead of installing FSX to its typical default destination within the confines of my hard drive I made a new folder directly into my C: drive directory and promptly named it Microsoft Flight Simulator X. Some people have had great success installing it this way, for the computer doesn't have to dig so deep to find the software buying my processors a little more time to do other duties such as rendering autogen, textures, ect. ect. I also know from past experience that a little .dll file called uiautomationcore.dll could also be the culprit to my mysterious fatal error crashes. I believe that this isn't the case for me though as I have tried in the past with all the tips and tricks of fixing the uiautomationcore.dll and has never worked for me so it must be something else.I have had all my drivers updated and so forth. It could possibly be the actual hardware itself or lack there of. Im on a Acer Aspire desktop which has a 256mb integrated video card. Good thing is it has 4 gigs of DDR3 ram and a 3.2 quad core processor. Bad news is finding a video card that will fit into the tiny little computer casing plus not to mention finding a strong enough power supply that is also compact enough to fit into the little rig to power the video card. Then again the lack of funding comes into play so I gotta work with what I got. Honestly though with the proper application of tweaks to the fsx.cfg and some modifications to the textures and resizing the autogen I can run FSX at a decent 20-24fps locked. With most of my sliders cranked. Not to shabby I suppose considering the hardware Im working with. Hopefully moving the default destination of fsx to a subfolder just inside the C: drive, i.e. C\ Microsoft Flight Simulator X will prove to be effective for me. As I have learned over the almost 18 years of working with flight simulator, the hard way I might add, is to never hold your breath when it comes to things like this. You can hope for the best but expect the worse. This especially holds true when it comes with dealing with FSX.... there is no miracle cure or quick/easy fix. If it aint one thing its another.
So Ive spent just about my entire day uninstalling FSX and then reinstalling it then added all my tweaks and such finally finished my last round of defragging with O&O defrag. I have had no time today to see if any of these thing has improved performance and rid me of that bloody freakin "fatal error". Only time and alot of patience will tell.
My apologies go out to the guys over at VFR Prop Hops I was looking forward to joining you guys today as you trekked across Cuba but as you can see I've been a little busy lol. Maybe Ill be able to join you guys this weekend, who knows?! Im hopefull!
1 comment:
Post a Comment