next »

[cubertron]

I am making a platformer game for android using ANDEngine. The engine only provides hitbox collision and the method returns true/false in case of collision/no collision.

My questions:
1) How can I implement the basic character physics without using Box2D. Should I use some trigger points(left/right top/bottom) around the player to manage vertical and horizontal movement?

2) If I have like 100 tiles, should I iterate through all the list to check if player collided with anyone of them? Won't this be super slow?Is there a way to optimize this?

Thanks!

[randomnine]

Hey.

1) This thread ought to give you some ideas.

2) Assuming your tiles are snapped to a grid, put them in a 2D array such that their position in the array corresponds to their position in the world. The character's X/Y location at any given time will then map to a certain position in that array. You'll be able to test the character against just the tiles immediately around them.

[Aloshi]

Regarding your second question, this explains it quite nicely.

[Vadinci]

How I usually handle this is to give the player a xspeed and an yspeed variable. In the update loop you move the player over the x-axis by the amount of xspeed. once you have done that , you check for collision; if there is none, continue. if there is a collision however, move the player in the opposite direction 1 pixel at a time, until there is no more collision. Then set the x-speed to 0. now do the same for the yspeed.

I don't usually work with hitboxes for my tiles though, instead I have a 2d dimensional array which holds a boolean for each tile, stating if they are solid or not.

I hope you can do something with this good luck

[cubertron]

Regarding your second question, this explains it quite nicely.

Thanks for it :D , I was actually thinking something like this but was not sure if it is a good method or not.

How I usually handle this is to give the player a xspeed and an yspeed variable. In the update loop you move the player over the x-axis by the amount of xspeed. once you have done that , you check for collision; if there is none, continue. if there is a collision however, move the player in the opposite direction 1 pixel at a time, until there is no more collision. Then set the x-speed to 0. now do the same for the yspeed.

I don't usually work with hitboxes for my tiles though, instead I have a 2d dimensional array which holds a boolean for each tile, stating if they are solid or not.

I hope you can do something with this good luck

So if you use 2d arrays, then how do you handle the collision?I mean the boolean array is good enough to know if the tiles are solid are not, but what for the positioning?If you use move the player 1 pixel at a time until the collision is over, doesn't this looks a bit weird(considering in terms of visual, like if the player is in half of the tile)

[Vadinci]

So if you use 2d arrays, then how do you handle the collision?I mean the boolean array is good enough to know if the tiles are solid are not, but what for the positioning?If you use move the player 1 pixel at a time until the collision is over, doesn't this looks a bit weird(considering in terms of visual, like if the player is in half of the tile)

It's not moving 1 pixel per frame, it's moving by 1 pixel until there is no collision anymore, so

Code:

while(collision)
{
 //move by 1 pixel
}
xspeed = 0;

so what will happen is, say the player has a xspeed of 10, and there is a tile 4 pixels to the right of the player. The player will move by 10 pixels, and register a collision, now it starts moving 1 pixel to the left in a loop, until there is no more collision; this will happen after 6 loops. At the end of the game tick, the player has effectively moved 4 pixels to the right, and touches the tile.

regarding the boolean array, I made my own hitbox-ish system, and I check for important points within the hitbox. Each of these points I translate to a point in the boolean array (which is simply dividing the coordinate by the Tile width and/or height, and then flooring it). It's just a different way of checking for collision.