texture_rectangle uses non-normalized texture coordinates like (width, height) (300, 100) instead of 0.0 to 1.0

and there are a lot of restrictions on filtering modes, etc

Yes, you could potentially be wasting up to 3/4 of texture memory and slowing things down on cards that can handle non-pow-2, especially if you have a lot of images.

The default should probably be to automatically pad images loaded to power-of-2, with the ability to check the card for non-pow-2 extensions and globally disable the behavior of automatic padding.

I've been using the latest, just note * using quads, the last two parameters are the width and height of the image * I had to use require() and dofile() over love.filesystem.require() etc. * TTF text positions at bottom left my other notes, not sure if still relevant *mkdir() fails when write direct...

It looks like the 200 m/s limit is a feature of the underlying "Box2D" so you have to scale your simulation to within the limits.

To make use of the library, I copied the DLLs to the folder with "love.exe" in Program Files. Then it allowed me to import and make use of it. I was basically just needing the capability of drawing a small representation of the current screen and saving it at like 20% so I could piece toge...

I'm working on an exploration platformer, so the map is very important. Each time you explore an area, I write an image file corresponding to the screen, in miniature to show that area. I have to use a separate library called "GD" for this. Is this the way to go or is there another way peo...