Hello Gang!I have spent the last several weeks re-building my traffic in FSX and customizing all my AI Traffic the way I had it in FS2004. For the most part, everything has been working allright until recently, I noticed that I can no longer launch any flights from TJSJ (Luis Munoz Marin Intl. airport in san Juan, Puerto Rico). After a lot of investigation and re-installing FSX from scratch (thinking it may have been a corrupted .bgl or a bad texture replacement file, I realized that the culprit fil was my Traffic.bgl file. On my installation of FSX, this file contains all my AI airline traffic; I renamed the original file and saved a backup. Things work allright with the back when I re-activate it, but somehow, my custom Traffic.bgl file has something messed up. The problem seems to be related to TJSJ because any other part of the world loads just fine - the minute i want to start form any airport in Puerto rico, "BAAMM" Windows error and back to the desktop.Could it be that the Traffic.bgl file is getting too big and FSX cannot handle it?Please let me know your thoughts.Thanks!Sincerely,Dennis D. Mullert

Hi Gang!As a follow-up, I have used TTools COmpanion to check all my flightplans and files rtelated to this Traffic.bgl file and everything checks out OK. I have nailed the problem down to something related to flights in or out of TJSJ on my traffic.bgl file but FSX does not tell me what the problem is when it crashes.Any ideas?Sincerely,Dennis D. Mullert

Might I suggest that you don't compile everything in one single, gigantic .bgl file?It would make troubleshooting much easier - not to mention faster to compile! - if you were to break the traffic into smaller, logically organized .bgl files... ;)

It's hard to say based on what you posted. How exactly are you making your traffic.bgl(s)? Are you using TTools, or are you using the new SDK tools?I would not use TTools to make traffic in FSX.Well, you can, of course...but TTools-created .bgl's could be a potential issue.I know that the FSX TrafficDataBaseBuilder.exe will throw an error when there is not enough parking at an airport, but not a CTD like you've got.I have built most of Northwest Airlines schedules for FSX, using the FSK SDK tools, and never had a CTD with it. I suggest not naming your traffic file, traffic.bgl. Rather, I'd name it something else. How many megabytes size is your file?Are you missing any textures for any of the AI planes? How have you referenced a particular aircraft? Missing textures are a known sudden BSOD or CTD causer.RhettAMD 3700+ (@2530 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 3-3-3-8, WD 250 gig 7200 rpm SATA2, CoolerMaster Praetorian

Hello Rhett!Thanks for your reply!You guessed correctly. I have been using TTools to compile the file - maybe re-naming it is a good idea for starters. How exactly would I be able to compile my traffic file using the FSX SDK as you mention? I've never used it and would not even know where to start!!!!! Help if you can!!!Funny you mention NWA Schedules - I believe that my grief started around the same time I installed NWA's schedules.Thanks!Sincerely,Dennis D. Mullert

Hey Bill!Thankls for responding!It's funny! When I had 2004, I had my traffic files broken down into 4 or 5 separate traffic files, as you mention; then came FSX and one day I asked if one big, happy file would be better than several and for the most part, I was pointed in the direction of having one big, happy file. I thinkl I tend to agree with you in the approach of having it all on several files.I'll give it a try.Sincerely,Dennis D. Mullert

To make traffic bgl's to FSX standards, at the present time, the only method I know of, is to use FSX's SDK.I don't know if that is the reason for the problems you're having, but it couldn't hurt. I agree with what Bill L. said. I question the wisdom of a 23 megabyte .bgl file, anyway. For lookup purposes alone, one would think that would slow things down, especially in a fragmented drive.You can simply rename the trafficAircraft.bgl file to trafficAircraft.bgl.stock and that eliminates all stock AI from the sim, but doesn't touch the default file, which is good. You don't want to mess with the stock files. You can always bring the stock AI back easily to supplement your custom AI, if you want. Most of the hard-core people don't like stock AI. Myself, I don't mind GA AI that is stock.Then I have my nw_traffic.bgl file in there. (sceneryworldscenery)I guess it could go in Addon Scenery but I haven't messed with that.Here's a short process to make traffic bgl's for FSX:Basically you create a couple of text files, run it thru the compiler, and you're done. Eventually there will probably be things like TTools for FSX, but not yet.Here's a code snippet from my nw_schedules.dat file:B744-1,N181US,1,ONE_WEEK,IFR{50640,KMSP,380,1451925,RJAA,370,3}B744-1 is a Boeing 747-400, paint scheme 1.14 is the flight number from the Narita to Minneapolis leg.The Narita to Minn leg leaves Saturday at 6:40z. The "5" in the '50640' string means Saturday. The 0640 is departure time in zulu.The Minn to Narita leg leaves Saturday at 19:25z and its flight number is 3.And here is the command line I'm using with TrafficDataBaseBuilder.exe:trafficdatabasebuilder /Output=nw_traffic.bgl /Airports=nw_airports.dat /AircraftTypes=nw_Aircraft.csv /Countries=countries_regions.csv /Schedules=nw_schedules.dat /Autoschedule=no /StatsDir=G:TEMP2As you can see I am using a lot of switches, not all of which are required. For example, I have my own nw_Aircraft.csv file, in which I only include those aircraft that Northwest actually flies.You can use all of our FS2002/FS2004 AI models perfectly, like EvolveAI, AI Aardvark, and others. To get FSX's jetways to automatically pull up to the plane, there are some mods that need to be done in the aircraft.cfg file.RhettAMD 3700+ (@2530 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 3-3-3-8, WD 250 gig 7200 rpm SATA2, CoolerMaster Praetorian

I've been having some good luck using World of AI and the new version of their installer which works with FSX. So far so good. You just have to wait patiently for them to catch up with airlines you want, but they have quite a lot.http://www.world-of-ai.com/Lee

Hello Gang!Thanks to everyone that has so far kindly responded.This problem is actually "mushrooming" into something different;Here's the deal:1. After further investigating and based on your input, I don't think that my Traffic.bgl file is corrupted or is the problem and here's why:When I load up FSX on TJSJ at Night, Dusk, or Dawn, everything loads perfectly, including all of my AI traffic - no problems. Whenever I try to load up FSX at TJSJ during the day, that's when the "Dump" occurrs. WHat in the world could be causing this? I don't any scenery for Puerto Rico loaded or any season changes or anything - I have a pretty virgin installation of FSX so far.Thanks agaon for any input!Sincerely,Dennis D. Mullert

>To make traffic bgl's to FSX standards, at the present time,>the only method I know of, is to use FSX's SDK.>-SNIP->Here's a code snippet from my nw_schedules.dat file:>>B744-1,N181US,1,ONE_WEEK,IFR>{>50640,KMSP,380,14>51925,RJAA,370,3>}>>B744-1 is a Boeing 747-400, paint scheme 1.>14 is the flight number from the Narita to Minneapolis leg.>The Narita to Minn leg leaves Saturday at 6:40z. The "5" in>the '50640' string means Saturday. The 0640 is departure time>in zulu.>The Minn to Narita leg leaves Saturday at 19:25z and its>flight number is 3.> Kee-RIST...couldn't they have made it more cryptic? I am not imnpressed with M$'s SDK implementations and from what I see here, I'm not likely to be enamoured with their traffic builder. I'll stick with my FS9 .bgl's which are working just fine in FSX as far as I can tell. I've only imported 10 of the 53 FS9 traffic files I have created but for now that keeps my "world" fairly full of AI. I seriously doubt that I would attempt to convert those 53 files to the FSX format using M$'s tools. I'll just wait and hope someone writes a more intuitive TTools-like package. Paul