Can’t wait!

Agreed – our art team is mainly on Mac, that’s how it got this way so long. The long term plan is to have an output log visible somewhere in-sim, plus in-sim on the fly script reload.

Thanks! I’m kind of a “art gal” myself and my experience doesn’t include C++ so I guess no recompiling from source for me 🙂

FYI, on Windows, error messages seem to go to /dev/null 🙂 they are not output to stdout nor the log.txt or even the Developer Console inside XP, so it would be super nice to have XLua emit its output *somewhere* 😛

Not easily. We do want to make per-airport mesh editing in the future, but that requires a lot of coding first.

Right – our assumption was that you’d use a scripting language so that .snd files didn’t have to be Turing complete. And…the more “real” languages you know, the more Lua will drive you insane. Our art guys love it, but from what I can tell it was designed to troll C programmers.

Right now XLua errors are sent to console (I think) – at least on OS X and Linux if you run from command line you’ll see the errors there. I am not entirely sure where they go on Windows. We could add some kind of sane support.

If your other programming languages include basic C/C++ you can also just recompile XLua and redirect output…I’m pretty sure we checked in the MSVC projects.

Since the .snd format is a bit limited about triggering sounds on complex conditions, I’ve turned into XLua in order to program the conditions there and create custom dataref on which to base the .snd triggers on.

The problem is, I’m a programmer on other languages but Lua syntax is new to me, and X-Plane is not helping because it “eats” Lua errors :-P. I couldn’t find a way to see any output of the Lua program or even the interpreter pass, so common things like syntax errors cannot be debugged.

Is there any way to debug Lua programs under XLua?

Thanks!

“probability as close to zero as it gets”
I guess google has quantified that residual and its not 42. From the wikipedia page on SHA-1:

On February 23, 2017 CWI Amsterdam and Google announced they had performed a collision attack against SHA-1, publishing two dissimilar PDF files which produce the same SHA-1 hash as proof of concept.

I think those two documents were the WED and ObjectEditor manuals.

Oops – sorry, I stand corrected — what Michael said! WED 1.6 was mostly done by Ted and Michael, so I’ve lost track of what went in and what got held.

I think we can get art assets in for 11.10 without trouble.