Is there a way to get the amount of memory a system has? If there is not, could you guys add a function for that in 0.9.2? It'd be very useful for what I have in mind.

But there is a huge difference in amount of memory used between a spritebatch that was first created and had nothing done to it and one that was filled and then cleared, why is that?

Plu, calling collectgarbage didn't help, I'm fairly sure this is a love2d bug.

After I clear a spritebatch of it's contents via :clear(), it doesn't seem to free up the RAM nor VRAM that it used, yet :getCount() after clearing returns 0. Is this a bug or is it intentional? Edit: oh another interesting thing - if you call :bind on a spritebatch, add the sprites you need to it, ...

Honestly, if every little bit matters, you should probably build it in C. It'll earn you a lot more speed than anything else would :) With the current speed ( 930 fps on my end ), it's not necessary. x) The reason why I am asking whether there are any other FFI version libraries, is that even thoug...

It's not (without modifying LÖVE's source), and you generally shouldn't need that kind of micro-optimization for spritebatches. If you're considering it, it might be a sign that you're trying to optimize down a misleading path or you're using the wrong sort of algorithm or tool for your end goal. N...

Interesting. Is it possible to write FFI versions of thr spritebatch library? If it is, what would I need to do?

Is there any way to load .lua files in threads? I tried doing require "filename", but it errors out in the thread. You have to require love.filesystem (and any other love modules you might want to use) in the thread's code. See the [wiki]love.thread[/wiki] wiki page. Yeah, I figured that ...

Is there any way to load .lua files in threads? I tried doing require "filename", but it errors out in the thread.

slime wrote:If you use this (all you need to do is require the file) then you'll get the performance of LuaJIT's FFI when calling ImageData methods, without having to worry about whether your C pointer / array arithmetic is correct.

Holy shit dude, you just saved my life.