I agree that when the device determines the oreintation...the ad will end up viewed top or bottom...I would not EXPECT it to display sideways.

And it was recently said by a GS programmer that attributes don't work top to bottom like some other programs, but rather use a notification system{although the lines of code running through actors mi

the first ball) - it will land neatly on the top of the first ball, even after bouncing for a while, whereas in the real world things are a bit noisier, factors like the quality of the surface (even

(Quote)

instructions right. But as the arrow in the hud layer sees itself on different coordinates as the object in the scene I thought that might be why it's not working?

It sounds like you're changing the value of one or more attributes and you have rules that destroy the tabs actors based on the value of those attributes. If you don't want the tabs to be destroyed,

Thanks Socks. The trouble I've had though is that the coordinates in the HUD layer are not related to the scene, but rather the position within the screen size / camera. For example, let's say my sc

The above will get the arrow on your non-scrollable HUD to point to the object on the scrollable layer.

(Quote)

I'm trying to get an icon in the hud point to an object on the scene, but it looks like the coordinates of the hud (defined as a non-scrollable layer) refer to the screen size not the scene size. To

While this is absolutely true, the word layer in GameSalad is a bit of a misnomer. Each actor is on its own Photoshop "layer", and the "layers" in GameSalad are mor

Actors are ordered within each layer from front to back. Think of a layer in Photoshop, Illustrator, etc., with objects (in this case actors) that are stacked on top of each other. When you spawn in

Agreed ! I just thought I'd throw that idea into the mix, but yes a spawner can only spawn to its own layer.

Technically, that's still spawning the actor on the layer the spawning actor is on (Image)

Unless (through an attribute) you trigger an actor on another layer to spawn - so a collision on a scrollable layer could spawn (via > attribute > spawner on the target layer) an actor o

The problem is that you're constraining the size of the bullets as well as the position of the player. You can remove this problem in two ways.

You can only spawn to the layer the spawning actor is on. What layer is the spawning actor on?

the layer under is scrollable and the layer on top is unscrollable and instead of it moving as if its on a scrollable layer it always comes as unscrollable... is anyone else having this same problem

you see...you can destroy the opponent, but you does not destroy yourself by enemy´s bullets...

The game performs well on a desktop supported platform, but right now, on mobile, aside from the 12 second load time for the actual game{menus load quick, due to minimal rules.} There is a strange &am