after you select device you did hit reset at the top correct because it works fine for me.

* You could Destroy your current Male actor and Spawn the new Female actor in their place.

(Quote)

Secondly, in the new version, the black "fetching ad" corner is too small and the loading square peeks over the top of it.

You can edit any post for up to 24 hrs after posting just hover you mouse over the top right corner of it and click the cog.

Plugging away at the next stable release is definitely top priority (Image)

New users of GameSalad often struggle with how to get something to change without using a Rule to do so. When an actor first loads on a scene, it starts running through its rule list from top to bott

Large asteroids will occasionally reveal power-ups, but some may hinder you. Use a missile barrage to randomly destroy large areas of targets.

In my experience GameSalad executes in essentially random order. Typically it will run top to bottom, but it will not always. And when it doesn't, it won't necessary execute in exactly the same order

(Quote)

The rule will only display the text if var1 = 1 and it changes from 0 to 1 back to 0 so fast you never see it, thats way when you have the top display working it only shows 0.

OK, take my original project and remove the very top display. Now you’ll see that no displays inside the rule ever get triggered. Does that make sense?

(Quote)

I'm sure most of us have noticed that a lot of apps (or at least the top apps) follow a pricing strategy similar to the usual $0.99-$4.99-$9.99-$19.99-$49.99-$99.99.

(Quote)

From I can see in the top box:

@jamie_c I thought that once something is displayed it stays on the screen, it doesn’t display and then disappear. If you remove the very top display the screen will remain blank.

because rules in actors run from top to bottom, and the layers read from bottom to top and I get what your asking now see new test. the top has a timer so you can see it happen the bottom has no timer

I did another test. I switched off the attr change at the bottom. So basically var1 gets 1 at the top and that’s it. Now the rule enters correctly. Why would attr change have an effect on the rule tha

I’d expect them to run top to bottom. I imagine they should go like this: