I might be a dummy, but idk haha.. I get your story, definately very logic, but how the hell should I get my interpole attribute to color back to original colors.

@KevinCross how do i put in the 'fade-away' you're talking about. Is it also an interpolate attribute? Can't find it.

You can also use Interpolate instead if you wanted, on the actor's Y attribute, over a pre-determined time down to your base level Y position (without worrying about matching the x position).

What a shame, OK, one last idea: using Change Attribute with self.Motion.Linear Velocity.X and Y to stop the actor, then Change attribute self.Rotation to vectorToAngle...(or maybe the other way aroun

So perhaps try stopping the actor with Change Attribute with self.Motion.Linear Velocity.X and Y... hopefully it should keep its angle that way. If not, I'll think again... :-)

That was my idea and i tried it again but cant get it to work. Maybe i overcomplicate things. Could it be the constrained VectorToAngle that overrides the angle attribute? Since speed is zero motion i

change attribute scene.camera.size.width to 1024

Hi F, without testing - so off the top of my head - what about using a Constrain behaviour on the actor's angle attribute, and when you change velocity to zero, change the Direction to the angle attri

Im trying to add some random movement to an actor. The movement is fine - im using Timers with random Change Velocity attributes. The rotation is constrained with VectorToAngle so the actor is always

• Unless you need that attribute mobhitcolor for something else, you don't need it at all to trigger the colour change if you're using overlaps or collides Rule

If attribute game.mobhitcolor = 1

Wrap doesn't work well with constrain camera so you will have your work cut out but if you leave the camera as it is and don't constrain it this should result in the same asteroids as the original (yo

For eg. you could Constrain scene.touchX to cam.Orgin.X + device.touch.1.x and that'll hopefully return the desired results.

I tried having the objects set their angle to a game attribute when they detect the collision and using this for calculation, but unfortunately, this causes inaccuracies to occur.

So, you have to keep the random seconds outside of the Timer, to be put into an attribute to use, and not have the Timer set to Every - just to After - then set up a loop mechanism with a boolean.

(Quote)

One way would be to put the random x of the floor chosen into an attribute as well, and change the position x of your Hero to match (if you wanted him smack bang in the middle of the floor - if not, s

equal to the spawned floor Y coordinate. Then, constrain my hero to that Y coordinate and add half the height of the floor so that the bottom of my hero lands on top of the floor rather than centere

Hi Charlie; we all need a bit more info to work out what's going on... are you using Windows or Mac GSC? What are you using to trigger the sound effects that cut out? Are there any Timers involved, or

Constrain Attribute: self.myReallyLongDistanceFormula To: sqrt((pow(( game.Mouse.Position.X - self.Position.X ),2)+pow(( game.Mouse.Position.Y - self.Position.Y ),2)))