EXPERIMENTAL USE ONLY!!! -- [What?] -- Login to add public annotations [How? >>YouTube].

WorldEditor 1.5 release candidate 1 just went up today. Please try it soon; we’re going to make this the official version for uploading to the gateway if no one finds any problems. This build fixes the last known validation bugs and has a bunch of improvements in the validation text messages; Jennifer, Ted and Julian did a complete review of the error messages (there are over 75!).

X-Plane 10.51 release candidate 1 should go up Monday or Tuesday; it has new airports and a few hot fixes for problems we found after shipping.

If you are the author of payware that won’t open due to an airfoil self-check failure, this is just a warning in 10.51, so your users won’t be frozen out.

But you should also fix the problem, as the self check fails only if you enter physically impossible values for the airfoil.

Update: a number of users have reported crashes on export in the release candidate. If you see a WED crash on export or validate:

  • Please include a link to the scenery pack causing the crash.
  • If you are on Windows and can provide a link to a minidump, that would be really useful. (You’ll have to do a link – even zipped, the minidump files are huge.)
  • If you see a crash on a Mac, include the full text of the Apple crash report.
  • If your pack requires tons of libraries, please indicate what libraries are needed.

Update 2: WED 1.5 release candidate 2 is out and fixes this crash, which is a crash on validate of a ramp start with no airlines, Windows only.

About Ben Supnik

Ben is a software engineer who works on X-Plane; he spends most of his days drinking coffee and swearing at the computer -- sometimes at the same time.

8 comments on “WorldEditor 1.5 Release Candidate 1 – Try It Soon!”

  1. Attempted to export, CTD using RC1. Been working in 1.5b4 two days straight and it’s been solid. First attempt to export a custom pack crashed.

    Faulting application name: WED.exe, version: 1.5.0.4, time stamp: 0x57e55212
    Faulting module name: WED.exe, version: 1.5.0.4, time stamp: 0x57e55212
    Exception code: 0x40000015
    Fault offset: 0x004986af
    Faulting process id: 0x384c
    Faulting application start time: 0x01d216199b4c3055
    Faulting application path: I:\SteamLibrary\SteamApps\common\X-Plane 10\WED.exe
    Faulting module path: I:\SteamLibrary\SteamApps\common\X-Plane 10\WED.exe
    Report Id: 3d323bf1-bb4a-4500-9427-aca3246bd762
    Faulting package full name:
    Faulting package-relative application ID:

    1. Please report a bug – if WED crashed, use the gateway bug reporter to file a bug. If X-Plane crashed, use the X-Plane bug reporter.

      Problems mentioned on the blog and not filed as bugs will -not- be fixed.

  2. Hi Ben,

    10.51 on Monday? I thought the plan was for all gateway artists to wait for a stable WED 1.5 and then upload their airports with new 10.50 features – so that they can be incoroporated into 10.51?

    We need a few days time for that – and Julian will have to check and approve the uploads – possibly hundreds of airports!

    Can we at least have a week or so? (Never thought I would beg for an update to be pushed back ;-)) )

    Cheers, Jan

    1. The airports in 10.51 are the ones that were uploaded -during- the 10.50 beta using WED 1.4.1. In other words, it’s the remaining pre-WED-1.5 airports.

      The amazing thing is: there are, like, 500 of them.

      We will need to do another, separate collection for WED 1.5-based airports. But this at least gets out the back-log of pre-1.5 airports that we were sitting on.

      (The rate of gateway contributions continues to surprise us. My long term goal is to set up X-Plane’s installation tech to distribute airports using a separate channel from the sim itself, so that gateway artists are not dependent on simulator releases, and Julian can launch airports a lot more frequently. Our original idea was “hey, it’s not hard to cut an X-plane patch with new airports”, but in practice the timing is always inconvenient for some reason and the airport submission rate is very high.)

      I do -not- know what the release vehicle will be for 1.5-based airports.

  3. Cannot even validate a scenery with v1.5rc1 which I created with v1.5b4 yesterday. WED instantaneously crashes.

  4. I installed wed_win_150r1 , and windows crashes whenever I try to save the file! 1.5 Beta4 and all other Betas worked fine! Is anybody else having this problem with Windows? Should I file a bug report? If so, what info is needed and where should I file it?

Comments are closed.