(Quote)

..Constrain Attribute: self.Image = "ghost_image_"..floor(scene.Backg/100)..".png"

Here is what we know. When you use a change image behavior like that all those images are loaded on start of the scene, even if preload is unchecked. It is best to use a change attribute and call the

Save attribute

. > @Approw said:

@Icebox Try to constrain the camera to the player instead of using the control camera behaviour. Maybe this will solve your issue for now?

Create a game attribute, call it spawncount.

(Quote)

Import a bunch of images named background1.png, background 2.png, etc. Then have a behavior in an actor that is as large as the scene that does Change Attribute self.Image to "background&

(Quote)

(Quote)

It would greatly help if we could see a picture of your rule(s) in your play button actor. I assume, as @tatiang has already mentioned, that there is an attribute that is not reset when the game ends,

I'm still not sure, but changing the movement of the shooter, from interpolation to a simple change attribute, seems to be improving the situation.

Then, in the animation actor, have an Animate behavior with however many frames/images. Have a rule that says When attribute self.Image is [name of last frame image filename] --> Destroy.

Then, in the animation actor, have an Animate behavior with however many frames/images. Have a rule that says When attribute self.Image is [name of last frame image filename] --> Destroy.

(Quote)

(Quote)

It's all conditional. One as when I showed it being embeded in a rule it eliminated the need for a self lockout attribute. As to the animation frame you now don't need the rule and associated code. Ma

The actors "rotation" attribute is an angle attribute, so it only goes from 0 to 360.

"Flicks to 330” could mean anything. Same deal with 'rotates to -30', this could be indicative of a hundred situations, maybe you are constraining an attribute that decreases in value and the