We can accept airports from OE if you can get them into the format we need.

But we are _not_ accepting road network edits. There is not a sane way to do this for overlay airports right now.

It is not our plan to share the XML at this time.

Hi Dozer,

A few things:

1. We _do_ intend to extend the airport library. We think we can get more detail and variety around the existing texture set!
2. The goal of the library is to provide nice looking art assets, reasonable plausible approximations of the real world, but NOT to exactly reproduce every airport in every detail or replace custom scenery. So there is a limit to how much extensions will affect the library.

So with that in mind, if there are classes of architecture that are totally missing, or ramp equipment that is missing, please file a bug – include a link to a pic of the real thing. The cases you’ve brought up sound valid…I just don’t want people emailing going “you have a brick tower with 3 floors, one staircase, and dark tan masonry, but I need two staircases and light tan masonry.”

Second, re: AGP vs OBJ, please file a bug indicating the OBJs that you want ‘released’. The default setup is to assume that the AGP cannot be ‘stripped for parts’ – in some case we can be less conservative and release the OBJS, in others the OBJs don’t make sense on their own. I want to avoid the case of ‘release everything now’ because we need to not rename/change those OBJs that are publicly in the library or we’ll break people’s airports. Hence the need for some caution and examination.

Cheers
Ben

Does that mean we could have acces to the XML wed file from older contributors ?

That would make sens to re-use the grouping, etc… from previous contributors…

Cheers

I’m currently flitting around northern South America replacing taxyways in WED, in the kind of airport which can operate 737s but only one at a time. For instance, the terminal at SKCO: http://commons.wikimedia.org/wiki/File:La_Florida.JPG

Looking through the default scenery objects, it seems the focus is for much larger airports. There’s several huge control towers, but no small 3-storey ones. More shocking- there appear to be no air-stairs?? Plenty of choices of jetways, but no truck with steps. Possibly the most ubiquitous ramp vehicle! I mention these two just as examples – will you be dragging Tom away from the MU-2 again to make some more stock assets some time 😉

Kind of related, is there a way to separate an object from an .agp? I’m often finding a useful asset locked away inside a scene I can’t use. For instance the vintage hangar_tower.agp – at SKCO I’d like to use just the tower but ditch the hangar and paving. If there isn’t a way to do this while remaining a viable candidate for the global scenery database, perhaps you could consider aiming to make the constituent .objs available along with the .agps? As it is, I used the hangar-tower.agp as a substitute for the terminal building but the character isn’t quite the same.

This is a really awesome direction that you’re going with the scenery. It’s fun and quite cathartic to drag taxyway bezier curves around!

We don’t have any such rule now. I would say this: at minimal object settings, include only objects that are necessary for operations.

Yes, I think so!

I was wondering if there is a rule of thumb regarding the “tuning” of the number of airport objects for the different detail settings, in other words:

.What should be the ratios of objects number for max (“extreme”) vs min (“default”) settings? 10:1? 100:1? 500:1?

.Do you advice a fixed ratio (e.g. 10-20-40-80-160-320), or a fixed amount of added objects (e.g. 10-70-130-190-250-310) between consecutive detail settings?

Daniel