GameSalad Forums GameSalad Forums
Categories
Discussions
Dashboard
Sign In · Register
Sign In · Register
Categories
Discussions
Dashboard
Sign In · Register
Home › Search
  1. Change attribute bug ?

    Socks
    by Socks · May 2014
    (Quote)
  2. Public Bug Database (Updated 5/1/2014)

    Socks
    by Socks · May 2014
    Using a change attribute behaviour after an interpolate has arrived at its target value - where both the interpolate and change attribute are operating on the same attribute - results in the change at
  3. Change attribute bug ?

    LumpApps
    by LumpApps · May 2014
    An other workaround would be using the self.time and an offset attribute. I believe that is taking less from the processor. It's like a custom timer.
  4. Change attribute bug ?

    Socks
    by Socks · May 2014
    (Quote)
  5. Change attribute bug ?

    retired_830c50d3bf119e557be016b4f24844c9
    by retired_830c50d3bf119e557be016b4f24844c9 · May 2014
    LoopUntil self.Size.Width=300Change Attribute: self.Size.Width to self.Size.Width+1RuleWhen self.Size.Width=300Change Attribute: self.Size.Width to 100
  6. Change attribute bug ?

    Socks
    by Socks · May 2014
    Yes, I tried pretty much everything, there are a few workarounds, constrain worked for me too, but oddly using >299 wouldn't work, nor would a timer always work.
  7. Change attribute bug ?

    retired_830c50d3bf119e557be016b4f24844c9
    by retired_830c50d3bf119e557be016b4f24844c9 · May 2014
    @Socks, I'm sure it's no good, but if you use a Constrain Attribute to 100 instead of the Change that works too.... but still no luck with the Change Attribute either. (Image)
  8. Change attribute bug ?

    Socks
    by Socks · May 2014
    (Quote)
  9. Change attribute bug ?

    Socks
    by Socks · May 2014
    (Quote)
  10. Change attribute bug ?

    Socks
    by Socks · May 2014
    Thanks for taking the time to make the video, appreciated. The issue I am having is with change attribute, you are using interpolate rather than change attribute to return the actor to its starting si
  11. Change attribute bug ?

    Socks
    by Socks · May 2014
    Placing the change attribute into a timer also didn't work, the rule just wouldn't fire for me, but even if it did unfortunately the way my project is set up I need it to work as shown in the video.
  12. Change attribute bug ?

    Socks
    by Socks · May 2014
    ”Not on my Mac at the moment so I can't test but have u tried tossing a timer in the rule? After 0.01 secs change size“
  13. Change attribute bug ?

    LumpApps
    by LumpApps · May 2014
    Instead of change attribute use an interpolate attribute in 0 seconds. See attachement.
  14. Change attribute bug ?

    -Timo-
    by -Timo- · May 2014
    @jamie_c the whole problem is in 'change attribute'. now you are using interpolate to change width back to 100. interpolate width to 100 in 0 seconds should also work instead of change attribute.
  15. Change attribute bug ?

    BBEnk
    by BBEnk · May 2014
    also you can change the rule itself to say when self time > then 2.02 seconds then change attribute width to 100 also works.
  16. Change attribute bug ?

    BBEnk
    by BBEnk · May 2014
    I think it as something to do with timing if you put the change attribute in a timer and say after 0.01 seconds then change size to 100 it will work, or at least does in 11.1.2.
  17. Change attribute bug ?

    Socks
    by Socks · May 2014
    I'm trying use interpolate to increase an actor's size - and when the actor reaches the target size I need to then change its size back to the starting size using change attribute . . . simple enough
  18. Help needed with moving ball

    Socks
    by Socks · May 2014
    Constrain self.Motion.linear.velocity X to 282.8*cos(vectorToAngle( self.Position.X - game.ballX , self.Position.Y - game.ballY ))
  19. How to compel player to alternate the arrows ?

    tatiang
    by tatiang · May 2014
    Create a text attribute called game.whichArrowNext. In the left arrow, have a rule that says When touch is pressed change attribute game.whichArrowNext to 'right'. In the right arrow have a rule tha
  20. Salt & Pepper: A Physics Game (coming soon)

    iamcartez
    by iamcartez · May 2014
    d. The side and bottom collisions on the bowls are better and no longer requires the salt and pepper to be dropped in the center.
Previous Next

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with GameSalad

Sign In Register

© Vanilla Keystone Theme 2026

Powered By Vanilla