Ur right. go make it and prove me wrong.

well, #1, flash = high-level = EPICMAJORFAILSOFOMGWTFROFLBBQWHY!?!
so cpu usage in general sucks balls. Flash is known among programmers as being incredibly inefficient compared to, say, java or c++.

#2 flash is known for NOT being multithreaded. so it only runs as fast as your first core. so quad/dual means nothing. if anything, quad runs slower (slower clock speed).

#3, i can play this on core 2 duo just fine.

for all that, i do appreciate your criticism. the whole point of my physics engine is to run quickly; if it is running slowly, that is Bad. im curious, however, how many objects u had on screen at once, and what the framerate was at that point.

well. the performance seems to not go below 27ish on my 4.1ghz core 2 duo until around 1000 objects onscreen. so obviously if you're running this on a shitty computer (ie laptop) and much fewer objects will slow the swf down.

and fyi this is a *demo*. What i mean by that is that it's unlikely that i will ever have 800 objects onscreen at once (think about any game like that in recent memory). Again, using this as a CPU benchmark is an idea, measure the average fps, etc.