I cut X-Plane 10.41 release candidate 1 last night – to get it, run the X-Plane Installer, pick update, and check “get betas”. Here’s a list of bug fixes.

10.41 is just critical bug fixes – fixes to crashes, and fixes to third party aircraft that didn’t make 10.40. No new features, no new airports. The goal here is to get these fixes out rapidly.

If your third party aircraft worked in 10.36 and does not work with 10.41 release candidate 1, please file a bug ASAP. We do not have any remaining open bugs with aircraft compatibility.

Steam users: we’ll cut a Steam version of 10.41 in the next few days if we don’t get any other reports – it’s the same plan as last time.

A number of users have asked me about why a build is sometimes named 10.40r1 or 10.40. Here’s how it works:

  • A build of X-Plane is called a “release candidate” if we think at the time we create the build that it could be an official release – e.g. there are no known bugs.
  • Release candidates get an “r” in the name, e.g. 1040r1 is our first release attempt for 10.40.  The previous builds had a “b”, e.g. 10.40b6 is the sixth beta of X-Plane 10.40.
  • If the release candidate doesn’t have show-stopping problems, we make it official – at that point every user gets that version when they update, even if they don’t have “get betas” checked.
  • We do not re-cut the build or rename the build. Instead, the “r1” remains in the name of the product forever in the Log.txt file and if you pick “Get Info” or “Properties”. We need this so that tech support can identify someone using the official release versus an older release candidate.
  • The version on the startup screen simply reads 10.40 – most users flying the sim don’t care about r1 or r2.

In order to remove the “r3” or “r1” from the long version of the build name, we would have to re-cut the build, which would mean a needless update and download for everyone, but more importantly, there would be a small but non-zero risk that we introduce a bug in the final version that was never tested in the release candidate.

You can see this strategy on OS X too – the OS version is 10.10.5 in the about box, but if you use the System Information App you get 10.10.5 (14F27) – that last cryptic number is the build identifier – it’s sort of like our r1 or r2.

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.

11 comments on “Please Try X-Plane 10.41 Release Candidate 1”

  1. Hi Ben,
    way better than 10.40 – no more horrible scenery stuttering every second and strange behavior of some planes is gone also.
    Thank‘s a lot
    Matthias

  2. Just curious, is the effect of issue 2456 (“Fixed black-outs during descent at low N1”) a magenta “In-Flt Start” indication on the FlightFactor B752? I’ve never seen that before my first flight with that aircraft under 10.40 last Friday. I thought it was an issue with the aircraft, not X-Plane. Engines were still running fine and responsive to thrust changes and I didn’t notice any disturbances other than that indication:

    Screenshot 1
    Screenshot 2

    The sim crashed after landing when I had to break on a hold line (I also submitted a crash report ~2048z on Oct 2) but that’s an older issue which has happened to me at least 5 times, ever since I got X-Plane last year (in both FF 752 and FJS 732, but this could be random as they are the two planes I fly most). So it’s unlikely to be related.

  3. Ben,
    I don’t know what the “cockpit stability button is”, but I filed a bug for the always “moving a little bit around” display.
    I thought maybe this has to do with this strange button and investigated again in looking for the settings.
    In view I found the “Cinema Verite” selected, and that selection was the reason why.
    Deselecting this show effect (?) allows me to fly again without getting ill 🙂

    So maybe I hit Shift-C by accident.

    Please close my ticket and thank you for this great Sim!

  4. I filed a bug report a couple weeks back when the Steam version was released regarding taxiway guard lights not being visible. Would I expect an email reply if that was not found to be a bug or ??? I included my lights.txt file in case it was something specific to me but I had checked with one other scenery developer and he said he noticed it as well in 10.36. Thanks Ben.

  5. How about the Precision Flight Controls Cirrus console driver not working at all since 10.40b5?

    1. Please file bugs on the bug reporter. There was a known issue with the PFC plugin that was fixed late in the 1040 run and noted in the release notes. If you still see issues, please file a new bug.

  6. Ben, for a long time the “Recent Release Notes” link on this website is NOT working, it simply takes us to “page not found” on the official X-Plane site.

  7. Hello.

    I am using PFC Cirrus C2 console, avionic stack and prof rudder pedals. After updating to X-plane 10.40 (not Beta versions) there is absolutely no communication between the PFC hardware and X-plane software. Previous version of X-plane software: no problem.

    Any solutions?

    Michael Nielsen

Comments are closed.