Glad to meet you all! :)
I've been working on a game with C2 and have been wandering the forums and made quite a lot of searches.
I am still looking for a few technical answers mainly regarding performance and game optimization.
Here goes (mainly applies to platformer and physics):
Should've mentioned that I read the Performance tips page many times, and I still got these questions! :)
1) By default, are sprites and tiled background objects calculated if they are off-screen? You know, are they in memory, using CPU/GPU resources? This is a question often asked mainly because we can't find the answer by searching for it and because that's the first thing you want to know when it comes to optimization on an engine you don't know well. Example: are the calculation done for a physics object that is off-screen? That object would not be rendered, but still be active.
2) If a sprite is checking for collision on a physics object, does it do it for every instance of that object (off and on-screen) and every frame? Or just when it touches something? Also, is it better to have the moving sprite do the coll checking or the non-moving phys object? So I guess a collision check between two objects is as expensive whatever the type of object with C2. It matters simply if there are many instances of these objects?
3) When a physic object is toggled immovable, does it still consume as much CPU cycles than when it's movable? Like just visually frozen? What if I was to stack 20 physics objects off-screen at the end of a level. Wouldn't it be better for me to set them Immovable while off-screen? So that their physics calculations aren't done during the whole level but only when visible at the end when toggled Movable?
Here's a star for making it this far in my post: *
4) Sorry for not knowing anything about that subject (didn't search for it yet): can you use particles with physics collisions, and if so, is it better to use that rather than just Spawn another object multiple times upon breaking an object? Any way to achieve that efficiently with C2 without using physics on sprites or particles? :)
5) Tiled background objects: same as a large sprite with bounding box collision performance-wise? Or do they behave differently?
Let me rephrase: if I use a large sprite (512x512px) and set that sprite with a bounding box coll, is it the same performance-wise as a large tiled background object of 512x512px? If not, what is the difference in performance? Like "TB are rendered twice as fast because of this and that". :)
6) Where do I put bits of coding I see on the forum sometimes? Does this require a plug-in or just a licensed version of C2?
e.g.: if (player.x - spearman.x) && (Distance(player.x,player.y,spearman.x, spearman.y) >= 30) > 0 --> spearman.x += 1; set mirrored.
You just got 2 stars!**
7) Is there a game in existence that make decent use of physics released on Android made with the awesome C2?
For that answer: *** and you got a Perfect score!!!
Many many thanks Ashley! :D