Originally posted by RAPB
Originally posted by minjit
It's probably not even a problem with the algorithm Bort is using because it's a fairly simple algorithm, but just a bug in the code...
I mean the algorithm isn't hard, based the FS's vision, he should be able to estimate the player's speed to a certain accuracy and he knows his speed so you have two time dependant vectors and you draw them and the FS should run to where they intersect (unless it's past the endzone). Sure, it takes some graph theory on deciding the best path, but there are tons of algorithms out there. Here the vision accounts for how accurate the FS's vector is and everything else is fairly straight forward. I'm sure that's how Bort's is implemented or some variation on that and that's not the issue.
That's EXACTLY the issue!
Because in football, this is NOT what players do:
- when beeing far away, only a REALLY DUMB kid is running straight for the man
- smart players calculate the ESTIMATED speed and direction LATER ON (not the present one!!!) - so they don't care if the guy is moving slowly or changing direction RIGHT NOW (for as they are there, he either is tackled already or heading towards the endzone)
- other players - especially safeties - got assignments that they care more about than the actual opponents position and direction: secure the endzone is more important than getting close to the man first; so a FS/SS rather far away will head for the endzone FIRST and turn towards the ball carrier not before he's deeper and able to prevent the easy TD-run
So the general "chase-down" logic is not realistic for the safeties at all. The "secure the endzone" logic should override as long as the safeties are rather far away from the ball carrier.
I'll tackle your points 1 at a time.
1) Never in the algorithm mentioned do I say anything about going straight for the man. Vision would allow you to estimate where he would be better. That's all. If you have awful vision, then you are a really dumb safety and therefor should be doing stupid stuff.
2) The direction he's going is towards the endzone, that is the vector you use and his speed I was talking about is his NUMBERICAL speed. i.e. how fast he CAN run. The vector won't just be a vector at any given time, but the average of a few of the ball carrier's vectors so that the player's overall direction is still towards the endzone.
3) The chasedown logic applies completely. When have you even seen a safety run backwards, get to the endzone, turn around to make the tackle? lol Yes, the safety's job is just that, to be a safety, but that doesn't mean they don't take the BEST route which is to run to where they think they player will be. It's stupid to run PAST that spot and then come back... lol
Originally posted by minjit
It's probably not even a problem with the algorithm Bort is using because it's a fairly simple algorithm, but just a bug in the code...
I mean the algorithm isn't hard, based the FS's vision, he should be able to estimate the player's speed to a certain accuracy and he knows his speed so you have two time dependant vectors and you draw them and the FS should run to where they intersect (unless it's past the endzone). Sure, it takes some graph theory on deciding the best path, but there are tons of algorithms out there. Here the vision accounts for how accurate the FS's vector is and everything else is fairly straight forward. I'm sure that's how Bort's is implemented or some variation on that and that's not the issue.
That's EXACTLY the issue!
Because in football, this is NOT what players do:
- when beeing far away, only a REALLY DUMB kid is running straight for the man
- smart players calculate the ESTIMATED speed and direction LATER ON (not the present one!!!) - so they don't care if the guy is moving slowly or changing direction RIGHT NOW (for as they are there, he either is tackled already or heading towards the endzone)
- other players - especially safeties - got assignments that they care more about than the actual opponents position and direction: secure the endzone is more important than getting close to the man first; so a FS/SS rather far away will head for the endzone FIRST and turn towards the ball carrier not before he's deeper and able to prevent the easy TD-run
So the general "chase-down" logic is not realistic for the safeties at all. The "secure the endzone" logic should override as long as the safeties are rather far away from the ball carrier.
I'll tackle your points 1 at a time.
1) Never in the algorithm mentioned do I say anything about going straight for the man. Vision would allow you to estimate where he would be better. That's all. If you have awful vision, then you are a really dumb safety and therefor should be doing stupid stuff.
2) The direction he's going is towards the endzone, that is the vector you use and his speed I was talking about is his NUMBERICAL speed. i.e. how fast he CAN run. The vector won't just be a vector at any given time, but the average of a few of the ball carrier's vectors so that the player's overall direction is still towards the endzone.
3) The chasedown logic applies completely. When have you even seen a safety run backwards, get to the endzone, turn around to make the tackle? lol Yes, the safety's job is just that, to be a safety, but that doesn't mean they don't take the BEST route which is to run to where they think they player will be. It's stupid to run PAST that spot and then come back... lol
Last edited Nov 3, 2008 08:54:37






























