mmmmmmmNope; just translating UIimages.
i suppose given that it's a real simple game you can get away with that.
mmmmmmmNope; just translating UIimages.
Is there any reason (other than speed) why I wouldn't be able to?mmmmmmm
i suppose given that it's a real simple game you can get away with that.
It's because I've never really used CALayers.probably not. it just seems weird doing it that way
If you do it too much you have to start again but I think that limit is going to be quite high, something that very few people will do. The original plan was to make the anti virus program more powerful in the CPU but now I'm not sure...wait... so crashing into the bytes that are coming at you is bad because it'll make the elephant more powerful and if you do it too much you'll have to start the trail all over again?
what happens when you reach the end?
I haven't updated the 1x graphics yet because I'm still messing with them, that's why it's doing weird thingsi ran your code and it looked like the white bars were jiggling until i went 2x on the iPad.
if those are meant to be electric streams I think you should look at showing it some other way. You know how you can use the lightning effect in Maya? you could do something like that. render out some lightning strikes, make it match the rest of your artwork, and make an image sequence (i think UIImageView can do image sequences)
it's also way too easy to hit the bytes, the spider is pretty wide. imo you should make the spider skinnier than the streams that the bytes are flying along or make the bytes skinnier. Or at least for the first few levels. or perhaps you have some penalty bonus that makes you fat and more likely to collide with the bytes
also, you should rotate your images and shrink them (you can do that in preview)
use something like #define MY_CONSTANT 60 or const static int MY_CONSTANT = 60; or in your header int myVariable; and in the implementation file myVariable = 60;