Constrain Attribute: self.AngleToTarget To: vectorToAngle(game.xPos-self.Position.X, game.yPos-self.Position.Y) RotateToAngle Angle: self.AngleToTarget Speed: abs(self.AngleToTarget-self.Ro

If I import a new collision shape made from the images in that project there is no issue with the collisions. Perhaps a video showing your process using PE? Try the attached collision shape.

Sorry for the late reply to this. Been busy with other things and am now coming back to custom collisions.

rotation. I don't think you can do that with a constrain behavior so you'll have to try one of the Rotate behaviors or use Interpolate. I'm not sure how exactly to do that.

How can I smooth that rotation, so that Actor A changes its rotation over time like with the interpolate attribute behavior set up with ease in and out?

Constrain Attribute self.Rotation to game.ActorB X

Make an attribute ( example : ADS )

The only idea I have is to use stretch mode, and recreate every width/height/location(x,y) of every actor in relation to the width of the device screen based on formulas with Change Attribute. But tha

At the moment, my planned solution is to give every UI element two Attribute rules that changes their self.positions based on a text boolean, and then have a button that simply changes the text Boolea

(Quote)

Make a couple of game attributes . . . . 'angle' and 'radius' . . . + create a master electron actor . .

Would anyone know how to create a various number of atoms circling and constrained to the center actor? My goal is to have my actor spawn an atom type "shield" that wraps around him

He does this all the time. Gives half ass explanations and then when you ask him to clarify he gets testy. The method I suggested would have worked without a ton of code. I suggested constraining the

Constrain actor's X to min(max( game.Mouse.Position.X ,200),400)

@Armelline i am going to use a table to check the images for each seperate actor... there is only going to be one line to win... there will be three columns with different image names in them and the

@fZolee That looks like it should work. You could save the table but for just one IAP saving just that attribute will be fine. Your logic looks good to me but be sure to test with TestFlight before re

You'll need to unlock the actor by double-clicking on it within the scene and then clicking the lock to convert it to an instance in order to access the scene attributes in the Attribute Browser.

http://gshelper.com/shop/free-templates-and-tutorials/constrain-to-mouse-and-keep-collision-gamesalad/

Hi @digitalzero Do you mean you've a boolean used in a change attribute behaviour which needs to be true for it to change scenes?

There is a video over at gshelper youtube called constrain an actor and keep collisions intact. As I take it you want a control that slides between two places on the screen? If you use that method you