X-Plane 10.50r1 is out – we should have a Steam build some time this week depending on when people can get it uploaded to the servers.

For users seeing missing runways when flying, we will have a special build for you to try soon if you filed a bug report.

If you are working on a WED 1.5 airport layout, please re-try your AI traffic in 10.50.

The release notes have a complete fix list.

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.

23 comments on “X-Plane 10.50 Release Candidate One Is Out – Steam Soon”

  1. By “some time this week” you mean next week right? This week is basically over.

      2. And based on the Facebook post the chances of it coming out this week or the next or the next are zero as well. Am I right?

  2. Ben, I can’t seem to get the hang of AI traffic using WED 1.5 and 10.5. Has anybody published any instructions yet?

  3. Hi Ben, yesterday I tried the special build for the missing runways and it worked like a charm! Is there going to be an update incorporating the fix? Thank you for the great support!

    Cristiano

  4. Water reflections finally look normal. No more ships looking like they hover above the water due to offset reflections.

  5. Hi Ben many many thanks for your team’s efforts on RC1. However when I try updating, I am unable to have access to RC1. The installer always shows “you are about to download … to X-Plane10.50b6”. Any solution to it? Thanks.

    Shane

      1. Hi Ben. Thank you for your reply. I am in the office and will file a bug after work.
        Again many thanks.

        Shane

  6. What does this item mean in the log.txt:
    “0:16:39.121 W/ATC: p=1 (N01XP): Wrist Slap!”
    Presumably p=1 refers to A.I. plane #1, but I’m concerned it might interfering with my SASL plugin when the rare event occurs.

    1. Is there more? It means AI aircraft #1 did something it wasn’t supposed to do (e.g. taxied off the runway onto the grass, etc. and the flight had to be restarted. The most common known source of this is CFIT – ATC doesn’t have an MVA map, so if it vectors the AI into a mountain, they crash and are then slapped for being “not flying when should be flying”. ATC is so judgmental.

      I have no idea how this would interact with your SASL plugin.

      1. Or they land short into the sea. Interesting. All I did was define the tcas datarefs for a custom map — not polling them yet. But the correlation is now confirmed: Every time a sasl reset occurs the entry is there, but the Wrist Slap event does not always cause a sasl reload. It doesn’t happen in the air or when the CFIT is remote.

Comments are closed.