"Actor 2" changes image, say "actor2.5", then becomes unaffected by gravity and floats to top of screen.

I like the if Alpha=0 destroy.. gonna try that, if anything, it will drop a function.. Thanx

Instead of using a second Timer to destroy, you could try setting a When the actor's alpha is 0, Destroy Actor.

accelerate and walls to have them flying in from top n bottom).

Thanks, SSS. I'll put up a blurb stating that my blog is not affiliated at the top of my page. Anyone who wants to announce assets/templates/game launches feel free to message me, I'll be glad to pu

OK, your problem: of the top of my head, try this, should work:

@deadlyseriousmedia at the moment I'm just stuck for ideas on what objects can appear in-front of the pivot at moment i'm only shooting backwards and top left i was thinking maybe obstacles that you h

(Quote)

Destroying an actor is, again, a very simple process, use the 'Destroy Actor' behaviour when you've finished with the actor.

After 1 second (this should match your Interpolation duration) Destroy this actor

issue. Because all my spawning actors were being destroyed by a wall actor that was behind the HUD of the game. They never made it to the bottom to be wrapped. But in this situation I dont have a hu

For me personally, i wouldnt be looking for the top grossing app. I'd be looking for the one that has given me the most impact. The one i connect to the most. But thats just me. Clearly there are goi

Pardon me if I misunderstood the problem, but couldn't you just put the actors in a non-scrollable layer?

bottom of the screen its re appearing from the top.

into English. This is one of the top selling apps in Norway - designed by a father for his daughter with special needs - a FREE and interactive app. We may cross over into developing on Windows 8 and

change the name, etc. just seems uninspired. On top of this, in the end, what may unfortunately be the lesson these kids learn, is that legal matters may come about over this. Instead of challenging

two actors are in the same layer group... then destroying and spawning in the back of the layer will make the actor just in the back of the particular layer group its in.

plus I just looked at the XML for the scene, the Layer position is not a value but rather the order in which the actor is written in the scene. so there's no real 'switch' to mess with.

OK, so by the sound of it the only other workaround is to destroy it and spawn it in the back of the layer, as you know...

Hi @sparkania no, changing layer order with behaviours/during runtime is not possible at the moment, unfortunately.... possibly on the cards for a future GSC release though.... just have to go with th