using an attribute as a speed bug?

Sparkyidr

Anyone else try this?

Create an actor
Create a game level attribute called "movespeed"
In your actor add a rule :
>>change velocity (180 reletive to scene)
>>game.movespeed

Manually set "movespeed" to 50 and hit play

the actor will move left at speed 50

Now, go and set "movespeed" to 0

then in actor 1, add a rule

>>Change attribute
>>game.movespeed to 50

now hit play, and the actor doesn't move, even though movespeed is 50 as before, but set in a rule rather than manually in the attribute list.

or am I being a bit dim?

quantumsheep

I'm having similar trouble actually - multiplying the base speed by one or two (to slow things down on picking up a power up)

I was sure it was just me and left it - will look at it again later (though this was happening in .92 as well for me)

QS

Rob2

@Sparky it depends which comes first in the actor the change attribute or the change velocity.

edit: ah..I wasn't using rules just behaviours

Sparkyidr

Just done some more testing. It's deffo not right. Even though a display text will show the attribute to be whatever your rules are telling it to be, it actually only uses whatever it's physically set to in the attribute list!

So if I set it manually to 50, but then have a rule in an actor that sets it to 200...it displays (using a display text) as 200, but is actually using the 50. Same behaviour when using a constrain instead of a change too.

meh.

Sparkyidr

@Rob

bang on mate. Shifted the change to the top and it works.

new "problem" though.....

if I have the change velocity on 1 actor (a game controller actor for example), and the change attribute on a different actor.
it doesn't work.

This is pretty important to be able to do, as I quite often have an actor in the scene that controls things like game speeds, and spawn speeds and whatnot.