This is the very definition of a memory leak. And of course its not anymore if you call garbage collect, i mean.... thats the point. What are you trying to say here? A memory leak consists of memory that is never released. The difference with what I'm saying is that garbage collection would eventua...

Practical example for a memory leak: Have a textbox, have it have a zoom in/out function. We reload our font with Font = love.graphics.newFont( zoom) _Font_ is overwriten each time so logically we would assume the old font data is discardet as it is no longer referenced. This is not the case becaus...

Here's a PoC of the love.physics approach. Lots of magic numbers everywhere as I fine-tuned the parameters by trial-and-error, sorry.

As I feared, love.physics doesn't do bouncing too well, and balls sometimes stick to the cushions if they are very slow, even when setting restitution to 1.

It's quite uncommon to have a memory leak when you're not using FFI. The most common cause of memory usage growth is not a memory leak; it's allocating objects and then disposing of them without releasing them, as Lua won't bother to garbage-collect them early because it doesn't "see" that...

Well, it depends on the degree of sophistication you're after. If you just want basic bounces, without considering aspects like friction with the cushions or during ball collisions, or whether the ball is hit off-centre to give it a spinning efect, then you could do with a simple bouncing-based sche...

The images with push use a linear filter, while the images without push use a nearest filter. With the nearest filter the adjacent tiles can bleed into the current tile. Changing to linear should solve it, if that's acceptable for your project. Otherwise, you'll need to fix your tileset by separati...

Have you tried what mön said? Filled polygons and circles are made of OpenGL triangles, which are usually rendered by default without antialiasing. setFilter won't help in this case though.

[Edited to avoid confusion to possible future readers] The images with push use a linear filter, while the images without push use a nearest filter. With the nearest linear filter the adjacent tiles can bleed into the current tile. Changing to linear nearest should solve it, if that's acceptable for...

This is a modified version of your code that does crash for me (for good reasons), using the image from the .love I posted above: local ffi = require('ffi') local texBuffer local terrainBuffer local backgroundBuffer do local imagedata=love.image.newImageData(640,360, "rgba8") local image =...

Come on, that's not the entire code. That's true, but i simply can't post my entire game. No one is asking you to do that. What we're asking for is a self-contained test program that can reproduce the problem. I've modified your code by adding this at the beginning of your code: local ffi = require...