X-Plane 10.11 release candidate 1 is now available online – run the installer, and update with the “get betas” button checked to get it.  This is a small bug fix build to get new Japanese strings out; most of these bug fixes were coded during 10.10’s release candidate period but held to keep the sim stable for DVD pressings.  It’s a small update.

EDIT: Please stand by, the upload did not work right – it should be available later tonight.

EDIT 2: Okay – now we are live.

We may do one more small bug fix release (e.g. a 10.12) before we get to 10.20, which will introduce 64-bit and have a longer beta period.  64-bit porting is going well and I am happy with the progress so far.

What About WED?

A number of WED users have reported a really nasty bug: while mousing around, WED would put up a fatal error dialog box and quit, with work lost.  This bug sucks, and what was worse, no one could find a good procedure to reproduce it.  The steps appeared to be “do some work, get a lot of changes ready, click, lose work.”

That is, until now; the other day Chris round the reproduction case.  I now have a fix, so I will try to cut a WED 1.2 beta 2 in the next week.

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.

18 comments on “X-Plane 10.11 and Other Release Plans

  1. Thanks for the update Ben, glad 64bit porting progress is going well. Based on the progress, do you see a beta coming before Thanksgiving?

    In regards to your 64bit post weeks ago, and Mac “not so fast” due to the memory limit being gone, would it be beneficial to have as much RAM as possible?; in order to maximize rendering/fps, and or flow of multitasking various apps on the Mac at the same time with x-plane loaded

    Thanks

  2. Good for the new WED!

    By the way… when we’ll be able to export “lego” definitions in airports in order to XP10 users can upgrade them from data.x-plane.com?

    Cheers,
    Cestomano

  3. Thanks Ben,

    It’s a long shot, but will WED 1.2 beta 2 have the secret roads function enabled? 🙂

    Al.

  4. Gentlemen,

    To make the story short ….

    I am happy to hear about the 64 bit work and small bugs fixes but…. the cities look the same as they did when version 10 started , namely , like crap ( sorry for a strong word)

    I have been asking about it for a long time and answer was always that it is high on the priority list.

    Now, 64 work is in progress but the tall buildings still appear like after a nuclear war…lol,lol

    I am flying in New York and Atlantic City area and see only couple of buildings.

    Isn’t the proper look of the cities more important than tweaking shadows , reflections and moving on to 64 bit for those who can run it?

    Keeping my fingers crossed.

    Cheers, Andrzej

    1. As I stated in a previous post, we are looking to release a city update _with_ 64 bit so that the increased memory load of additional auto-gen definitions doesn’t cause memory failures.

  5. Ben,
    Glad the 64bit porting is going well and looking forward to it. With that being said it is important that as many as possible of the bugs be removed before going onto 10.20. I have taken the same aproach with my Xsaitekpanels doing a feature stop to remove any current bugs before going on to 64bit.
    Thanks Bill

  6. Will 64bit be a complete reinstall or just an update as indicated by 10.20? Furthermore, would a 64bit platform make way for larger texture files such as 4092×4092 duo to those extra memory allocations?

    1. It will just be an update, e.g. 10.20. No need to re-install. You’ll do the update and have two apps/EXEs instead of 1

      X-Plane already supports 4096×4096 textures as of 10.10.

  7. Hello Ben. congratulations for all the work and much encouragement.
    Try to contact you by email to your address but I’m afraid that’s impossible, I guess you have no time.

    But I still worried about the bug in the transition from the cloud layers can not find solution anywhere.

    When you think that you fix this?

  8. Hi ben. Sorry if my question has angered you. was not be my intention. You can tell my the reason for this? Thak you and sorry again.

    1. It didn’t anger me – I just do not have time to discuss this bug with you right now. It is not a bug I am working on right now, and there is no new information on it to post.

      1. Well, Maybe not angry, But It Sounds nasty enough. Having a bad day?

        I have those too, but I don’t find the need to snap at someone on a blog or forum.

        I thought that was the job of the nasty railway simmers.

        disappointed.

        1. It wasn’t me snapping at him – it was just _brief_. As I said in my previous post, I _do not have time_ – either to address his bug report immediately or to have a discussion about it.

          If you are going to interpret a brief reply as snapping at someone and be disappointed, I don’t know what to do; I do not have time to write long and detailed responses to every email and blog comment I receive and still get work done.

Comments are closed.