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

A new 10.22 beta is out – it fixes a crash-on-startup in beta 1 that some users were seeing.

If you can’t auto-update (because the sim crashes before the update message appears) simply run your installer, pick update, and check “get new betas”.

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.

14 comments on “X-Plane 10.22 Beta 2”

  1. Hi!

    Any chance XP will ever use multicore CPU for object rendering?
    Actually we have no increase in single core performance in CPU last years…

    1. Maybe someday when shadows are enabled. But making the actual OBJ code faster is a higher priority right now.

      Single core has gotten faster – Intel cranks out about a 10% boost per hz with each micro-architecture rev. But…that’s not a whole lot faster.

      1. —–about a 10% boost per hz
        A bit lesser, I guess, 5%-7%. And overclocking capabilities are getting worse, so if you OC Haswell and SandyBridge you will result with the more or less same performance.

        —–Intel
        There are also AMD CPUs. Their have lesser single core power than Intel (about 1.3 or time slower), but more cores. Thus AMD’s system will benefit a lot for X-Plane multithreading.

  2. Running Beta 2: I’ve tried to fly the Carenado C210 twice and both times it’s crashed. The first time it crashed gracefully and submitted an error report. Just now it crashed to desktop before takeoff with this in the log:

    SASL ERROR: Error updating avionics: not enough memory

    Should I report this to Carenado to have a look at how SASL is managing memory?

    1. The 64-bit SASL 1.x plugin for Windows and Linux is _not_ compliant with X-Plane’s memory management rules. This is fixed in the SASL 2.0 build. As far as I know, everyone who I have seen using the 1.x 64-bit plugin is in process of moving over to the 64-bit plugin. Carenado has a chart of update status posted on the org somewhere.

  3. i tested many situations when in the earlier version of xplane and sasl would crash, no sasl crashes were observed, which is rather good.

    now something new and unpleasant i have noticed: custom scenery objects (mostly osm2xp and high detail level airports addons) will not load in real time when you transit from one ’tile’ to another, neither airport’s objects will load when you approach them … (in previous version, the scenery object loads were noticeable by stutters) now, in order to have those objects loaded within the surrounding area you are flying over, there is a need to activate the ‘local map’ and the exit it, after a short ‘asynchronous loading’ message delay, all objects are loaded properly.

Comments are closed.