Keep in mind I have it set to both destroy the actor and reset the scene on collision yet it does neither of those and it simply slides through it.

I don't know why it won't destroy on collision, perhaps it has to do with the properties of the actors that should kill on collision(the spikes)? I don't know. Any tips would be greatly appreciated.

The ability to reorder the images by name/date/date added/size (etc) would help, but you can't do this either. Additionally when you do scroll through and locate your image, you only need click on ano

I resubmitted clarifying how the menu system works (stage numbers on top, levels beneath) and also clarified that this particular build is for the fireTV only, phones and tablets are not supported, n

You said you want the actor to disappear so you have a few options for that (Destroy, Move off screen, Interpolate self.Color.Alpha to 0, etc.) but you'll probably want a Timer in that actor to handle

Check the Big Top Blaster template that comes with Gamesalad. That should help you.

I am making a game for iPhone where i shoot a cannon to the top of the screen but i don't know how to make the shooting part. I want it to be like dragging and then releasing like angry birds style if

I am making a game for iPhone where i shoot a cannon to the top of the screen but i don't know how to make the shooting part. I want it to be like dragging and then releasing like angry birds style if

(Quote)

Did you accidentally unlock the actor on the 1st level and create an "instance" with its own rules? To check for this, double-click on the actor in that scene. If you see a large l

i got the same rejection, but when i test it on my device it stops as it should. and I confirmed that I have the rule in all scenes.

Just got rejected by Audio doesn't top, so it can not be resolved by simply use the hibernate function, it must be a bug from GS.

one other question how do I move for example the actor from the top of the screen to the middle at the same time as it becomes larger, instead of first moving it and then make it larger?

It is straight up not optimized for Yosemite, but hey, there is a slew of apps out there that are not running tip-top at the moment. Not as perky, but it works.

My last suggestion would be to experiment with layer position in relation to how the actors are constrained to each other, I've often started out with very noticeable lag and been able to remove it en

In addition, consider when you are saving and loading. Attributes should be loaded when the app loads which means that you place the Load Attribute at the top of an actor's rules and place that actor

Do you have multiple layers in your scene perchance? If so and you changed the size of your scene, the layer that's putting actors in the incorrect place needs to be deleted and set up again. This hap

Try putting your problem in the Gamesalad made treads towards the top.

Try placing A below B and see if that makes a difference (GS scans layer from bottom to top).

A on top layer