line actor is above the other two actors in the layer. But if you place the line actor at the bottom of the layer, there is a significant lag in the position of the line, as you can see if you drag t

Edit: Only after posting do I notice the bullet fire from over the aliens not under. They, erm, have cannons mounted on top. Yeah, that's what it is.

In respect of scrollable / non-scrollable layers - and the way collisions interacts with them, I'd say it does produce consistent and expected results (although I'd agree with you that it might not be

My goal is not to simply detect a collision at the top of a tall scene. I can do that a myriad of ways. While I really do appreciate your suggestions of workarounds, and will try them out in my produc

I wouldn't really call it a bug, a non-scrollable layer is primarily designed for HUD elements, so generally speaking (the overwhelming majority of cases) there would be no need for interaction betwee

(Quote)

Most of the time (90%?) the Display Text appears on top of the actor's image, as expected. However, randomly, on some instances the actor's Display Text appears sorted BEHIND the actor's image. Anyone

I have a "Main Char" actor which is controllable by arrow keys and walks around a top-down / bird's eye map. The character shoots where the mouse is clicked. I would like to constrai

1) Make your HUD layer scrollable and move it so it is above Actor A.

But In other words, actor A, the Hero, is on a scrollable layer and trying to detect collisions with Actor B. If Actor B is also on a scrollable layer everything is fine. But if Actor B is on a non-sc

How would actor A be able to collide with actor B . . . when B is on a non-scollable layer, so A could never move towards it (in your set up where the camera tracking area is closed down) ?

The only thing I could work out (I might be wrong) was that you wanted to have a movable actor collide with a second actor . . . when the second actor is off screen and on a non-scrollable layer ? In

So, turns out that the problem occurs when an actor on an un-scrollable layer collides with an actor on a scrollable one. I have attached a test project where an actor called detector displays the te

(Quote)

Thanks @Socks. I didn't think that sounded likely, but I am unfamiliar with LUA. I did a test and layer order does not in and of itself seem to be an issue so I'll have to dig deeper. Thanks again.

-Destroy actor

But seriously I can't think of anything off the top of my head, but there have been impressive games made with GS, maybe check out the Game of the Month threads, or something like Spooky Hooves . . .

up top there will be a health bar

(Quote)

I think at a time when people would likely be more unsure about the future of the software than they have been for years keeping them up to date might dispel their concerns - (but who knows, maybe the