the problem is if you put anothor wall in the center and jump over it when come back and touch it don't come back

@tatiang After a hiatus and some re-evaluation i found out that just adding whatever point to the score total actor attribute worked best with the equation you gave me thanks for challenging me and ma

(Quote)

File size is mostly to do with artwork, music and audio files. I'd not expect adding 97 more scenes to increase the file size too much, unless you add new graphics with each scene. That all said, you

You've probably made a mistake when creating the rule.

You want collide behavior with floor (concrete).

(Quote)

GS processes actors in reverse order. The bottom most actor will be processed first then the next one and so on ... That might be why it worked when you changed the order ... I had a similar issue tha

@Reckless App See the file below. I am guessing thats what you want.

Make an integer attribute ('A') set it to 1 / set Linear Velocity X to 250.

so how i can make an actor touch another one and come back??

When the actor hits the obstacle its linear velocity drops dramatically, you are then asking the actor to make this velocity negative.

Have you added a display text behavior (or log) to the actor which shows the velocity X? Just for verification, to check if it changed to 0 or remains at 250.

Then what is making the difference ? The three actors which showed no issues, or all the actors, images and game mechanics of a large game that when added make a difference ?

@Socks if you create a test project with three actors it probably won't make a difference. But add all the other actors, images and game mechanics of a large game and it does or it did when I last mad

I've been tinkering around with the Alien Conquerors template, messing with the actors' movements and behaviors. That got me to think about how the enemies fire back at the player.

The possibility of a certain level of concurrency could certainly account for the four quarters of a whole etc loading faster. So tiling large backgrounds could certainly make sense.

You could chop your images into as many pieces as you like - for example 768 x 64 x 64 px images - number them sequentially - and have GameSalad lay them out for you with a simple iterating change sel

If this theory were true then you could iterate the logic down to - for example - 1024 32x32 px images that would - in theory - load in 0.00097th of a second (or, at it's extreme, 1,048,576 1x1 px ima

You can if you have an old file from when it was activated. I've been working on this for a while now so I already had a game built.