One small request. Now that Raspberry pi 4 is out and the standard Raspbian uses OpenGL accelerated drivers by default, is it possible to include the armhf format as part of the standard releases? The ppa already contains armhf builds. Unfortunately I don't have access to a decently-specced arm mac...

phoyd wrote: ↑Mon Oct 28, 2019 4:05 pm Hi! It looks like liblove-11.3.so is distributed unstripped in the Linux x86_64 and i686 binaries.

Oops, you're completely right. I somehow managed to strip every binary except liblove. I've reuploaded the stripped (but otherwise identical) versions.

I just nuked all reported spam posts.

On windows you need to make sure you link against the dynamic library version of the (same) c runtime. We've seen before that mixing runtimes causes output issues, for some reason.

replace: __declspec(dllexport) with: __attribute__((visibility("default"))) I would assume, considering you're setting the visibility to default, that you can simply remove the declspec, and it will work. I was then able to compile into an .so by using: gcc -fPIC love_steam.cpp -shared -o...

The exact symptoms you're describing are.. weird, but I'm fairly sure I know what the issue is: you're creating a new tween every frame. You probably want something like this: Timer = require 'hump.timer' function love.load() color = {0, 255, 0} end function love.update(dt) Timer.update(dt) end func...

Like I said in irc: that depends on your os, unfortunately but last I checked desktops were on latest 2.0, phones were on the 2.1 beta I should also mention that on linux it uses whatever your system provides, so if you have luajit 2.1.0-beta3 installed, it will use that. As an aside, the bbcode for...

That code should work, do you have other code that may affect this? Have you tried running without mobdebug?

The graphics driver does this optimisation, without love being able to affect it, so the uniforms are gone either way. So now the option is to either ignore all uniform errors, or error for all of them, and love chooses the safest option.

Transparent in what way? If you just want every part to be equally transparent, you can use setColor as usual. If not, you probably need to write a shader.