I'm curious about how C2 handle the resources. Will it load all sprites or other picture images into ram in the beginning? Or is it just load those necessary things for current layout?(e.g. characters and level backgrounds)
I'm trying to constraint the sprite sizes, re-use and scale them up to save up memory for mobile platforms. but since the project grows bigger it will eventually be many sprites.
I believe it loads everything except for music into memory on first load, however I read that Ashley is working on letting assets load on a per-layout sheet basis.
boolean I'm almost 100% sure every browser with webgl support has per-layout memory management.
Develop games in your browser. Powerful, performant & highly capable.
sqiddster: Ah you are right, it looks like it was added in R07 as per this thread. I had no idea!
Where WebGL is supported we load images layout-by-layout. Where WebGL is not supported, usually the browser does something reasonble like evict textures on a last-recently-used basis so that they don't run out of memory. The exception is CocoonJS and directCanvas which load everything in to memory on startup; this is being worked on though.
Great to know! I hope CocoonJS can support WebGL soon in the future. its been asked for a while:)
Since CocoonJS is launching their iOS webGL support any day now (waiting to pass AppStore approval), does that mean PER-layout resource loading will be automatically compatible?
damjancd - I need to check with Ludei, but hopefully.