Create a new actor positioned under the actor you want the particles to spawn from; constrain the X and Y values of the new actor to the actor on top of it, and then spawn the particles from the botto

to the 'Side Collision - Damage' rule; that way the health will only be affected if the character is too low to be counted as a top jump

the goal is to create a science fictional top down multiplayer team based shooter (hopefully a 64+ player experience). Once development plans have been established we will proceed to begin work on pr

I discovered that as long as the actor in question is marked as MOVEABLE in the Physics properties, it does indeed return "true" as overlapping, even if it's spawned on top of the ot

But if you have one actor, and then spawn another one on top of it, there is no "overlapping or colliding" event (as they don't actually cross boundaries, they are simply overlapping

"Currently, my skid marks spawn on top of the car, and I'll need to make another actor that follows along with the car everywhere if I want it to leave skidmarks in the right order"

Or even a drop down list (Back of layer, back of actor, front of actor, front of layer). Personally, I don't need this level of control though, just "in front" or "behind&a

@gingagaming is the top guy round here for paid help.

Does anyone have any idea how I can destroy an attribute (unlock with XX coins) after I unlock the character?

Does anyone have any idea how I can destroy an attribute (unlock with XX coins) after I unlock the character?

I tried that, still nothing. It is really odd how it is set up. I am guessing it is that way due to all the camera rotations.

They need to be in the same layer group as the HUD.

(Quote)

I think you should extend your white trail a bit to bleed out of the shape. If you look closely, you can see it ends just shy of the top-left corner and it bends at the top edge of the icon.

I am playing around with a Deep Blue Apps template. It is called Soosiz2. I am a bit stumped on how you would add extra elements (score..etc) on the non (HUD) scrollable layer. When I do this they r

I remember a big optimization top being to uncheck moveable if an actor doesn't use it. Wondering if this still has performance benefits or if "can sleep" takes care of that. Just wo

there is a tizen campagin febraur onwards during this year to get 10000 Dollar if your app is in the top 100.

Obviously ^. But the point being, it's not easy even if you're a top talent in this field...

(Quote)

Dave is a top guy and one of the best, his knowledge with GS is 2nd to none, good luck finding a partner.