I have several game made by GS Mac version, when I try to run my project with windows version and everything seems ok, but I have set up a bunch of " Index "attribute in the project,

So, what it looks like you need to do is not use the Move To position. This is what is locking your bullets to that position. Rather, use a move or accelerate behavior in conjunction with a constrain

constrain attribute: self.Rotation to: vectorToAngle( self.Motion.Linear Velocity.X , self.Motion.Linear Velocity.Y )

Make three real (game level) attributes. How about calling them axeX, axeY, and axeWidth

Constrain attribute - Var1 = tablecellvalue(arrayA,ID,1)

Double click on an actor to open it. Of the left hand side, you'll see that actors self attributes. Near the top of that list is a Boolean attribute called Preload. Uncheck that to turn it off in that

panning when two fingers are pressed, also i need to constrain it to stay in limits of my background which is 1024x768.

I always use the change attribute behaviour and change the self.image attribute.

their health status, I can do this by using two attributes, which, when combined, specify the name of the graphic I want shown.

Hi everyone,

1. Change Attribute: VONumber = random(1,30)

go into each actor and give it a unique set of attribute (without breaking them off from the prototype actor itself), so that each key has it's own "note" (in terms of what note it

time, a way to do it would be to make an integer attribute, let's call it BallNum.

And only a few constrain attribute, maybe just 4 or 5 line. But i had tons of global attribute.

1 how to do save and load like FMG's game ?(like the lost city or secret of grisly manor,it saves anytime.does it use table?So many items ,how to easy to deal with saving which are player having and w

This is because when the coordinate for the actor to move is set (using its Position attribute), it'll "roll on to the end" until that condition is met.

area in a Play Sound behaviour because: any attribute selected would still have to be linked with whatever sound you wanted via a Change Attribute Behavior anyway.

and I can manipulate those attributes for each key, so that the user can manipulate the interface to choose a different instrument, choose a different octave, and press the keys to derive the appropr

So one workaround to your problem would be to have several integer attributes, one for each soundset.

I'm a little confused by your use of periods between the quoted string and the attribute. If i want to display something like: