Since this is a pretty straightforward action (no physics involved), it all comes down to this:
There are many methods of working around the collision event, but all of them will eventually be ineffective if you don't keep the following in mind:
The way GE movement works, actors don't actually move. They jump by the amount of pixels you tell them to per frame. So if I told an actor
- Code: Select all
x = x + 3;
it would jump three pixels to the right with each frame.
In many cases, the collision engine in GE will not register a collision because actors simply jump ahead / skip the actor they are supposed to be colliding with. A few different flaws can trigger this:
- The actors colliding with each other are too small / thin
- The actors moving are too fast
- Your fps (frames per second) rate is too low.
The higher your fps rate is, the less velocity you have to trust your actors with and the more precise your collision detection will be, respectively.
If these aspects don't take care of your problem sufficiently, there are a couple of more twists to the collision engine (and even standalone custom engines) we can point you to.
NOTE: It is imperative that when adding gravity, you also implement a limit. Don't let your actor accelerate infinitively.
- Code: Select all
yvelocity += 0.5;
if (yvelocity >= 10) yvelocity = 10;
// using 60 fps, which is a pretty solid rate for collisions.
