One area I've recently jumped into in scenery design is customizing airports and I'm finding it to be a frustrating and daunting process. There are marvelous freeware tools such as AFCAD and SceneGenX for manipulating runways, taxiways, nav aids, etc. but no one of these tools can be used to completely control all of the objects within the boundaries of an airport. The reason for this is that the objects for each airport don't exist within the same .BGL file. Most do but some are scattered about in different scenery files without some common naming convention or comments identifying what airport they belong to. Most times they are only identified by the cryptic GUID of the object. Designers are forced to decompile all of the scenery files one by one and look for object geographical position that falls within the desired boundaries. SceneGenX attempts to do this but has some holes in its logic.I'm curious as to why MS can't encapsulate all airport-related information into one central file. I'd think it'd make things easier for MS designers as well as the after-market bunch. Thanks,Art Martin

I think rather than putting all objects in a single file for a particular airport, I'd rather see them document what objects are available (with graphics), and make it easy to use them in other scenery. I do understand how and why they end up in separate files. Happens over time in my sceneries, too, no matter how hard I try to plan up front.Thomas[a href=http://www.flyingscool.com/FC_StartJava.html] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)