Now I remake some events and it check on colizion only ~3/second and poly check only ~1-2/second. Yeah!
(But high CPU % on mobile make me sad.)
Liking the debugger so far. I'm betting there are lots left to add to it.
One thing though, it's not working with Node-Webkit previews currently. It's not really a big issue, but it'd be nice to be able to run the debugger on a Node-Webkit preview as well.
I was always wondering how much better is to use simple distance check like (Obj1.X - Obj2.X) < 100 ; (Obj1.Y - Obj2.Y) < 80, than using collision checks?
Pakost - there is no point doing that. The runtime basically does that itself, but faster, inside ordinary collision tests.
Develop games in your browser. Powerful, performant & highly capable.
Is there a way to use only the cheap collision tests based on the bounding box, without using the actual polygon check after. Or maybe the 4 point poly checks is as fast as the simple collision check?
Pakost - yes, just set the collision mask to be the bounding box.
I was setting most of my events to be formula based, thinking that is cheaper, but i prefer using "on collision" and "is overlapping" conditions.
Just had to add another big +1 for the debugger, it's saved me endless headaches already!
Nice Work :)