I didn't take a close look, but one thing that looks off is in all the functions of Hamster you put a dot (.) as opposed to the colon (:). Putting a colon gives an implicit 'self' argument, so that might be what you're missing.

After commenting out love.graphics.reset() (and leaving the pop() and push() uncommented) the corruption error stops, but for some reason my tiles were being colored the red color I was using in that same code block. Am I using the drawing api incorrectly there? edit: I can't say I know what was goi...

Yeah that definitely rings a bell, my laptop is using 13.04 now. Maybe it's time for an upgrade.

I had a similar issue with an older version of ubuntu, what version are you using?

For me, since the libsdl2 package didn't exist I had to install love by compiling from source, and resolving dependencies in the configure process.

This happens for Ubuntu 13.10 32-bit and Ubuntu 13.04 64-bit. I'll give the nightly build a shot to see if that takes care of the issue.

edit: I gave the latest stable build a try on my 64-bit machine, and the issue exists there too.

Hello, I'm working on the camera for my game, and I ran into an odd issue with a bit of the graphics api. If I use love.graphics.push() and love.graphics.pop(), when I quit the game I get an big backtrace and the error. I know it's related to these functions because I don't get the error if I commen...