You might want to start investing your time in hash tables instead of checking the table 1 by 1. http://en.wikipedia.org/wiki/Hash_table Expanding on TechnoCat's idea: use two hashset's, assuming you want to keep a set of tuples. The first hashset would be your keys, the second would be your values...

Every update also check if it is colliding, if it is colliding move it back before update(dt) is finished. That is what I was doing before integrating with the physics module. My goal in using the physics module is to inherit the collision detection. At the same time, I need to be able to track at ...

If you want to move it one pixel per update you could write this in update(dt) body:setX(body:getX()+1) This moves 1 pixel/update But you are more likely wanting to do it one pixel per second. This is because the update cycle frequency highly depends on the speed of the computer it is being run on....

Hello all, I'm trying to right my vector so that it moves my body at 1 pixel per update cycle. If I set my vector to 1, nothing happens, if I set my vector to 50, the body moves, but skips pixels. I've read the box2d documentation and the love documentation but I can't figure out a way to compute th...