Jan,

I must be dense in the head..... .......

I just cannot get this WED Gateway stuff to work. Getting the apt.dat or the dsf.dat into wed is fine, I make the changes I want, (signs in my case), use the shift-click like you said to get the dsf items up the hierarchy panel and then delete the major file heading so I don't get the hierarchy alert.

 

I then select validate again, and now I get the "This airport is too big" alert. :(  I rechecked the Apt & Dsf again and again, the numbers are all ok (KHWY apt of +30-80 and a dsf of +38-078.)

In WED I zoomed way out and sure enough, another airport is making itself known as part of the data, thus the alert. How in the heck do I get rid of the other airport? 

 

This process is getting discouraging and am about to give up and take up magic tricks :angry: ....hmmm maybe this is already magic, smoke and mirrors.

 

Anyway thanks for any guidance and hope this is the last time I have to bother you.

 

Chuck

Hi Chuck,

 

easy solution:

 

When you import a .dsf from the global airports scenery folder, it holds the data for a whole tile - usually 60x60NM (at the equator). Naturally that may contain data for several airports, on occasion.

 

You want to weed out the airports that you don´t work on.

 

After you did the shift-click and drag thing, zoom out the map, until you see all the objects that used to be in the .dsf. They will look like little clusters, concentrated in the spots where the various airports of that tile are.

 

They might still be all "selected" (showing little green crosses) - unselect them by clicking somewhere else.

 

Now you use the "rectangle-drag" to select all those objects that you DONT want - namely the other airport clusters. After selecting those, hit DEL to remove them (you will also see those entries disappear from the list on the right).

 

Keep doing that until only the objects remain that are on and about your airport.

 

Now save (to create a .xml file for future WED work) and export scenery pack (to create apt.dat and .dsf data to use in X-Plane) and optionally also upload to the gateway (make sure everything works swell first, though!).

 

Hope this helps, Jan

Got it Jan and thank you.  Works just great, will print out the procedure and paste it to my forehead.

Got airport errors to correct I made a few months ago so off to work I go.

 

Regards,

 

Chuck

Just a quickie out of curiosity - are ATC routes being added to all these new uploaded lego airports?

When LR finally improve XP10's ATC, we will benefit a great deal if the routes have been included from the start.

Got it Jan and thank you.  Works just great, will print out the procedure and paste it to my forehead.

Got airport errors to correct I made a few months ago so off to work I go.

 

Regards,

 

Chuck

 

Just thought of something... if you are trying to correct airports that are part of the new "global airports", its easier to download them directly from the gateway - you will have a folder that contains both apt.dat and .dsf file for ONLY THAT airport, so you can omit the pruning action I mentioned above...

 

Jan

Just a quickie out of curiosity - are ATC routes being added to all these new uploaded lego airports?

When LR finally improve XP10's ATC, we will benefit a great deal if the routes have been included from the start.

 

That is up to the scenery authors.

 

I usually add at least rudimentary ATC routes to my airports. Nothing elaborate, just a way to get to the main runway and parking spots. This should also speed up loading times, as X-Plane doesnt have to "create" ATC routes from the taxiway layout as the sim loads.

 

Once (if ever) Laminar gets a useful ATC system implemented the incentive to add ATC routes and traffic flow rules will increase.

 

There is nothing stopping anyone interested to download an airport from the gateway, add atc info (or any other improvement) and re-upload it afterwards, in fact this is intended usage. There is no such thing as "ownership" or "copyright" by the original author. All airports become common property. Of course one should strive to improve the airport, not totally dream up something.

 

I have seen airports submitted that were back-of-the-woods private airfields, and in X-plane they were decked out with approach lights etc... Laminar can´t check all submissions for authenticity and realistic data, so if garbage gets submitted, garbage will be in X-Plane.

 

Jan

Jan,

 

Good point on the d/l from the gateway, that's what I did and put it into a work folder separate from x-plane.

Pointed WED to that folder and all the imports work better, no hunting around for those orphan airports.

 

Chuck