The runway should be 02/20.

No work-around right now.

nb I am converting FSX packages so I am only using the smaller demo version (space reasons on my MBP). I have the full monty 10.50 on my Mac Pro’ s.

Bug filed for WED.

Maybe found the answer…says longest runway is not paved. I use transparent runways because I use a custom texture. Any way around that? Thx.

As I said above, I did this and since the debug setting is not persistent, it seems to indicate no additional information. That is, I set it after the AI have been spawned in-flight, never land at the airport and never spawn ON the airport. Is there a global setting for the airport that I missed? Worked before 10.50, no longer works once I use the new WED. Clearly I’m missing something simple. Thx.

Right – it does not apply to the gateway, and we had to pick our battles – we didn’t have enough dev time to put every single validation possible into 1.5; we focused on ones that were causing serious problems in real use.

If you are making custom scenery, you should absolutely read _X-Plane’s_ log and make sure there are no problems.

The reason why it’s so important to get validation into WED for the gateway is to _require_ that authors address their errors before sending them on to the repository.

Turn on the art control atc/debug/log_spawn and you can see how the AI is deciding where to put aircraft.

Ok, after seeing this screenshot: on my iMac the ATC lines look thin as ever in my WED1.5b3 version, no wingspan markings or wheel thingies… RWY segments are still red (or white, if I mark the segment ‘runway’), not blue… file a bug, I presume?