whats a modern way of doing this? makelove works really well. If you have python, it's easy to install and use. I use it on Windows, but it builds for multiple platforms and on multiple platforms. You can even configure it to build for lovejs and host a server so you can test your lovejs build with...

Why doesn't Joystick:getName return the name of the gamepad from loadGamepadMappings? My USB-connected DualSense gamepad's name is reported as "Wireless Controller", but the GamepadMappingString is "PS5 Controller". Here's a simple demonstration main.lua (requires you download ht...

The README says: > However that way you will get a submarine which "emerges", then "suddenly disappears", and emerges again. To make it look more natural, you must add some animation frames "backwards", to give the illusion of "submersion". Here's the complet...

I think I installed love on macOS with brew and was able to use `love .` to run love in the current directory. My /usr/local/bin/love is a symlink to /Applications/love.app/Contents/MacOS/love, so I'm not sure why it doesn't work for you. Maybe try this: cd ~/path/to/mygame /Applications/love.app/Co...

> So when an element with a random velocity hits an obstacle I want it to bounce to another directions. Reflecting momentum should be the default behaviour of box2d (unless you want to bounce to be a random direction?). Try using setLinearVelocity/applyLinearImpulse to set the *initial* movement of ...

You could try refactoring your working code into a Hoverable class that you can use in both cases: Hoverable = Class{} function Hoverable:init(x, y, width, height) self.x = x self.y = y self.width = width self.height = height self.hot = false end function Hoverable:update(dt) local mx, my = love.mou...

Check out the lua users tutorial on modules: http://lua-users.org/wiki/ModulesTutorial

Ah, of course. I didn't think about the tostring that was happening inside Text:set! > Note how Löve generates garbage too. Moving the mouse, pressing keys, and probably other things will raise the count. That's what is not under your control. I guess not generating garbage shouldn't be my goal. Ins...

Writing out that question helped me figure it out. You can collect garbage before measuring and use that to zero out other garbage so you only measure one specific function: local function measure_garbage(fn, ...) collectgarbage('collect') local tare = collectgarbage('count') collectgarbage('stop') ...

Is there a good way to measure how much garbage you're generating? It seems pretty trivial to put love in a state where the garbage alloc never stabilizes. Take this code: local time = 0 local text = { garbage = love.graphics.newText(love.graphics.getFont(), ''), time = love.graphics.newText(love.gr...