WorldEditor 1.5 release candidate three is posted. Hopefully this one is a keeper. The show-stopping bug was: the error margin for near-but-not-connected taxi routes was too large, causing it to incorrectly flag parallel parking spots for aircraft. Two other minor bug fixes went in too.
If you find a bug in the release candidate, please report one ASAP on the X-Plane Scenery Gateway bug reporter.
Third time is very charming, working well from what I’m seeing. Woe be to the person who has to go through all the submissions that will soon be hitting the Gateway.
That’d be Julian. 🙂 We’re hoping this will be -less- painful for him because WED catches so much more stuff…
Got an update this morning for XP via Steam. Failed to load because several files in the X:\SteamLibrary\SteamApps\common\X-Plane 10\Resources\bitmaps\skycolors had a file size of ZERO (I restored them from a backup) and when it did finally launch, it has an airfoil debug/diagnostic/info screen displayed. Couldn’t see how to toggle that off. Please advise. Thx.
Saw there are lots of thing checked in Settings | Data Input/Output. Turned off wings/propellers, etc at the bottom right and that cleared up the view. Still, lots of other column 1 items checked.
Also, AI aircraft still will not spawn at airport with transparent runways:
0:09:44.675 D/ATC: User’s airplane appears to be at: KSNA (Orange County – John Wayne)
0:09:44.675 D/ATC: p=4 (N04XP) cannot start at KSNA: the longest runway is not paved.
0:09:44.675 D/ATC: Not using KSNA for spawning because it is unsuitable for p=4 (N04XP).
Bug was filed on this a while ago. Thx.
AI not spawning on transparent runways is a known design limitation; it will not be fixed for 10.50 or 10.51.
Ben and team,
I asked a question about LAHSO recently, and determined setting FLOWS for this was not beneficial. Now I’m coming up against another real-world situation that may be the same. Brisbane (YBBN) has Reciprocal Runway Operations RRO which breach the ‘rule’ that says airplanes cannot land and takeoff from different ends of the runway.
See //www.airservicesaustralia.com/aip/current/dap/BBNNA01-146.pdf for their nighttime “Mode 2” ops.
WED’s validation has just rejected my flows. I’ll hide them for now as I suspect there is no way around this rule. The Flow Authoring Guide also warns about this “mistake”. I also think it’s safer to have the rule and trap mistakes rather than let this rare (I assume) real-world situation through.
Is it worth hiding the flows for now, hoping for some way to bypass the validation in the future, or should I just delete?
Here I was thinking I could “Hide” an Airport Flow … only to find you cannot. Delete it is then.
Please take above as a comment, not a question 🙂
I just tried the case in the .pdf and it works. Let’s be clear:
Takeoff 19, land 1 is legal! Every case in that PDF is like this. KLAX is like this too. This passes WED validation!
Takeoff 19, takeoff 1 is ILLEGAL. I see nothing in the RRO info that would imply you can do this!
Whoops. I obviously made a real error trapped by Validation. Let me try that again!
Is it only me who have problems with scrolling in WED? If I click on the arrows on the scroll bars the scrolling leaps away miles from the airport
Bo, no it isn’t only you. I use the right-mouse click-and-drag only, but when I do use the scroll-bars (accidentally), using View/Zoom Package or Zoom Selection can quickly get you back.