Besides the difference in bugs that we would have to work around, would this delete a users data? or are there any other problems that we would face? Currently CocoonJS works best for our game with less bugs (no odd volume bug, better performance, few other things) but once crosswalk gets better, we might want to switch to it.

the only thing is, the player might have to backtrack, and on some levels they can get around the object chasing them to go left, so I would use

Sprite.X < ViewportLeft - Sprite.width - 400

• Destroy

then switch it up for Y axis up and down, and X axis going right. thanks!

So i have an infinite runner game where platofrms are spawned infinitely on the X and Y axis as the player runs/falls. I used to delete the platforms as the player ran along, but i just found out my delete script isnt working. Performance has been fine though. Our target platform is mobile, does that mean that I don't have to delete off screen objects past a certain point? Or am I missing something and maybe if I run far enough, performance will go down?

i exported with cocoon and the volume worked fine, still stumped on this one

Does not need to be power of 2, but when it gets into memory as a texture, it becomes power of 2 regardless of your original size. Using a background of 1280 x 720p for example (even if its blank), requires 16MB of memory because it has to be stored into a 2048 x 2048 texture.

thank you so much for this, that bit just made a huge connection in my head with how to work best with sizing images. your explanation along with this chart helped me understand how to work with image sizes better:

http://www.vaughns-1-pagers.com/compute ... s-of-2.htm

is there a place I can learn that kind of stuff? because i consider myself good at the main logic of game development (at least in C2), but i would love to be better at formatting games specific to mobile.

bscarl88 if you read the images section of the manual and the don't waste your memory thread in the forums you will see that even transparent pixels still count. Your images are WAY to big for mobile.

Thanks, I can definitely see how that's hindering us. I read the manual 2 or so years ago, but i guess not everything stuck! One of the problems that the export is telling is, is that our images aren't all in the power of 2. Do all of our images have to be a size of the power of 2, or is it just for the large tiled backgrounds?

Keep it below 2048 x 2048, lots of devices cannot handle bigger textures than that!

Even if 75% of the 2560x2560 tiled background is empty pixels?

Are there any good tutorials on achievement systems without using clay.io? I would like to use clay.io but only if the player wants to. So i would like to use in game achievements, with the option of storing them on clay.io as well. Or if that's not possible, at least just use in game ones. I could only find forum posts on having to use clay.io, so i decided to ask!

I get the following errors when compiling (GL_OUT_OF_MEMORY). IS this only because the images are not powers of 2? We have some rather large scrolling backgrounds. Some are 2560x2560 some are 640x1500, and there can be up to 3 or more scrolling at a time. But their entire box isnt completely filled with pixels though. depending on the device I can get to the main menu which has all of our backgrounds in all 4 levels scrolling behind eachother, and they are called up depending on what level is called. But then I can't get into the first level which is only 3 of the 16 scrolling backgrounds the menu had.

Here's the errors

if you want to see the scrolling backgrounds for yourself it's on kongregate right now:

http://www.kongregate.com/games/oobente ... ou+can%27t

I really want to know this as well. currently my games use phone volume instead of media volume

is it possible to just use clay.io's achievement system without loggin in? I don't want to bug the player with the clay.io screen, it's a little slow and laggy, ut we still want to use it's achievement system to give the player in game currency

I too would really loove to know