User Pass
Home Sign Up Contact Log In
Page:
 
minjit
offline
Link
 
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
Last edited Nov 3, 2008 08:54:37
 
OttawaShane
offline
Link
 
Again, where the hell is Bort?
 
Tobysmith6922
offline
Link
 
I thought the point of this was to figure out why the FS runs in circles....
 
minjit
offline
Link
 
The point was to figure out why FS don't take the best possible path... even with ridiculously high vision and we are still clueless...
 
Link
 
it makes me wonna jump out the window - i love the cover1 shell but with that bug which is STILL UNADDRESSED by bort its very risky/useless

and im also wondering why bort doesnt make a comment about this issue - as DC im very "unhappy" about this issue
 
saintedix
offline
Link
 
Originally posted by minjit
The point was to figure out why FS don't take the best possible path... even with ridiculously high vision and we are still clueless...


There is no issue here. It is a lack of agility. Show me a FS with 70 speed and 70 agility taking a route like this and I'll believe it. Every example that people are throwing out about bad FS pathing is from a FS with 80 speed and 55 agility.
Last edited Nov 3, 2008 23:34:46
 
Link
 
Originally posted by saintedix
Originally posted by minjit

The point was to figure out why FS don't take the best possible path... even with ridiculously high vision and we are still clueless...


There is no issue here. It is a lack of agility. Show me a FS with 70 speed and 70 agility taking a route like this and I'll believe it. Every example that people are throwing out about bad FS pathing is from a FS with 80 speed and 55 agility.


ya right...agility is the reason why FSs get >> behind << the ball carrier and try to chase them down - complete nonsense but i think you know that...
 
saintedix
offline
Link
 
Originally posted by Knut the Bruin

ya right...agility is the reason why FSs get >> behind << the ball carrier and try to chase them down - complete nonsense but i think you know that...


Same thing happens with CB's that have too high of speed w/o matching agility (called the CB hook path, notorious in the pro leagues where CB's have 90+ speed and only 60 agility).

The path that a player chooses is adjusted all the time. The FS likely chooses a decent path to start, but when he starts on that path, he doesn't have the agility to change his course, thus he "misses".

The FS on my team has 70 speed and 70 agility and I have never once seen him make an error like this, even in cover 1.
 
Link
 
their is "no need" to change the path that big time once the FS has realized the "interception point" cause the WRs are running straight lines most of the time (at least as long as they arent feeling a tackler) so the FSs have to run just a straight line to the point of interception

if i run a straight route and you want to catch me...you wont calculate your running path every time if i dont change my direction?

maybe in GLB you dont have that issue if you have enough agility but thats not a solution to the problem its a workaround at its best cause it shouldnt be a agility issue - vision is the attribute to figure out plays and the likely point of interception....if you have low vision your "guess" of the point would be bad but you still would run "right" even if the point is "false"
 
minjit
offline
Link
 
Originally posted by saintedix
Originally posted by Knut the Bruin


ya right...agility is the reason why FSs get >> behind << the ball carrier and try to chase them down - complete nonsense but i think you know that...


Same thing happens with CB's that have too high of speed w/o matching agility (called the CB hook path, notorious in the pro leagues where CB's have 90+ speed and only 60 agility).

The path that a player chooses is adjusted all the time. The FS likely chooses a decent path to start, but when he starts on that path, he doesn't have the agility to change his course, thus he "misses".

The FS on my team has 70 speed and 70 agility and I have never once seen him make an error like this, even in cover 1.


I'm sorry, but my HB with 90 speed and 60 agility has no problem making cuts 30 times as sharp. The agility is not the issue.

Also, when agility is an issue, you see a wide turn. Not a sharp turn one way and then a sharp turn to the correct direction (which is what currently happens occasionally). The fact that your team's FS hasn't the problem occur is more luck than anything else: the problem doesn't always happen. My FS has yet to have it happen to him from the plays I've watched, but it happens often enough to FS with better stats to where it is an issue.

Watch this play: http://goallineblitz.com/game/replay.pl?game_id=144447&pbp_id=3429303 and tell me that's not a pathing issue. There is no reason for those players to not continue to the cutoff point...

