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

A quick follow-up on yesterday’s post regarding LuaJIT memory failures on Windows:

We will be making a change to how plugins interact with LuaJIT and X-Plane for 10.20 rc2.  If you have an add-on that uses a LuaJIT-based plugin (SASL, Gizmo, or FlyLua) you must get new 64-bit binaries for your add-on!  If you do not get new binaries, it will only be a matter of time before your 64-bit add-on stops working.

This change is unavoidable – it either has to happen now (in RC, when only beta testers have X-Plane 10.20) or later (when we’ve shipped the product and everyone is happily flying).  I think now is better — I would rather not have to do this at all, but the memory problems are not going away.

I am already in direct contact with the plugin developers who use LuaJIT to work with them on the needed changes.

With this in mind, I am hoping to cut RC2 later this 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.

2 comments on “Airplane Authors: You Will Need New 64-Bit Lua Plugins!”

  1. Should non-aircraft plugin authors that embed LuaJIT be concerned? Is this something you are addressing on the SDK side, or do changes need to be made to LuaJIT itself?

    1. YES! Anyone _directly_ using LuaJIT needs to follow the X-Plane guidelines for 64-bit X-Plane plus LuaJIT. These guidelines are changing for rc2. The SDK web pages are/will be updated, but it’s best to contact me off-list to synchronize. I am currently only in direct contact with the dev teams for FlyLua, Gizmo, and SASL.

      The most important thing is that if your 64-bit plugin follows beta guidelines and _appears_ to work, that’s not good enough to survive the long term.

Comments are closed.