Would perhaps an “Are you sure?” message before exporting a scenery without an exclusion zone be reasonable? It will at least serve as a reminder.

Hi Jan,

The naming thing is a little messy. The problem is that the scenery packs are stored in a mostly opaque form on the server – WED has the brains to understand them, but the gateway relies on meta-data that WED passes in. This makes the gateway itself much much simpler; if it had to be a full scenery editor it probably still be in development. But it means that when there’s a problem like names we can’t do “simple” things like mass-rename every single pack – the name is baked in.

I’d say any validation warning you think should be in there, file a feature request. For exclusion zones, that one’s tricky – it’s usually a bad sign if you don’t have them but WED can’t know the author’s intent, so it probably shouldn’t stop someone from exporting.

I welcome tighter validation checks – it would be awesome if these could also be extended to “checking the airport name” with the Gateway database (warning: Your airport name differs from the database airport name!) and maybe add some warnings regarding exclusion zones and airport boundaries “warning: your design has no exclusion zones”, “warning: your design has no airport boundary”… I will add these suggestions via the Gateway suggestion system.

Thanks for making WED better continuously!

Jan