Thanks – we’ll fix it.

The check box is on the airport in WED.

In this doc:

ATC Taxi Route Authoring.html

this line:

Size

The size field limits traffic to aircraft small enough to fit on that taxi route. X-Plane will allow traffic of the size specified and one size lower–i.e., set this field to “B” to allow aircraft identified as size B and A to use that taxi route.

Guide for Ramp Starts.html is correct.

Thanks !
Terry

This is a design limitation of X-PLane. X-plane can’t model clearance delivery services _except_ in the case of a towered airport. This includes relays and picking up clearance by phone and being given a departure window.

Someday X-plane will allow IFR departure from untowered airports, and then we can start to allow this kind of thing; until then all you can do is take off and pick up a popup clearance.

This might be a doc bug. “The size and one smaller” applies to RAMP positions – that way we don’t park a Cessna 172 at a class E spot for a 747. For taxiways, it’s the size and ALL smaller.

If the docs got that backward, send me an exact link and we’ll fix it.

Colocated points will be fixed in 10.51. Generally, file x-plane bugs in the x-plane bug reporter and WED bugs in the scenery bug reporter. But we’ll move them if it turns out the bug is in the wrong place.

Hi Ilias,

Like I said, the problem is in our engine. If you give us a nice high res triangle mesh, we have to merge the two meshes – merging two TINs is non-trivial and we don’t have code that does that.

Right now for each validation, an object involved is selected. Use the zoom-selected command to go see it!

We do have plans for a better validation error display, but this is not going to go into 1.5.

I have already filed a bug report for this but was curious about the rationale.

When validating a non-towered airport I was instructed to delete all ATC frequencies. Is this due to the state of the ATC system? If a non-towered airport is within radio range of ATC, clearance delivery should be available. Yes?

Cheers