Or I could be smoking rocks, and reading too much of my co-workers broken code =x
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > This new "dancing" that is prevalent since the update.
Originally posted by Potzer01
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.
It uses vectors, but you're not really close at all.
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.
It uses vectors, but you're not really close at all.
fate3283
offline
offline
It seems to me that the elusive setting it trying to make the back avoid ALL defenders rather than just immediate threats. The Aura of Intimidation is supposed to effect players within a certain distance of your player, why not only try to avoid tacklers within a certain area, while only ever moving forward?
If there is a tackler coming from the left and one from the right it looks like the back redirect left/right to avoid them when instead he should run forward and he'd be fine. He should run straight ahead and deal with the next level of defenders.
If there is a tackler coming from the left and one from the right it looks like the back redirect left/right to avoid them when instead he should run forward and he'd be fine. He should run straight ahead and deal with the next level of defenders.
fate3283
offline
offline
Or maybe, based on vision, they would have a larger cone of vision, but had a priority check so they will still be 'aware' of the defenders down the field but will make sure the guy in front of him is dealt with first.
http://goallineblitz.com/game/replay.pl?game_id=78819&pbp_id=350448
Here the returner was set to Elusive but ran straight ahead until it was too late. I agree with the eventual 'blocking sucked' response, but I also think the right choice would have been to cut right instead of left.
So the check would make him him cut to avoid the closest tackler but the secondary check for the rest of the defenders in his cone of vision would make him see that right was the best choice.
http://goallineblitz.com/game/replay.pl?game_id=78819&pbp_id=350448
Here the returner was set to Elusive but ran straight ahead until it was too late. I agree with the eventual 'blocking sucked' response, but I also think the right choice would have been to cut right instead of left.
So the check would make him him cut to avoid the closest tackler but the secondary check for the rest of the defenders in his cone of vision would make him see that right was the best choice.
zollins5
offline
offline
Originally posted by fate3283
Or maybe, based on vision, they would have a larger cone of vision, but had a priority check so they will still be 'aware' of the defenders down the field but will make sure the guy in front of him is dealt with first.
http://goallineblitz.com/game/replay.pl?game_id=78819&pbp_id=350448
Here the returner was set to Elusive but ran straight ahead until it was too late. I agree with the eventual 'blocking sucked' response, but I also think the right choice would have been to cut right instead of left.
So the check would make him him cut to avoid the closest tackler but the secondary check for the rest of the defenders in his cone of vision would make him see that right was the best choice.
My WR does the same exact thing on almost every return. And here is one for my HB
http://goallineblitz.com/game/replay.pl?game_id=81776&pbp_id=804691 he was just about around the corner and then just stopped to adjust. He could have atleast gotten a couple more yards from that.
Or maybe, based on vision, they would have a larger cone of vision, but had a priority check so they will still be 'aware' of the defenders down the field but will make sure the guy in front of him is dealt with first.
http://goallineblitz.com/game/replay.pl?game_id=78819&pbp_id=350448
Here the returner was set to Elusive but ran straight ahead until it was too late. I agree with the eventual 'blocking sucked' response, but I also think the right choice would have been to cut right instead of left.
So the check would make him him cut to avoid the closest tackler but the secondary check for the rest of the defenders in his cone of vision would make him see that right was the best choice.
My WR does the same exact thing on almost every return. And here is one for my HB
http://goallineblitz.com/game/replay.pl?game_id=81776&pbp_id=804691 he was just about around the corner and then just stopped to adjust. He could have atleast gotten a couple more yards from that.
Tyroen Jones
offline
offline
Bah. I was standing on the sidelines and was watching the OP do the worm halfway down the field.....
outus
offline
offline
http://goallineblitz.com/game/replay.pl?game_id=79152&pbp_id=832333
This seems to be the right place to post this play.
My CB stopped in the center of the field and just shivered there until he was easily tackled. Only the K to beat and he was being blocked.
Not saying he was gone, but it looks like he stopped to tie his shoes.
This seems to be the right place to post this play.
My CB stopped in the center of the field and just shivered there until he was easily tackled. Only the K to beat and he was being blocked.
Not saying he was gone, but it looks like he stopped to tie his shoes.
You are not logged in. Please log in if you want to post a reply.






























