User Pass
Home Sign Up Contact Log In
Page:
 
Sciz
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=896246&pbp_id=17350814

Vision is 24 and Agility is 40. But still, wtf?
Edited by Sciz on Nov 17, 2009 18:35:45
 
acrnobrnja
offline
Link
 
Failed Vision check. Only possible explanation. Especially with 24 vision.
 
NYJets52
offline
Link
 
Failed visions check or not that is pathetic. He might as well run backwards.
 
Sciz
offline
Link
 
Yeah. If nothing else, going out of bounds needs to depend on something other than a vision check.
 
bberyquiet
offline
Link
 
I realize that it probably is a vision check, but it seems like every bug reported in this forum is being explained as a vision check. Enough already, it's not Stevie Wonder and Ray Charles out there. Kids in Pop Warner leagues don't run out of bounds like that.
Fix the damn sim, will ya????
 
Troymk1
offline
Link
 
No it was Low Ag vs High Speed (he can't turn)

We've seen this reported a fair bit at lower levels
 
Sciz
offline
Link
 
I have plays of him making that turn easily back when he had 60 speed and 20 agility. Why would increasing both make him worse?
 
tragula
title
offline
Link
 
Originally posted by bberyquiet
I realize that it probably is a vision check, but it seems like every bug reported in this forum is being explained as a vision check. Enough already, it's not Stevie Wonder and Ray Charles out there. Kids in Pop Warner leagues don't run out of bounds like that.
Fix the damn sim, will ya????


It is a computer simulation, vision checks is the main (and almost only) mechanism to make the dots looks like making human decisions. Vision checks are fundamental to the game and most of the time a dot acts "humanly" and make something weird, it is due to a failed vision check.

http://www.youtube.com/watch?v=AIWWrdDNBRU&feature=related
http://www.boomclips.com/videos.aspx/video~dumbest_football_play_ever/Dumbest_Football_Play_Ever/Stupid_videos/

Saying that, I doubt that the OP is a vision check, since you can see him adjust his path toward the sideline (a failed vision check would send him in a straight line). The wrong angle of the turn also make the high speed/low agility hypothesis weird.
Edited by tragula on Nov 17, 2009 21:59:45
 
TrevJo
offline
Link
 
Originally posted by NYJets52
Failed visions check or not that is pathetic. He might as well run backwards.


Originally posted by Sciz
Yeah. If nothing else, going out of bounds needs to depend on something other than a vision check.


Agreed. I don't care if the HB has 10 vision, that should never happen.
 
PING72
offline
Link
 
I see this a lot...it really is annoying.
 
TrevJo
offline
Link
 
Originally posted by PING72
I see this a lot...it really is annoying.


Really? If you have other links, please add them.
 
acrnobrnja
offline
Link
 
Originally posted by tragula
Saying that, I doubt that the OP is a vision check, since you can see him adjust his path toward the sideline (a failed vision check would send him in a straight line). The wrong angle of the turn also make the high speed/low agility hypothesis weird.


Ok maybe not failed... But scared vision check? If you look right when he should turn up field, he is lined up with the unblocked CB in the hole. I think "weird" vision check made him notice the defender there and try to kick it more outside. Then the low agility problem kicked in and he couldn't turn back up field (if you look, he nears the sideline and tries to turn back inside). I know it sounds like a weird reason, but it's the best I can come up with now that I actually spent time looking at it.
Edited by acrnobrnja on Nov 18, 2009 15:54:11
 
NiborRis
offline
Link
 
What's his running style? I have a theory on how this happens, and I've posted it a few times, but I don't know how to fix it.

Basically, it appears that the "avoid sideline" effect is created by adding a vector to run away from the sideline when you're within X feet of the sideline. This is why you sometimes see the zig-zags down the sideline instead of a smooth line - the HB runs away from a defender, then gets close to the line and far from the defender and bounces back in, then is far enough away from the sideline that he ignores it but sees the defender again and bounces out, and so on back and forth.

So, in these cases, I suspect the running style is set heavily towards Power (although the faster you are, the more towards Elusive you could be and see this). This causes you to be updating pathing only every several ticks - maybe as long as 5 or 8 or so, I don't know the number. So at some point, you have a pathing update, and you're, say, X+1 feet away from the sideline, so your pathing says "ignore the sideline, you're too far away to worry about it" and you end up running fairly sideways to avoid some D players. Then, because you're traveling so fast, by the time you have a new pathing update, you're very, very close to the sideline. All of a sudden you try to cut inside, but your low agility can't handle it. Thus, you right right straight out of bounds.

Vision isn't a factor, unless it impacts the distance at which you worry about the sideline.

What can help as a player is to run more Elusive, and have better agility. Also, however, the sideline logic could be improved to be based on not just distance, but distance, speed, projected impact time to the sideline, that sort of thing.
I think optimally the pathing should just check "will i be out of bounds before my next path check; if so, adjust my route back in bounds (except for whatever conditions cause a runner to want to just run out of bounds to avoid contact)" but that's actually a pain to do. I'd settle for a more fluid vector to avoid the zigzag and these boundary scenarios where you just bolt out of bounds.
 
NiborRis
offline
Link
 
In fact, in this case, I can see when the sideline vector kicks in and he tries to make the turn (with WOEFUL agility given his speed). The sideline vector always seems to kick in right about where the hash marks end, and it happens here too - he's running straight sideways until he hits those hash marks, then he tries to turn.

I don't know why he's running straight sideways until then, though. SuperElusive? Anything less and you should have a bigger "run to the endzone" vector. Bad vision may be making him think there's defenders closer than there are, I suppose, instead, causing him to want to run wider around them.

In any case, this might not be the "boundary condition" problem of the sideline vector, but it's certainly an issue where the sideline vector is hardcoded and doesn't work well for this RB's speed/agility.
 
Sciz
offline
Link
 
+50 running style, if it helps
 
Page:
 


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