@AxiomVerge Hi, you already told me you were using mostly AABB collisions in AV, how did you manage the slopes, like when you're walking over save stations?
I have a not so good solution where I find the depth the box intersects the line in x and y and push back by the smaller (as if it were a box on box collision). Always causes me problems. I think @BitKidGames did something much simpler like just have it slide along the line.
-
-
Yea, I don't allow any intersections. Since the game is pixel based I break down the velocity into pixel increments and test each one before inching them a pixel at a time. The only tricky part is slopes, they have to be handled specially (ignore horz. checks, do vert. correction
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Here is an explanation I wrote a long time ago: https://web.archive.org/web/20161225190606/http://bitkidgames.com/?p=2221 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You’re awesome guys, thanks a lot for taking the time!! I can’t decide between tile based aabb collisions or bigger polygons (vectorial) collisions, you’re input is helping me right now. Cheers
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I cheat and ignore the box for slope intersections. I only intersect with the player's "foot" (a point at the bottom center of the bounding box.) I wrote a bit about it forever ago over here: http://thirdpartyninjas.com/blog/2010/07/28/sloped-platform-collision/ …
-
It's similar to what
@Jamezila and@NoogyTweet were doing back then in their games, and I really liked it. - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.