if an actor is not marked as "Movable" and you move it via interpolate or constraining the x/y attributes manually then the physics engine really has no idea that the actor is moving

I'm guessing that I should use some type of attribute that would randomly generate a number between 1 and 6 (or 0 and 5) and then that number would correspond to a different colored ball? Any ideas?

Ok make a game attribute game.itsspeed

I'm using increments of 1/3 of a sec. Seems ok so far, but I use the self.time as opposed to the timer attribute. Dunno if that makes a difference.

you will need to create a game attribute and constrain the movement of teh actor to that attribute. then in the text display that attribute

Changes the saved attributes to 0

Delete the app off your ipod, then re-synch to load it back up. Every saved attribute will be reset.

Make game real attribute called Timer (OK, call it Time to avoid confusion with the behaviour called Timer)

Create Object Attribute -> Random_X

I would create an attribute called ChangeScene and another actor called manager and in it put display text and have it display the attribute. And place the change attribute in the rules where things h

I would create an attribute called ChangeScene and another actor called manager and in it put display text and have it display the attribute. And place the change attribute in the rules where things h

Collision also have problems with constrained actors.

Make a attribute called taps. Then have a rule when actor recieves event touch is pressed, change attribbute taps to taps+1. Then whenever you want something to happen because of the tap number(say 3

constrain attribute: self.rotation to (vectorToAngle( self.Motion.Linear Velocity.X , self.Motion.Linear Velocity.Y ))-90

Collision also have problems with constrained actors.

I'm not going to take a screenshot of the enemy actor, because all the other collisions work except this one.

It seems that something is changes after you mess around with the navigator , i guess you have rules for draging an actor and different rules for spinning them , use "display text" t

constrain attribute: self.rotation to (vectorToAngle( self.Motion.Linear Velocity.X , self.Motion.Linear Velocity.Y ))-90

in you draggable actor create 2 self attribute - "real"

constrain alltimescore to score.