You could try using a vertex shader instead of a pixel shader; I don't actually know how much they affect performance, but I'd guess much less since the code only runs once per vertex instead of once per pixel

molul wrote: ↑Mon Jul 23, 2018 6:51 am EDIT2: spritebatches my ass. I only had to make texture atlases of all my textures and properly define quads ^_^U

If you're using LÖVE 11, that's probably because it automatically batches draw calls with the same texture

How are you printing stuff exactly? Could the bottleneck be in string manipulation rather than lg.print itself? Could using a Text object help? I'd help more but I'm afraid I don't have access to devices of similar power.

You need to drag the folder that contains the main.lua file, not main.lua itself

One reason would be safety. Lua code would need to be sandboxed, or people sharing modified saves could potentially run untrusted code through them.

Please don't just rename the topic to "closed". Use a descriptive title and add something like "[SOLVED]" at the beginning or end, so people know what it is.

gutil.tile returns two values, but since it's followed by a comma Lua will only get the first value and discard the second one. You should do something like this: love.draw = function() local x, y = gutil.tile(0, 0) local w, h = gutil.tile(1, 1) love.graphics.rectangle("fill", x, y, w, h) ...

You can use love.audio.setVolume to keep playing them while muted, or love.audio.stop to stop everything that's playing and then, as you said, not play anything unless it's unmuted. What you choose is up to you - I guess the former will be a bit heavier on the processor and/or battery and/or might m...

I think he means the launcher.

Nixola wrote: ↑Thu Jun 14, 2018 3:08 pm Try setting the LOVE_GRAPHICS_USE_OPENGLES environment variable to 1 before launching LÖVE; that should be all there is to it.

That is, assuming your computer supports GL ES and the drivers use a stricter compiler. I don't know how to check for that, but trying won't hurt.