> Have you tried setting the parameters when using the "On Created" event?

>

> That should work like a "Constructor" and apply to only the freshly created object.

>

> If you're using some system objects or functions and not re-picking though, I could see that potentially causing some issues.

>

Hmm. I missed that one! Thanks for pointing that out. >.>

you can also add the events just under the creation itself, it should work

thanks aphrodite ... you are really like aphrodite in mythology (saverrrr)

yes this why i was thinking to destroy object when its outside layout maybe will reduce the collisions calculations ... so as i understand i will help (just little but better than nothing ...)

and for reduce polygons collisions on object (as you sad i have object with some parts that not need to be checked for example only their X and not ther Y so ... that will help ??? yes ?

finally i just not understand something ...

when you say "Some collisions maybe could be check only each other ticks."

that mean that i have to add another condition to "when object 1 is on collisions with another object B" for example every tick or every seconde ?

thanks a lot for all

i just finish my game and publish it on appstore ... but i see that its slower on iphone 4

so i would like to improve performance at maximum for iphone 4

For the collisions, C2 already checks only the bounding box first, then if the bounding box are indeed colliding(very fast to calculate), it checks the true collisions, this can be slower depending on the complexity of the collision polygon, also C2 arranges everything in different cells (areas) if it is possible to reduce the collision checks, but other than that, I do not know much about how it is done.

As for not checking every tick, I would say for exemple a large (relatively speaking, testing will tell if it works or not) projectile can checks if it is colliding with the player only one tick out of two for exemple, to achieve that, you can add the system condition "Compare two values: tickcount%2 equal to 0", that may help (it could also cause problems in some cases, but I consider that this kind of projectile will be destroyed right after colliding)

I do not know much about your game so I cannot help a lot, the debugger feature of C2 may help you see what parts are cpu consumming.

Also, it may be possible that graphics are what kneel you game down, but not sure about that

Getting rid of objects outside layout will help (they normally are collision checked, and even if not because of collision cells, it still helps a little), reducing collison polygon of object could help during intense phases.

If your ennemies have an AI that doesn't need to be active when not on screen, you could do something for that too.

Some collisions maybe could be check only each other ticks.

At the end, the goal is to keep the amount of calculations as low as possible, while preserving the game.

I would like tilemap to look like the tilebackgrounds actually looks like, right now seams makes it pretty useless for a lot of people

Other than that, not much I can think of other than modularity

If your rock is a sprite, use the rock action: create object

If not, add a system: for each rock loop just after the collision check

jayderyu : I didn't remember seeing them for that long, but ok, I still though it could be useful somehow, guess I was wrong.

megatronx : in the view ribbon, you can show the configuration bar, but since jayderyu said it is a old thing abandoned an not documented, I am not sure it is wise to use it then.

I see, thanks for the awnser

I've seen from quite some time a feature not really described in C2 manual other than a WIP, the configurations.

They seem pretty powerful, but I am not sure how they are working (it seems they work for laout changes, but not for events changes, but I might be just using them wrong)

Does someone uses them?

I wondered from where the graphic driver updater with C2 come from, I tried searching inside the proprities of the file, but.. Most of it is filled with "TODO: <file description>" and such, I think it is proper to C2 itself, but by seeing the "original file: GfxDriverUpdater.exe", I am not sure, also I did not find informations about it in the "About" of C2, maybe I was blind

Just asking since it could come in handy for helping people updating their graphic card driver if it can be used, but the thing is I do not know if it can be useful, nor if we could be authorized to use it at the end, since I do not know who got the rights on it.

Ashley .

I think this should have been discussed in an e mail to the scirra team.

All we (users) can really say about this topic is either:

-Learn to C2.

-You should have used the trial before buying, or have contacted scirra beforehand to make sure the product suits you.

-For your anwser: https://www.scirra.com/store/terms-and-conditions .

-and some talking about our personnal experiences

DUTOIT : be wary of couguar, they steal your youth o_o

Aphrodite

Thanks, is exactly what I wanted

Still can you explain the formula lerp(a, b, x) ? I understand that a=current position, b=destination and x=speed, but I can't figure how x works. I want to understand it in order to use it for menus. Using these examples, how can I make the "easeOutBack" or "easeOutExpo" ?

In fact, lerp(a, b, x) is:

a: start number

b: end number

x: percentage (0 to 1) between a and b

But most people instead of making x varies, makes a variying, for exemple, if a is your current position, b your destination, and x is 0.5, theneach time, the distance between you and b will be divided by 2