3 times and for some reason i can't get the destroy command to work on my main actor when it collides with my second actor- which was lava in the video. Its like a glitch. Any help?

despite being barren of graphics except for the player character and a single enemy{and the level itself being the size of a menu scene.;}

When the app starts, they are correct (all true). I go to the options scene and change option1 and option2 and then go back to the initial scene. It correctly displays the text "false true fa

spawn a set amount of crates perfectly on top of the ones below after placing a set amount of crates close to perfect, to act as a boost of sorts. If anyone could look at the template and see if you

@QASalad when I press play in the preview the log in thing at the top pops up. Also when I press any 3 of the buttons something pops up .. so its set up right but I just can't test it

@Chunkypixels of the top of my head, sherman, panzer, tiger.

Go to https://developer.apple.com and click the "member center" button on the top right corner.

2 will be brand new to me as i have never created any game with attacks or i am not sure what your hero will use to destroy enemies.

Actor logic is processed from the top down.

Back in my original project I slightly moved a "Change Attribute self.Graphics.Visible = true" and suddenly the problem went away... Now the text is displayed on top of the actor eve

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