OK, so I assume that the black and white image is a mask, the blue image is the background, and the red image is the one you want to draw over the background using the mask. This works for me: local bg = love.graphics.newImage('mountain-and-lake-landscape-800x600.jpg') local fg = love.graphics.newIm...

print(#map.layers) If you use the above code, you can see how many layers you have, and change that 8 to 1 higher than what the print offers. Unfortunately that isn't guaranteed to work. The only method that works is ipairs. For example: local t = {1, 2, 3, 4, [6]=6} local n for i in ipairs(t) do n...

I do believe that premature optimization on certain areas is the right thing to do, but you need some common sense for when to apply it. You don't need it for something that runs only once per frame.

If I understood what you're after I would be able to give you better advice. For colours, white (or full intensity of a given component) counts as 1.0, black counts as 0.0; for alpha, fully opaque counts as 1.0 and transparent as 0.0. That's the value that gets multiplied by the given component. Thi...

I'm not sure I'm understanding, but doesn't "multiply", "premultiplied" do this?

See also this subforum: https://love2d.org/forums/viewforum.php?f=14 in which several users post games. The advantage of the latter is that the games in the last threads are usually for the latest version of Löve.

lushfoliage wrote: ↑

Fri May 29, 2020 7:00 pm

Ahaha...turns out in some functions I had brick:render() instead of Brick:render(),

That should be the correct thing to have. You don't call an instance method on a class (Brick), you call it on the instances (brick). That's the whole point of the self parameter and the colon syntax.

And please use the support forum to post questions!

Hello, welcome to the forums. Quite unfortunately, Löve is using single precision to generate noise, which intrinsically has that limitation on big values. Here's a representation of the range 1999999.5 to 2000000.5 in both dimensions, showing the loss of precision in the coordinates (it gets worse ...

Is it fair to say that it would be better to have a clearer separation between the generated map and the engine necessary to load it? Kind of like the file that Tiled generates, on one hand, and the library that loads them (plus a simple program to use the library to represent it, if you wish), on t...