Hi!I wonder if anyone knows/has experience of FSX with regard toAFCADS and AI traffic?Can you use the "normal" TTools and AFCAD2 for FS9, oris it different?Can you use the traffic.bgl file fron FS9 and use it in FSX?Are there AFCADs to modify gates, parkings, etc.?Grateful for info.........Thanks!Hans HermanssonSweden

There have been several posts about this that will come up in a forum search of Avsim.Here's one:http://forums.avsim.net/dcboard.php?az=sho...ing_type=search

First you wil have to do everything in FS2004, then copy the files over to FSX.After further testing we most strongly recommend you do NOT use FS2004 AFCAD files in FSX.The AFCAD program has the following statements written into every file it creates:Now - this is going to delete almost every change made in FSX from the FS2004 airport - and people have reported issues with radios not working at some airports because the frequencies are different.Some other things which now disappear from FSX if an FS2004 AFCAD is used at high scenery setting levels.Airport Control TowersBlast FencesAlso - the ILS may not line up with the runway any longer,Taxiway Signs may be in the wrong place,Buildings may be in the wrong place,Parking spots may be in buildings - or away from buildings,Ground traffic may run through buildings or aircraft.There is at least one developer group working on a scenery tool to replace AFCAD.

>There is at least one developer group working on a scenery>tool to replace AFCAD.Are you at liberty to say who this is?Matt

I read a statement over at the Projectai forum, that they have a small group trying to create something like that.

I have already seen in this forum and others where people are saying to copy a FS9 AFCAD to FSX without the understanding of what will happen.The FSX world scenery has moved a few meters. If you copy a FS9 AFCAD into FSX nothing will align properly. That is the first problem.In order to see additional problems you must Set the slider for Airport vehicle Density to MaximumSet the slider for Scenery Complexity to Extremely Dense1. Control Tower is now gone if the airport has one2. Any Red Blast fence that sits on the airport or is part of the parking ramp is gone.3. All Airport Buildings are in the wrong place based on the af2_xxxx.bgl that was made with FS9.4. All Taxiway signs no longer align and some are sitting in the middle of the runway. Most windsocks are on the runway also.5. All the ILS GUIDS are no longer aligned with the threshold of the runways including the antenna buildings6. Many airport buildings are sitting on taxiways.7. Ground traffic tracks cause vehicles to drive right through buildings and on the grass textures8. Airplane parking stands misaligned9. etc.These are just a few of the visuals that no longer align or have been removed by AFCAD.If by chance a Airport has updated freq's, changed runway numbers, night apron lighing, changes ILS Navdata, etc. this is the unseen scenery and AFCAD blocks this and replaces the default FSX data back to what FS9 had.Also if someone tries to update a more complex scenery airport (using a FS9 AFCAD) like KATL, EHAM, etc., all the default animated Jetways are removed. This is because FSX links the Jetways to the parking spot and AFCAD knows nothing about that type parking spot or its XML data. This list is more comprehensive and what is removed or corrupted if you copy a FS9 AFCAD to FSX.1. Animated Jetways2. BlastFence 3. BoundaryFence4. Airport Control Tower5. Alternate Threshold to indicate international rather than US Threshold markings 6. Alternate Touchdown to indicate international rather than US Touchdown markings 7. Alternate Fixed Distance to indicate international rather than US Fixed Distance markings 8. Alternate Precision to indicate international rather than US Precision markings 9. Leading Zero Ident to indicate runway numbers have a leading zero (for runway numbers 0 to 9) 10. No Threshold End Arrows to ignore Threshold End Arrows.11. Runway Designator If this value is set, the Secondary Designator (the runway in the opposite direction) is set automatically. 12. Primary Designator If this value is set, the Secondary Designator is not set, but should be specified next. Same values as designator. 13. Secondary Designatior Opposite designator to primary designator. 14. Primary Closed is closed with