Hi,

 

Over the weekend I've been playing around with AI, and downloaded a large number of World of AI packs. I'd never really flown with AI in the past (always at 0), but thought I'd try as it'd add a bit of extra immersion.

 

I now find that if I fly around either UK2000 EGLL or EGKK with AI enabled (tried various levels from 100 down to 1%), when I exit FSX and check the event viewer, it always registers an Application Error for fsx.exe with faulting module ai_player.dll, which I believe simply put is the module for controlling AI traffic. Note that FSX doesn't actually CTD, and no error message is displayed on exit (although so far all my flights have been very short just for experimental purposes to see the traffic, I don't know whether it will if I try a proper flight), but it always registers in Event Viewer.

 

I thought it might be something with a WoAI package causing it but actually going back through the logs it started happening when experimenting with default traffic also, before I downloaded any WoAI packs.

 

Anyone seen this before?

 

I've also tried disabling UK2000 EGLL but still get the error. I don't get it at FlyTampa St Maarten but I guess that's not a fair comparison as there's nowhere near as much traffic there.

According to the AVSIM CTD Guide the following are a list of probable fixes:

AI_Player.dll - The faulting module was the ai_player.dll which is the module that controls your AI (a commercial AI program or the default).
• Could be something wrong with an AI model or object. If you have MyTrafficX, you can disable AI in the Scenery Library to see if this fixes the problem. If so, then this is the problem. If you have another AI program installed, then disable that program to see if the program is causing your crashes.
• Problem occurs occasionally in the Seattle area with FTX/Orbx Pacific Northwest. This may have been fixed by now but check the FTX/Orbx forums and search for AI_Player.
• Caused by freeware airports in the area that has static aircraft or their own AI aircraft and flight plans. Disable the add-on airport and see if problem is gone. If you have any FSDT, Flight Beam airports, do not disable them. They are not the problem.
• AI programs like MyTrafficX has AFCAD's for hundreds, maybe thousands of airports in the MyTraffic/Scenery folder. Anyone of these could be the cause of the ai_player crash. In this case, make sure you have the latest version of your AI program installed.

Best regards,

Hi,

 

Thanks for this.

 

Following your advice I have managed to whittle it down to UK2000 Gatwick Xtreme being the likely culprit for the error. When I disable it from the Scenery Library I can fly there or any other airports in the locality and not get the error on exit. When I enable Gatwick Xtreme I start getting the error if I fly anywhere near the airport.

 

Anyone know how to fix this?

 

Cheers

Tom

I had the same problem with UK2000 EGKK and ORBX England.

I changed the UK2000 AFCAD option from "Airline Specific" to "Generic" and the problem went away.

 

I have also had the ai_player.dll with neither installed.  It's not always easy to track down the culprit.

My Traffic has constantly been the biggest offender.

I changed the UK2000 AFCAD option from "Airline Specific" to "Generic" and the problem went away.

That would be interesting if this fixes the problem for OP too.

 

When I enable Gatwick Xtreme I start getting the error if I fly anywhere near the airport.

If TonyD's suggestion does not work and you have MyTrafficX installed, goto the MyTrafficX scenery folder and disable EGKK. MyTrafficX should always be located just above Propeller Objects in the Scenery Library.  If you have a commercial AI program installed, you might try to look for EGKK there too and somehow disable it.  I only know about MyTrafficX airports.  AI programs need to have their airports so that the AI can takeoff and land.  In MyTrafficX's case, they have some AFCAD's that are modified and really enhance some default airports. 

 

Best regards,

I had the same problem with UK2000 EGKK and ORBX England.

I changed the UK2000 AFCAD option from "Airline Specific" to "Generic" and the problem went away.

 

I have also had the ai_player.dll with neither installed.  It's not always easy to track down the culprit.

My Traffic has constantly been the biggest offender.

 

Hi,

 

This does seem to have fixed the error. However now the airlines don't park at the correct terminals. I guess this is something I can live with, since WoAI doesn't have a configurator like the payware products.

 

Thanks

Tom

There is an updated set of AFCADs for Gatwick on the UK2000 site  http://www.uk2000scenery.com/afcad/

I have not tried them but it might provide a solution.

 

I strongly suggest you get a copy of the freeware Simple Airport Scanner for locating duplicate AFCADs

http://www.scruffyduck.org/simple-airport-scanner/4584282795

 

Good luck

 I've spent quite a few hours looking into this in P3d as the ai_player.dll issue was very specific to certain airports only. At first I had it pegged on certain AI models, but not wanting to remove those models, I tried something else. Using traffic explorer I noticed that the ai_player.dll ctd would happen whenever a variant of a certain group of models would land and exit the runway. The a/c would stop at the holdshort clearing the active and upon starting to taxi again it would trigger the ctd.

 

 Using UK2000's EGBB, where EGBB is within the AI catchment area of EGKK I removed the runway exit holdshort nodes and the ai_player.dll ctd stopped occurring. I've since removed the runway exit holdshort nodes (exit nodes only, leave the entry point hold short nodes in place otherwise AI will NOT takeoff) from EGCC as well as I had noticed problems stemming from there also.

 There have been 2 or 3 other areas worldwide where I used to routinely get ai_player.dll ctd's and removing the runway exit holdshort nodes has essentially eliminated them.