You can use LuaJITs ffi API to access the filesystem functions of the OS, if you know a bit about C programming. This one kind of works, both for Windows and POSIX systems, although it's not very good code. It works for simple use cases. There's also at least 2 LFS implementations in pure ffi code (...

Wow, that looks really awesome. Excellent work! Creative abuse of the github issue tracker as a blog host too, lol. i like it. Any reasons why you chose this approach instead of using the wiki? Did you plan on making the tutorial right from the beginning? Like, "I'm gonna make a game as a tutor...

I don't think there's any easy "plug & play" solution; you need to create a comprehensive scaling engine that will cover all parts of your game. If someone knows of a better way, I'm all ears! :monocle: It all comes down to the fact that there's no way to query transformation states i...

Does not crash anymore, Debian x64 and Win10 x64.

In the 64 bit machine, it loads and shows the screen; it crashes when I move a bit (not immediately but shortly after I start moving). Same behavior on my Linux machine, same error, same stacktrace. $ uname -a Linux deb9 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux No e...

How to reproduce:

1. View the file on the default branch: link
2. Switch tag to 0.10.2
3. ???
4. Profit!

Thanks, this one works. I wonder how I managed to make Bitbucket give me a broken link.

Well, the defaults are hardcoded, but to me it seems that would be possible to study the code and use love.graphics._setDefaultShaderCode to work around that limitation, without modifying the Löve sources. It would certainly be possible, but that requires to actually read the code and not just skim...

It's hardcoded in src/modules/graphics/wrap_Graphics.lua, so you'd have to change the source code. The upcoming 0.11 seems to have support for newer versions.