• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

Your F****** kidding me....

fallenphoenix1986

fallenphoenix1986

SOH-CM-2022
Ok, I'm a fighter guy.. I rarely go up for more than 40 minutes... can usually be found circuiting a carrier however last night I decided to give the big iron a go. I flew a short hop from Bristol to Glasgow IFR in an Embraer 170, no problem. Tonight I thought it be interesting to try a Transalantic hop... though I don't have 6 or 7 hours to spare... Concord it is then... all goes well, get her up to 60,000 and Mach 2.00 without much trouble,transit accross to Newfoundland before making my way down the eastern seaboard. I'm in touch with JFK setting up my aproach... rolling onto finals....

"FSX has suffered a fatal error and is restarting"

I now have a computer shapped hole in the wall :pop4:

Craig
 
I get the same thing hauling from Deccimamanu to Toulon- as soon as I get within sight of the coast-poof- fatal error. There must be a corrupt scenery file or something, but I have not found it
 
I hate it when that happens.

If you have the registered version of FSUIPC, it saves your flight at intervals (autosave), and you can re-start FS and go back to your flight within minutes of it crashing, then resume. Yea, a bit of a 'break in action', but sure is nice to be able to finish you flight after hours in the air. Luckily it is rare, but a great feature when you need it.
 
I have those things quite often. I now have certain no-go area's. Latest error cost me all my settings (tweaked controls and programmed buttons). Had to do all the programming again since the cfg file was corrupted.
There are still some errors in FSX that are not fixed, but there will be no update to FSX since MS decided to pull the plug!

I have learned to live with it........:mixedsmi:
 
During the time I was building my mass bomber stream of B-17's going from Basingbourne, England to St. Nazaire, France and back, that happened to me a number of times. You should have heard me HOWL with F...king rage....
 
Been there, done that. I've learned on long flights to periodically save the flight, JIC.

I feel for you guys. I know exactly the wtf moment you're talking about, lol. It's not funny when it happens, it's just funny because I can relate.
 
Yep...I've been there too. One of the main reasons why I only fly short haul now.

Nothing worse than having an hour to take a quick flight...spending 10 minutes waiting for the sim to load up,another few minutes to select your desired aircraft, set desired fuel,carry out checklists, taxi to the runway,push the throttles forward,start to get airborne (after about 30 minutes) and WHAM...no more FSX :sleep:
 
With some patience and some trail and error, most of that can be worked out.

It seems to me that there are two main causes for the old CTD. The first is related to add-on traffic files. If this is the cause, it's probably because there is an airplane in there that has issues. The second is usually caused by an error in add-on scenery.

Finding the approximate cause is easy. Start by deactivating the add-on scenery in the area. Then, remove "local" traffic files. I try to regionalize my traffic to make loading quicker, but that's another story. Start flightsim and fly a default airplane in the affected area. If it works, close out flightsim and add either traffic or scenery, either one file or one folder at a time depending on how your scenery is organized. Also, depending on how you've organized your folders, you can go to the add/remove scenery area and turn it on and off. Then try again. If all works, continue the process of closing flightsim and repeating the process of adding back a folder and rerunning. Once you have found a suspected folder, remove it and try again. Keep in mind that there may be more than one issue, so even if you find one problem, you should continue to hunt for issues.
 
Had the same issue, esp. long hauls. If you don't have it yet, and you have Vista or Win7, just unzip and drop this baby in your main FSX folder and it should solve your problem.
 
wantok said:
Had the same issue, esp. long hauls. If you don't have it yet, and you have Vista or Win7, just unzip and drop this baby in your main FSX folder and it should solve your problem.
Click to expand...

Thanks for sharing. But, what does it do?
 
There's one more thing to think about..... since we're nearing the change to Fall, it could be the dreaded 'season bug'. It is a bug that seems to happen when at or near a season change, like from Summer to Autumn, combined with being near some scenery border. We had it often near Alaska when Fall turned into Winter...... just sayin'.....
 
Regarding this UIAutomationCore.dll file, where does it go? I have 3 of these in various locations:-

1. System32
2. SysWOW64
3. wow64_microsoft-windows...... etc etc....

No biggy as I have not experienced this crashing symptom yet but one never knows ..... Murphy's law states it will happen within minutes of posting this.. lol
 
No need to touch the other 3, just move the one referenced in my above post to your root FSX folder.
 
You must log in or register to reply here.
Back
Top