• 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

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

CTD trouble

Well, with no AI it will run happily for over two hours, but when I set the sliders to 10% there's a CTD after about an hour, caused by ai_player.dll so I think it is narrowed down to one of two things: either the dll, or the video card (AMD Radeon HD 6470M) getting overloaded by too much AI. Since AI does appear, and the sliders control the amount of AI properly, I tend to lean toward the card which, after all, is a fairly low end one. Any thoughts please?
 
dhasdell said:
Well, with no AI it will run happily for over two hours, but when I set the sliders to 10% there's a CTD after about an hour, caused by ai_player.dll so I think it is narrowed down to one of two things: either the dll, or the video card (AMD Radeon HD 6470M) getting overloaded by too much AI. Since AI does appear, and the sliders control the amount of AI properly, I tend to lean toward the card which, after all, is a fairly low end one. Any thoughts please?
Click to expand...

For what it's worth, I have this issue with ai_player.dll crashes too. Mine usually happen as I'm trying to exit FSX. I've NOT been able to identify the cuplprit either, sorry:-(
 
dhasdell said:
Well, with no AI it will run happily for over two hours, but when I set the sliders to 10% there's a CTD after about an hour, caused by ai_player.dll so I think it is narrowed down to one of two things: either the dll, or the video card (AMD Radeon HD 6470M) getting overloaded by too much AI. Since AI does appear, and the sliders control the amount of AI properly, I tend to lean toward the card which, after all, is a fairly low end one. Any thoughts please?
Click to expand...
Add-On AI? It will take some time. A single duff AI model, *.air, or texture, can cause the CTD, so, if you don't have a lot of AI planes, removing those, and putting them back one at a time, may be faster than removing traffic.bgls
If you have a ton of AI, like I do, removing all of your AI traffic.bgl files(defaults too) and putting them back one at a time might help isolate the problem child.
To be sure, you must fly a flight path that is known to CTD with the AI enabled. Some AI are regional and may not spawn where you are.

Before attempting a repair etc. isolate it. A repair will not fix a duff/corrupt add-on.

Repair: Rename the default traffic files {...FSX\Scenery\World\Scenery} and ai_player.dll before the attempt.

The biggie with a Repair is any default file, including those default aircraft.cfgs with added liveries, that have been modified, tweaked, or otherwise changed, will be returned to default status.
You can make a copy of your existing FSX folder before the repair and paste those individual files back in afterwards.

Important: If you have SP1, SP2, or Acceleration installed, they will have to be uninstalled before a repair attempt, and reinstalled, after the repair, or it won't work.
Once you have your FSX up and running properly again, back it up, all of it.

FSX file locations:
fsx.cfg and GrantedRewards.BIN, {C:\Users\User Name\AppData\Roaming\Microsoft\FSX}
Your control settings = Standard.xml {C:\Users\User Name\AppData\Roaming\Microsoft\FSX\Controls}
Logbook.BIN and flight plan files {C:\Users\User Name\Documents\Flight Simulator X Files}
scenery.cfg {C:\ProgramData\Microsoft\FSX}

You may need it again and it's a lot easier than a Repair or Re-Install...Don
 
I have always related this to extreme scenery coupled with extreme textures on a new plane. If you have huge textures and new scenery, then as you fly, your system resources on the computer start to build up until BING, windows closes it down before it causes windows to crash.

To test this, setup a flight in a basic stock small plane, flying over the desert. See if it makes it over a desert region for 30+ min's in auto pilot. If it does, then add a plane that is new, sophisticated, and see if it can do the same route over the desert (like over Africa somewhere). If that makes it, then try the simple plane in the usual route you run where the crashing is happening. If that lasts fine, then add the detailed plane in the land where it crashes. If it crashes there (as it was before) but no where else, and with certain planes, then its either the land or the plane or both that is causing this.

Some planes have a memory drain issue (bad gauge design) that can cause this.

Also, a newly loaded airport addon that is a duplicate airport with the same name will cause the sim to crash also such as KDVT and KDVT in the addon folder, etc.

Hope that helps.



Bill
 
My thanks to all those who have offered suggestions. I don't think I have duplicates in scenery, or clashes in traffic.bgl files, but then again if it was obvious I'd have found it, wouldn't I? I'll keep poking about with it and see what happens.
 
I think that it was airports called up in the AI flightplans that didn't exist in FSX that caused my problems.
 
So if I had installed and later deleted the Orbx Tasmania demo, but didn't delete the Australia AI, that might be it? I thought I had temporarily deleted all extra AI traffic files, but that is possible.
 
Have you added some new AI planes? As the module AI player appears either corrupted or having problems handling your AI. Sometimes FSX will ctd when one (or more) AI planes have corrupted textures.
Or could be related to AI Carriers, as you said it was on the list but wasn't activated at all.

Hank
 
dhasdell said:
So if I had installed and later deleted the Orbx Tasmania demo, but didn't delete the Australia AI, that might be it? I thought I had temporarily deleted all extra AI traffic files, but that is possible.
Click to expand...

Yes indeed, that might be it. Also, it may be that the ai_player.dll got corrupted after a while. This is windows remember? And you have one of the worst windows versions running that was ever released. I'm not trying to put you down or anything, but that is just an observation, nothing more.

You could try to search your FSX DVD's for the ai_player.dll and replace that one with the one on your rig. If you are running FSX-A, install the dll from the accelleration DVD!

But IMHO, the best thing you could do is ditch Vista and move over to Windows 7 64 bit. Windows 8 is almost as bad as Vista, so that would be a "bridge too far". It would mean a total install from scratch, but IMHO it is worth it.

A quote: the source code of windows vista is probably the longest suicide note in human history...

I sincerely hope you get this sorted out WITH the added pleasure of having AI traffic!

Take care,

Dumonceau
 
You must log in or register to reply here.
Back
Top