User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > This new "dancing" that is prevalent since the update.
Page:
 
panther17
offline
Link
 
Originally posted by Shagrat
Originally posted by Eric the Great of Antarctica

There are plenty of elusive backs that are successful. You're just pissed because we won't share with you. I am telling you that elusive backs work FINE. Its just the standard elusive back build that is problematic and apparently has been since season 1. Hmmmmmm. Perhaps people post bad advice to stay at the top of their game? Wouldn't surprise me one bit. While I am willing to agree that the ACCEPTED elusive back build doesn't work, I refuse to say that elusive backs as a whole don't work. There are just too many guys MAKING it work.


Um which one of your HBs are you talking about? The lvl 15 playing in the A leagues?


Mine seems to do alright. 5.1 avg for last year. Haven't had the opportunity to see how he will do this year yet.
http://goallineblitz.com/game/player.pl?player_id=125529
 
Bukowski
offline
Link
 
Yeah - last season.

Which isn't really what we're talking about.

Elusive RBs have a problem right now, not last season.
Last edited Jul 31, 2008 00:48:02
 
pestface
offline
Link
 
I think the biggest problem is just the HBs who stand in the middle of a giant hole, daydreaming about being elusive, then 5 seconds later finally decide to keep going.

No RB, not in high school and not in the NFL just stands in a hole like that. If a tackler is coming up, they might try to fake and thus have reason to stutter step a bit. But if there's open space, he's going to go for it and do his elusive thinking on the way there. There's no reason to stand around faking and stuttering when your blockers did a good job.

The elusive backs should pick the best path to avoid any contact, and if he feels like it maybe throw in some jukes or head fakes just to improve his chances, but he should try to keep his speed up wherever he's going. Only when a tackler closes in should he start pulling his stutter-step and spinning moves or whatever makes him look like he's not gaining any yards.
 
Bukowski
offline
Link
 
Originally posted by pestface
I think the biggest problem is just the HBs who stand in the middle of a giant hole, daydreaming about being elusive, then 5 seconds later finally decide to keep going.

No RB, not in high school and not in the NFL just stands in a hole like that. If a tackler is coming up, they might try to fake and thus have reason to stutter step a bit. But if there's open space, he's going to go for it and do his elusive thinking on the way there. There's no reason to stand around faking and stuttering when your blockers did a good job.

The elusive backs should pick the best path to avoid any contact, and if he feels like it maybe throw in some jukes or head fakes just to improve his chances, but he should try to keep his speed up wherever he's going. Only when a tackler closes in should he start pulling his stutter-step and spinning moves or whatever makes him look like he's not gaining any yards.


Very well said. Exactly how I feel.
 
Kevin Smith
offline
Link
 
Originally posted by Doc
Here's another from a different player / league:

http://goallineblitz.com/game/replay.pl?game_id=82459&pbp_id=1077



Lol, thatīs a good one.

 
Bort
Admin
offline
Link
 
Originally posted by Bukowski
Its really simple to me: Elusive Backs worked great last year, we need to just go back to that.

What would be wrong with just coding elusive backs, just like last season?


They stutter stepped last season too. They have since season 1 in various forms.
 
panther17
offline
Link
 
Originally posted by Bukowski
Yeah - last season.

Which isn't really what we're talking about.

Elusive RBs have a problem right now, not last season.


I was kind of defending the guy saying elusive backs work fine but I also said I haven't had chance to see how he is doing this season.
 
panther17
offline
Link
 
Originally posted by Bort
Originally posted by Bukowski

Its really simple to me: Elusive Backs worked great last year, we need to just go back to that.

What would be wrong with just coding elusive backs, just like last season?


They stutter stepped last season too. They have since season 1 in various forms.


Yeah. I noticed it went down though as my agility and vision went up. IDK
 
HERO
offline
Link
 
Stutter step may have worked last year but it's on serious overdrive right now.
 
Melancholy
offline
Link
 
Originally posted by Bort
Originally posted by oldskool

It seems like the paths it's generating are good, it just takes too long to generate them and it gets confused too easily.

If you don't want to outright scrap it, maybe set it so that when it picks an "optimum" path, it goes that direction for some arbitrary length of time before re-checking its path, so that instead of dancing around going nowhere they'll be gaining positive yards?


It generates a new path every tick, so yeah maybe that's contributing to the problem.
I can certainly try something like that - I'm just worried we'll never be able to see Barry Sanders type moves if that's the way it goes.


I don't know, in the majority of the replays that I've seen where this is an issue, it seems like the player with the ball just got to a "clearing". Obviously this is a guess, but I'm suspicious that it's not the frequency of regenerating the path that is causing the problem, but how many possible paths with similar "scores" there are once the path gets clear. Instead of just holding back how often the path is checked, you might be able to get away with some combination of the following.

