Youll want to have your attribute for when the buttons pressed, ill call it rotate. In the button have when touch is pressed change rotate to 1, and a rule when touch is released change rotate to 0.

Use constrain to 50.

Thanks for all your suggestions! I've been playing with GS and found that if I constrain velocity AND positions the problem... disappears! I get great collision detection AND functionality. I wonder i

I understand that GS overrides collisions if you use constraints but I want to know how to not care about that and get good collision detection regardless

In GS Constrains override Collisions so if you have a constrain anywhere that affects ether actor that conflicts with the collision it will over ride it. Also you can try playing with the densities. W

Thanks again for the speedy response! I added a rule that says if the Y value isn't what its supposed to be then change the Y attribute to the correct value, but this doesn't seem to work at all! I ev

I have a simple game where balls fall on a paddle, the paddle's center is constrained via two constrain attributes (Constrain X and Y to some global variables) and the collision detection does not fun

change attribute: scene.gravity to 0.

Yes it slows down coz of the mem leaks. if you keep on accessing actors attribute and changing scenes very often you need to restart it every 10 mins. I got 12 gig of ram on my pc. I hope this issue w

you just need one attribute. you can load different keys into that attribute or save that attribute into different keys.

I think you need one score attribute and use different keys base on the levels.

You can also do when attribute self motion linear velocity x is > 0 do right animation, and another rule when attribute self motion linear velocity x is < 0 do left animation

Let me get this straight. I have 30 high scores, one for each level of my game. In order to save these as attributes do I need:

you need 1 attribute and make it random(1,10)

in the "otherwise" section of the platform's rules, try setting constrain self.x & self.y to self.position.x & self.position.y

either interpolate the camera actor to the position over the level select box when its > but < a certain position and you would do that for every level select so when its close it interp

Thanks a bunch! That almost worked like a dream! The only problem I have now is that the "attractor" and the "follower" need to basically be the same actor (basical

You create a Integer Attribute in that Actor Called something like: My number

Thanks a bunch! That almost worked like a dream! The only problem I have now is that the "attractor" and the "follower" need to basically be the same actor (basical

you have to "trick" gs into checking that attribute before the timer fires each time.