Thanks for the help guys. I finally got it to work by using self_motions and using the layout that you gave me gyroscope, except it wouldn't work with the attribute for some weird reason, so i changed

If you don't ever need your actor visible, do the second option. If you do need to change its alpha (interpolate, change attribute, etc) do the first option.

Rule within above: When Attribute scene.motion is false

rule on pause button when touch is pressed pause game then change attribute game.pausegame to 1

attribute pointer_in?, default value 1

what attribute only loads the game NOT the splash scene?

Real quick guessing here: can't you use the change scene behavior for that? (and optionally some change attribute behaviors to reset any attributes that need resetting)

in scene attributes there is a camera attribute called rotation

when making a new rule condition that is not an attribute

when making a new rule condition that is not an attribute

My concerns are that with all those constrained attributes on one actor you may have some processor issues, collisions may not be perfect and they might not work at all. (I've had a game that balls li

I am trying to make a movable collidable triangle and to do that I need to constrain some actors, at the moment I have a square that is not collidable and 3 very thin rectangles that are the sides of

large size of the scene by using a camera offset attribute, but when you zoom out, things go wrong again. The position of the arrow itself is fine, it's just not pointing to the mouse position. And t

change attribute max speed to 0.

FMG, one of the best GS developers ever, Said one time what he does is only use numbers for attribute names. Then he keeps a notebook next to his computer with the attribute number and a good descript

I keep track of mine with a naming system. I'll do something like "From_Scenename" and use that for all of my attributes involved with changing scenes. I'll use "SceneName

thanks for the reply's, this makes me feel a lot more reliefed, just one more thing, how do you keep track of what does whats when you have so many attributes?

EDIT: Turns out what I used before was correct, I just needed to add something extra in. Works fine now, just need to get it to rotate. (constrain self.rotation to game.heroRotation)

1)create a game attribute called game.collideSpeed (real)

The way that I do it is with a game.integer attribute.