1) calculate distance to nearest defender along with path checking, the closer the nearest defender, the shorter the path is valid for. This way if there is someone nearby, the guy with the ball still has the chance to bust the barry sanders on the defender, but if the guy is in the clear, he'll be happier to reach top speed than to keep cutting.
2) give the current path a bonus when calculating path scores. in other words, when re-checking the path, even if the current path isn't the absolute best, let the guy stay on it unless there is another path that is significantly better. I'm very suspicious that since there are so many good paths for the ball handler to take when he gets out to the open, the guy just keeps picking a new one every tick even though the path he is on is barely worse than the new path that is selected.
 
Bukowski
offline
Link
 
Originally posted by Bort
Originally posted by Bukowski

Its really simple to me: Elusive Backs worked great last year, we need to just go back to that.

What would be wrong with just coding elusive backs, just like last season?


They stutter stepped last season too. They have since season 1 in various forms.


Yeah, they did.

But it was NOTHING like it is now. Its completely different..

Well built RBs didn't really stop in the open field, with no one around them, dancing around until someone tackled him - he found the hole and hit it.

I'm not saying Elusive was perfect last season, but it sure would be better than not being able to run Elusive at all.

I made a High Agility/High Speed/High SA Elusive Tree just for this season, now I'm worried that it was a waste of flex points, because all he does now is dance. He doesn't seem to know anyone else.

 
Itsatwap
offline
Link
 
Originally posted by Melancholy
Originally posted by Bort

Originally posted by oldskool


It seems like the paths it's generating are good, it just takes too long to generate them and it gets confused too easily.

If you don't want to outright scrap it, maybe set it so that when it picks an "optimum" path, it goes that direction for some arbitrary length of time before re-checking its path, so that instead of dancing around going nowhere they'll be gaining positive yards?


It generates a new path every tick, so yeah maybe that's contributing to the problem.
I can certainly try something like that - I'm just worried we'll never be able to see Barry Sanders type moves if that's the way it goes.


I don't know, in the majority of the replays that I've seen where this is an issue, it seems like the player with the ball just got to a "clearing". Obviously this is a guess, but I'm suspicious that it's not the frequency of regenerating the path that is causing the problem, but how many possible paths with similar "scores" there are once the path gets clear. Instead of just holding back how often the path is checked, you might be able to get away with some combination of the following.

1) calculate distance to nearest defender along with path checking, the closer the nearest defender, the shorter the path is valid for. This way if there is someone nearby, the guy with the ball still has the chance to bust the barry sanders on the defender, but if the guy is in the clear, he'll be happier to reach top speed than to keep cutting.
2) give the current path a bonus when calculating path scores. in other words, when re-checking the path, even if the current path isn't the absolute best, let the guy stay on it unless there is another path that is significantly better. I'm very suspicious that since there are so many good paths for the ball handler to take when he gets out to the open, the guy just keeps picking a new one every tick even though the path he is on is barely worse than the new path that is selected.


Great post.
 
Combatt
offline
Link
 
I have a LOLB with 55 speed and 57 agility/ 43 vision. He runs in much the same way as these backs.
Last edited Jul 31, 2008 05:29:54
 
arteryman
offline
Link
 
What's the update here Bort?
 
Potzer01 DTD
offline
Link
 
Reposting from the punt returner thread...

I bet I know what this is.....
Basic AI:

Vector2 diff = Normalize(playerPos - tacklerPos);
float dot = tacklerDirection.perpDot(diff);
if (dot < 0.0f)
// Turn one direction
else if (dot > 0.0f)
// Turn the other direction

float Vector2:: perpDot(const Vector2& v) const {return -this->y * v.x + this->x * v.y;}

So since the nerf on speed backs, which I assume was something to the effect of
if( length(newdir -prevdir) > 0.1){ velocity*=.1;}

Then whats happening is the direction is constantly swapping left right left right every frame.. and velocity == epsilon (~0, almost nothing)

The fix is to not recalculate the heading if length(velocity) < (some value determined by ballcarrying settings and players agility and speed)

Oh come on, its not optimal path, its the heading...

Spamming this as its a better description of the problem and potential solution =x


**** Edit...

So from looking at the play on the top the matter is even worse... Bort doesn't do float dot = tacklerDirection.perpDot(diff);

He does Vector2 diff = Normalize(playerDir - Normalize(playerPos- tacklerPos));
float dot = tacklerDirection.Dot(diff);
if (dot < 1.0f)
// Turn one direction
else
// Turn the other direction

So the formula as I stated to begin with would solve the problem.
Last edited Jul 31, 2008 23:24:22
 
Page:
 


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