If you're feeling like you could use a particle system editor, take a look at this topic. HGE's editor is very good at least as a starting point to tweak around until you have what you want.

Maybe it's time for a particle system contest? kikito?

BlackBulletIV wrote:I can't see where you're calling push() and pop()

Translation, scaling and rotation only last until love.draw exits. Anyway, I've already added push and pop to print some debug info on the screen.

Thanks,

Andre

BlackBulletIV wrote:Also, as far as I know, you can't just execute

Code: Select all

$ love

Running the executable without arguments should present the no game screen.

How so? It goes to board[row][key] and changes it. How does it set the whole row? Because it is in a for-loop. But he only sets the element if ""..i==key... A better way to write this is changeBoard(key + 0, 1). key + 0 will convert the string key into a number and add zero to it. As for ...

Just to help LuaWeaver better understand the difference. This code calls the setIdentity function which lives in the filesystem table which in turn lives in the love table which is a global variable (meaning it lives in the globals table): love.filesystem.setIdentity(name) This code calls the setIde...

TechnoCat wrote:Source:Stop()
Source:Play()

I think a better behavior would be if Source:Play() stops playing the sound if it's still playing. It's easier to figure out what's going on if your sound stops in the middle to being playing again than the sound not playing at all.

Hi All, I'm developing a game where all objects have a getExtents() method which returns the minimum and maximum coordinates occupied by the object. I'm trying to develop a camera that will get the extents of all visible objects and scale and translate things appropriately to have them all appear on...

Clearly a memory leak somewhere I'm pretty sure there's no memory leak, it's just the way Lua handles user data. Youare right in the sense you have described. It is a "leak" from the lua point of view. The "workaround" is to put collectgarbage("step") or collectgarbage...

miko wrote:Clearly a memory leak somewhere

I'm pretty sure there's no memory leak, it's just the way Lua handles user data.

Let me try to guess what the problem is... When you make a call to fb:getImageData() a new image data is created, which has all pixels from the frame buffer so the memory requirements for it is width*height*bpp (where bpp is probably 4.) But on the Lua side of things what is created is a Proxy userd...