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

X-Plane 10.40 RC2 is out now. This RC has a few key bug fixes:

  • RC1 had a bug in the file scanner that would cause some key frame tables in OBJs to be misread. This could cause add-ons to look wrong.
  • There was a shader compile problem on Linux, definitely due to bad GLSL.
  • I tracked down an out of bounds memory read in the autogen engine.

At this point I believe there is going to be an RC3 tonight because:

  1. I have a reported work-around for auto-update failures on Windows 10. That’s pretty high priority – if auto-update doesn’t work, we get tech support emails from now until doomsday.
  2. There’s a spurious error message in the log. This should really just be considered cosmetic, but for some reason y’all are really, really, really concerned about error messages in the logs* so if we don’t fix it, my in-box will fill up.

Steam users: there will not be an RC2 on Steam – if RC2 is indeed replaced by RC3 within 24 hours, then we’ll wait for RC3 to go to Steam. The reasoning here is the same as it was with RC1.

 

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.

17 comments on “X-Plane 10.40 release candidate 2”

  1. Are you talking about this as the log error message?

    “Failed to find resource ‘test/AGtrees_test.for”

      1. Hahaha, I was considering asking that same question. Seriously though, the concern about log reports is a symptom of high interest in customization, some of which is to work around bugs or non-simulated items, which then might be bypassed in updates because of the lack of transparency in bug reports and the lack of an updated/skipped log.

  3. Why do you keep putting back the beta for steam version? first you said couple of days after RC1 then you said in another post 2 days after RC2 and now again you change it RC3 then only 24hrs or maybe more after that.

    1. As I have said before in previous posts: the decision making process is this:

      10 Cut an RC with the latest best stable 1040 code.
      20 Wait 1-2 days, depending on whether it’s the weekend.
      30 If bugs are found, fix bugs and GOTO 10
      40 Cut the steam build

      So twice in a row we’ve hit that “bugs found” case and gone back. This will continue to happen until we have an RC that remains a _good_ release candidate for at least 2 business days.

      1. Hi Ben, once again sorry for off topic, data what site do you use data for roads and Railways which will be present in the landscape of X-Plane 10.40 ?
        If OSM is : 1) based on the standard map 2)Map for cyclists 3) Map Transportation 4)Mapquest open or 5) Humanitarian ? In OSM there are 5 layers I wonder what is used as the basis of the terrain in X-Plane 10.40.

        1. The OpenStreetMap layers are a product of the OpenStreetMap map renderers – they all come from a single unified source of vector data. We download the entire vector data set and select the tags we want.

        2. For some reason, I can’t reply to your second post, so I reply here.

          There really are no “map layers” in OSM data. It becomes more clear if you download an external editor such as JOSM, download an area around your neighbourhood and take a look at the raw data instead of a rendered & filtered product: You will find that there is much more data (at least in well-mapped parts of the world) than is visible on rendered maps. Those map layers you speak of are only graphical representations of a select subset of data, where tags trigger certain graphical styles (main roads, foot ways, building shapes, icons for businesses etc.). What you see as a “transport map layer” is nothing but a different graphical style to a different subset of tags (e.g. public_transport and bus=yes renders in a different color/line style than train=yes but may not be rendered at all on the default map layer). For example, in my area I found that telecommunication hubs have been mapped and while they don’t show up in any rendered map layer I am aware of the data is still there and ready to be processed if needed. That means I could go ahead and create some application (or map) using that information. You never see the full data from just a rendered map; there’s always more information available in raw data. All maps based on OSM share the same data source. And that’s the way scenery is being generated from OSM as well: Import the data (not a pre-processed map), filter for everything you want to process (roads, buildings, railways, power lines, …) and instead of rendering a graphical map turn it into a data format X-Plane understands.

          BTW, if you find some place you know to contain any errors or to be incomplete, you are welcome to edit OSM data similar to editing an article on Wikipedia. The next time map layer generation or X-Plane scenery generation fetches an update from OSM, your input will be incorporated.

    1. All time estimates are estimates. If I say 24 hours and it turns out to be a week and you get bent out of shape, then I need to stop posting estimates.

      1. sorry Ben but I am just getting angry because your building up steam peoples hope then breaking them down. The whole reason I asked this is because it says a few days,I just feel like steam users are getting punished for owning the game. As you can see I am really sorry .

        1. This is why we can’t have nice things.

          If I tell you our estimated date to post something, and that date changes due to the development process, then I have three choices:

          1. Try to explain _why_ the process works the way it does. Maybe you will then understand what is happening and not be angry, but understand that we are trying to get the RC out as fast as possible. (You might notice that when RC2 turned out to also be broken, I cut RC3 on Saturday and got it posted within 24 hours instead of waiting until Monday. This tightens up the schedule.)

          2. Continue to post estimates because some readers of the blog can understand them, and end up with angry users or

          3. Stop posting any time estimates, and when people say “when will it be done” I can say “we do not pre-announce the release dates of anything, ever.”

          So you and the X-Plane user community have to decide whether you can hear and understand detailed information about the development process that other companies might not be so candid about. If you cannot, then I will stop posting it.

          I’m not sure how the punishment part comes in – I’m not going to intentionally post dead release candidates on Steam.

  5. The more sophisticated the plumbing the easier it is to stop up the drain!
    LOL
    Take your time id rather see it done right then have a bunch issues!

  6. Ben, I think your estimates are perfectly reasonable. I am still inclined to buy myself a non-steam download version to cut my waiting time (and get rid of the dlc processes).

Comments are closed.