(Quote)

Game.attribute = XXX

It looked like the actor stopped colliding for a second which caused the image to revert back to the running animation. You should set a boolean attribute that says when the player collides with enemy

You just need to add the camera offset onto the end of your Constrain behaviours.

On the actor I have these constrain attributes:

Yeah, basically, they aren't scanned as such, not until that are called into action, so in theory we could have 12,000 attributes and they wouldn't really impact performance.

Attribute just sit there right? Doing nothing until they're called? And the reason I said the sound might be a problem is because I had the issue with playing a gun fire sound every .08 seconds...

Change attribute self.animation false

I'm not sure a crazy amount of attributes would impact performance, an attribute doesn't place a strain on the processor.

create a game attribute call it : combo

Im avoiding using timers as they affect performance. The attribute would have to be a real attribute, because the lifetime will have to be in decimals. .1 the smallest and 2 the largest number. Try

I was thinking you could make game.ParLifetime integer and put that in the lifetime attribute of the particle and THEN make a timer that says: every (number) change attribute game.ParLifetime :to: gam

It seems no matter what I try the particles will not change lifetime. The particle lifetime will not reflect increase or decrease even when set to an attribute manipulated with a loop.

I've also tried using attributes within the actor with conversions and a combo of both so I'm narrowing it down. I get the feeling its may have to be all done outside the actor, the converting of sce

Yes there is a place for expression, however I can seem to constrain the particle lifetime to a real decimal converted attribute that I manipulate with a loop. No matter what I try I can change the l

Is there an e for expression editor in the lifetime attribute of the particle?

(Quote)

,> @hoomann210 said:

It has a text box that shows the value from the correct answer, while the KeyAnswer actor in the middle is where you can type with the Keyboard input attribute.

@crestwoodgames, are you trying to collide one or more actors that is being affected by Interpolate Behaviors? If so that will not work, collisions don't register when using interpolate behaviors, you