I think I figured out the problem. There were global variable names being shared by both libraries (specifically the utf8.lua file) but not throwing any errors. I ended up changing the serialize library to Tserial.lua which doesn't appear to have any naming conflicts with the love frame library

I have a game that does some deserializing of data using a serialize.lua library found on the forums. With a os.clock() taken before and after running 1 deserialize() operation, the time is about .001 seconds. Just by adding: require("libs.loveframes") and not even adding the update or dra...

what are you using to make the color gradients?

I just started developing with love and this is what I am currently doing:
1) Opening my .love in 7zip
2) running .lua in Notepad++ from 7zip
3) saving, closing Notepad++
4) 7zip sees changes, clicking ok to update archive
5) Running .love
6) Step #2

There must be an easier way?

Yes, I am running 2 cores. Good thinking.

Seems to have dropped CPU down to 15%.

Running a high end machine and taking a look at Love demo projects: lovalanche: Essentially 0% CPU usage, uses GPU I assume, Good! no: Essentially math.. no difficult animation.. click detection.. 50% CPU usage!! Very Bad particles: uses GPU, very basic input detection... 50% CPU usage again, Very B...