DVA12393
Captain, A320
OLP
Joined on April 24 2014
Fresno, CA
61 legs, 206.5 hours
61 legs,
206.5 hours online 61 legs,
206.5 hours ACARS
|
Posted onPost created on
November 12 2014 03:58 ET by Jon Wilder
|
When I started flying in the VA community a couple of years ago, I was flying on FSX. I had purchased FSX Deluxe Edition back in 2006 before I had a machine that could run it. I held onto it throughout the years and finally decided to run it on my current machine.
In most cases it was fine until I got into areas of high density traffic. That was when all hell would break loose and I would run into crash-to-desktops with "Fatal Error Occurred". Eventually it didn't matter whether I was in areas of high traffic density and it would just do it at random.
At the time I had a system with only 2GB of memory. I increased it to 4GB DDR800 (the max DDR speed my mobo is compatible with) with matched sticks running dual channel. I can max the system to 8GB to allow for headroom for the OS and everything else that runs but haven't done that yet.
Nonetheless, I continued to have issues. I finally just started flying FS9 and called it a day. Figured I'd go back to running FSX when/if I ever got a better machine.
Fast forward to last night...I decided to install my new Wilco Airbus Evolution Vol 1 for FSX and give it a go. I started a flight out of SFO to MSP. About 2,000' from cruise flight level I had a dual engine flameout for unknown reasons. Later found out it had to do with a bug with FSInn weather and Simconnect. OK fine...I won't run FSInn weather. However, tried to get the flight going again, only to be presented with CTD's and "Fatal Errors" once again.
OK so...do some research. I came to learn that FSX under Windows 7 has a lot of issues with User Account Control. Remembering how I had to install the Wilco Airbus Evolution by first adding my user account name to the Security tab of the FS9 root directory and give my account full control plus run the installer as administrator, I decided to attact FSX the same way.
Now...I install my flight sims not just in their own separate directory outside of Program Files(x86), but I also install them on a separate hard drive. I decided to first do a complete remove/reinstall of FSX. I removed FSX plus deleted the App Data\Roaming\Microsoft\FSX directory. Before I did anything else, I first disabled my anti-virus, then I added my account name to the Security tab of the entire Flight Sim hard drive and gave my account Full Control access. I then ran the FSX installer as administrator, selected D:\Microsoft Games\Microsoft Flight Simulator X as my install directory, and completed the install. Then I installed FSUIPC, FSCopilot/FSInn, and my Wilco Airbus Evolution Volume 1...all of which I ran as administrator. Lastly, I downloaded and placed a 32-bit uiautomationcore.dll in the FSX root directory. Go through all the settings and get everything configured how I had it before, then proceeded to fly it.
Since last night I have done 4 full flights...all of them on VATSIM and DVA ACARS logged and not even so much as a hint of a CTD.
So I am officially back to flying FSX. After all this time of accepting that I just did not have a machine that would run it, only to find out that Windows 7 User Account Control was the culprit all along...even though I had turned the UAC fader all the way down!
|
DVA11781
Captain, MD-11
Joined on October 03 2013
Everett 250 Club
Million Mile Club
DVA Two-Year Anniversary
Quatercentenary Club
Northeastern United States
|
Posted onPost created on
November 12 2014 08:49 ET by Joe Cappelo
|
DVA6534
Senior Captain, B747-400
OLP
Joined on October 19 2008
50 State Club
Online Triple Century Club
Quincentenary Club
DVA Ten-Year Anniversary
Everett 250 Club
Cleveland, OH USA
576 legs, 1,329.4 hours
377 legs,
879.4 hours online 570 legs,
1,318.5 hours ACARS 36 legs,
87.6 hours event 30 legs dispatched, 40.9
hours
|
Posted onPost created on
December 26 2014 07:20 ET by John DeBarr
|
ooh.. Jon. I was just to post something to the effect of "Is FSX just a steaming pile of garbage?" I am back after a 2 year break with a new computer too. I JUST on xmas eve reinstalled my desktop operating system (win8 x64) my machine is a screamer too. I took a quick flight and well.. CTD. I was about at wits end and about to hang it up when I read this post. (I got TrackIR 5 for Christmas too from the wife) So before I just scrap the whole idea of flying (because it crashes to much.
What is this you are talking about ??
Where did you get these instructions?
<quote>
OK so...do some research. I came to learn that FSX under Windows 7 has a lot of issues with User Account Control. Remembering how I had to install the Wilco Airbus Evolution by first adding my user account name to the Security tab of the FS9 root directory and give my account full control plus run the installer as administrator, I decided to attact FSX the same way.
Now...I install my flight sims not just in their own separate directory outside of Program Files(x86), but I also install them on a separate hard drive. I decided to first do a complete remove/reinstall of FSX. I removed FSX plus deleted the App Data\Roaming\Microsoft\FSX directory. Before I did anything else, I first disabled my anti-virus, then I added my account name to the Security tab of the entire Flight Sim hard drive and gave my account Full Control access. I then ran the FSX installer as administrator, selected D:\Microsoft Games\Microsoft Flight Simulator X as my install directory, and completed the install. Then I installed FSUIPC, FSCopilot/FSInn, and my Wilco Airbus Evolution Volume 1...all of which I ran as administrator. Lastly, I downloaded and placed a 32-bit uiautomationcore.dll in the FSX root directory. Go through all the settings and get everything configured how I had it before, then proceeded to fly it.
<end quote>
John DeBarrSenior Captain, B747-400
|
|