sadpmpk
/
HATPC
1
0
Fork 0
Code Issues 11 Pull Requests Projects 4 Releases Wiki Activity

Update 'Step 2: Player, Movement, and Collision'

master
sadpmpk 2023-01-01 23:21:28 -05:00
parent 3845050b05
commit b0ce6d54fd
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Step-2%3A-Player%2C--Movement%2C-and-Collision.md

@ -114,7 +114,7 @@ So, the goal is to implement a collision detection between AABB and AABB, and co
Thankfully, the lecture series does address both parts. What interesting is the proposed method of resolution. Rather than using the minimum overlap, it uses the overlap amount from the previous frame to determine which direction is the entity colliding towards. E.g. if the previous overlap is higher in the X direction, then the collision would be from the Y direction, and therefore the Y overlap should be used for resolution. For AABB resolution, this method works well enough. Thankfully, the lecture series does address both parts. What interesting is the proposed method of resolution. Rather than using the minimum overlap, it uses the overlap amount from the previous frame to determine which direction is the entity colliding towards. E.g. if the previous overlap is higher in the X direction, then the collision would be from the Y direction, and therefore the Y overlap should be used for resolution. For AABB resolution, this method works well enough.
There are a lot more to narrow phase collision when the bounding box is not limited to AABB. Outside of AABB, there are a lot more edge cases to consider. Particularly, I have thought about slopes quite a bit and how to handle that. One hard edge case that I can think of is how to resolve a collision between two consecutive tiles that forms a 'V' shape. Even just resolve normal slopes is already a challenge. For now, this will not be a focus. There are a lot more to narrow phase collision when the bounding box is not limited to AABB. Outside of AABB, there are a lot more edge cases to consider. Particularly, I have thought about slopes quite a bit and how to handle that. One hard edge case that I can think of is how to resolve a collision between two consecutive tiles that forms a 'V' shape. Even just resolve normal slopes is already a challenge, really. For now, this will not be a focus.
These are links that I find useful to reference when dealing with collision: These are links that I find useful to reference when dealing with collision:
- How N deals with collision: [link](https://www.metanetsoftware.com/2016/n-tutorial-a-collision-detection-and-response) - How N deals with collision: [link](https://www.metanetsoftware.com/2016/n-tutorial-a-collision-detection-and-response)