News for hackers. Stuff that matters.
Re:The Game Engine Dating Guide: How to Pick up an Engine fo... by pestaa on Thursday May 03, 2012 @04:38AM (#3922918)
Interesting. Can you please name the framework you left behind?

Also, why did it seem to be more time-efficient to ditch canvas altogether and rewire the rendering part?

Re:The Game Engine Dating Guide: How to Pick up an Engine fo... by ricardobeat on Thursday May 03, 2012 @07:31PM (#3926302)
That was OCanvas (ocanvas.org). It's perfectly fine for vector stuff, but our game is very bitmap heavy. We started getting FPS rates as low as 10 with only 5-10 characters on screen (using animated/scaled Sprite objects). Using DOM + transforms we can get up to 500 chars on screen without any lag whatsoever.

We didn't ditch canvas altogether though, we render all the scenes in a background canvas and use DOM only for the moving chars. I suspect it's possible to get much better performance by pre-rendering all scaled objects, but haven't had the time to try it. CAAT performs incredibly well with bitmaps on canvas: http://labs.hyperandroid.com/static/caat/

Re:The Game Engine Dating Guide: How to Pick up an Engine fo... by jay_kyburz on Thursday May 03, 2012 @04:59AM (#3922957)
I'd also like to know more, I have just been rolling my own stuff so far and have been surprised by how well the canvas is handling everything I throw at it.

Tablets / Phones is a little different, but the desktop much faster than I expected.