Disclaimer: I don't know the vision on those 3 players that started going the wrong direction, but it happens to people with 70 vision so I'm just posting an extreme case to show the issue... Also, from the sharpness of the cut that the 3 of them make and the timing, it really makes it seem like a code issue.
Last edited Nov 4, 2008 01:27:43
 
RAPB
offline
Link
 
Originally posted by minjit
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


1.) Agreed: when vision is low, bad reads should result. Problem here: decent vision (60 - 70) shows how the SIM is set up: the safeties calculate the CURRENT speed and direction of the ball carrier - so they head for the man right from the start. Instead, they should GUESS the FUTURE position of the ball carrier and secure the endzone.

2.) It would be a GREAT improvement if the safeties headed for the endzone! Really!!! Instead, the safeties head towards OPPONENTS endzone first - this way giving up their deeper position; again: they head for the intersection point calculated by their (possible) speed and the ball carriers CURRENT speed and direction (which is about zero/none as the ball is caught or the ball carrier cuts).

3.) It's not running towards the goalline, touching it and then turning to tackle. It's about the first direction the safeties should choose: towards the corner of the endzone, calculating maximum progress the ball carrier could possibly get (again: not based on the current movement of the ball carrier, but the estimated, possible advance during the time the safeties need to get close). As they get closer to the ball carrier, they consider the current movements more and more. So safeties don't mind going 3 yards too deep; safeties mind not going deep enough and allowing the ball carrier to get by!
Again: Right now, the first step and first direction taken is upfield, towards the current spot of the ball carrier. It's giving up the deeper field position and then chasing down from behind instead of getting in the path.

To break it down:

SIM: chase down from behind, let the ball carrier get deeper first to do so
should be: get in the path, always stay deeper than the ball carrier


_____________________________________

Originally posted by saintedix
...

The FS on my team has 70 speed and 70 agility and I have never once seen him make an error like this, even in cover 1.


That one made me chuckle!

1.
We're not talking about rather slow FS that are not able to fulfil their most important assignment: not to let anyone EVER get behind them and to be able to catch anyone trying for the catch&run.

2.
http://goallineblitz.com/game/replay.pl?game_id=200847&pbp_id=10118523

(took me about a minute; not a good example, but it's the circle-motion)

Oh... and talking about 70 speed:

http://goallineblitz.com/game/replay.pl?game_id=200847&pbp_id=10121650

Wait till first receivers or HBs got 90 speed. You'll see why safeties need more than 70 speed then. And you'll see your 70 agility guy still make awesome cuts, turns and motions - exept when you need it most: to prevent the big play. Then he'll act like an idiot.
Last edited Nov 4, 2008 05:41:41
 
saintedix
offline
Link
 
Yeah RAPB, the FS couldn't keep up with a WR that has 90+ speed. Well, neither could my CB with 81 speed (LaDaJerious) in the replay you showed. That still doesn't address the current bug at hand.

 
OttawaShane
offline
Link
 
Originally posted by saintedix
Yeah RAPB, the FS couldn't keep up with a WR that has 90+ speed. Well, neither could my CB with 81 speed (LaDaJerious) in the replay you showed. That still doesn't address the current bug at hand.



Didn't you say in the other thread that this isn't a bug, its related to agility being too low?
 
minjit
offline
Link
 
Originally posted by OttawaShane
Originally posted by saintedix

Yeah RAPB, the FS couldn't keep up with a WR that has 90+ speed. Well, neither could my CB with 81 speed (LaDaJerious) in the replay you showed. That still doesn't address the current bug at hand.



Didn't you say in the other thread that this isn't a bug, its related to agility being too low?


Actually, he said it further up on this page.
Last edited Nov 4, 2008 13:47:15
 
Tobysmith6922
offline
Link
 
Originally posted by saintedix
Originally posted by minjit

The point was to figure out why FS don't take the best possible path... even with ridiculously high vision and we are still clueless...


There is no issue here. It is a lack of agility. Show me a FS with 70 speed and 70 agility taking a route like this and I'll believe it. Every example that people are throwing out about bad FS pathing is from a FS with 80 speed and 55 agility.


So low agility makes a FS run in a circle and figure 8 pattern instead of going for the tackle???...Wow..
 
Page:
 


You are not logged in. Please log in if you want to post a reply.