Non Scrollable Layer? or Non Moveable Actor? makes a difference, but Yes you can have a moving Player collide with non moving Actors placed on scene.

Could it be because one of the layers is scrollable and the other is not? That's the only thing I could find that affects it, but I really need one scrollable and one not... (Image)

(Quote)

Layers don't effect collisionality (I'm rolling the dice with that phrase, it probably doesn't exist (Image)

I'm trying to make my player actor collide with some enemies that I need to have on a seperate layer to work properly. Problem is, even though I have my collision behaviours set up, they aren't actual

Spawn top obstacle in front of actor direction 0, relative to actor. Position self.position.x, self.Gap+220 relative to scene

top of the list again hahaha after release in oktober:)

I have no idea, all I know is that I can lay another actor on top of another but can not change the bottom actor to be on top

Do you have more than one layer in your project ?

google Socks link machine or Socks fast constrain. I think that'll get you what you want. If you just want one to sit on top of the other no matter what, just make two real attributes actorX and actor

I want to create a pendulum with a bomb attached to it, as it swings i want to be shown the trajectory/path of the bomb all the time while it's moving forward and back. and when the player is satisfie

optimized logic, as well as code running from top to bottom within an actor}, I learned from your posts. {Although, as for the attributes, I learned from GS staff that it runs on a notification based

On the note of Usability, I've posted a list of my Usability Suggestions here, which I think would make using Game Salad much nicer. I've added priorities to each one, with the top few being my big o

These things drive me nuts. Scroll scroll scroll, click and scroll scroll scroll........

Or if you were looking through your layers, click on Scene, click on layers, scroll down to the relevant layer, open up that layer, scroll down to actor 42, double click and edit - hit preview . . . h

@Uplink1001 check your layers and make sure that it isn't in the non-scrollable layer. You may also have a rule that says to kill it? Or a rule that changes it's position? These are some oops moments

i have another trick to get to the top of the list again,that really helps a lot:)

@RThurman No existential dilemma here. And yes, I was banging on about the layer order issue. Thanks for the reply – that one seems kinda important to know.

Try putting the actors closer together in the layer, right next to eachother would be ideal. If there is an actor, between them, who's code is the result of the lag this would cause the two to move a

The same thing happens with constraining an actor to another , I am constraining a hitbox to the main hero actor, the hit box is attached on the hero's head and uppper body , i set it to be visible to