User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Why Do Defenders Run In Vertical Lines Where An Angle Would Be Better??
Page:
 
that1guy
offline
Link
 
Why is it that defenders with high vision take such messed up angles? I saw Bort just posted that he's fixing a similar bug on the offense and it would be great if he fixed it on the D side as well. i've seen other players do this but i only posted examples of my player because its easier to pull my own plays. i tried to get a response from Bort on the offensive thread where he was responding to the bug but i got no answer so i'll try a thread for the D

Originally posted by Bort
Good news is that somebody made an actual good suggestion on a fix for running pathfinding. I'm working with it right now in testing.

It's basically a double pass on the "best path" algorithm: one with a long vision distance for a general "avoidance vector" and one with a short, 3-5 yard distance for a "juke vector." Add 'em together, with the juke vector at a stronger strength than the avoidance vector, and it seems to get a pretty good path that really takes the runner's vision into account quite well.

is there a way that this "best path" algorithm can be used to help defenders take better angles of attack?

http://goallineblitz.com/game/replay.pl?game_id=125654&pbp_id=4805282 (this one was just a bad angle)

not the first time my FS has taken a poor angle and with 50 vision and 5 superior vision the guy is far from blind. there have been other plays where the FS is in persuit and seems to run to directly parrallel to the guy he's chasing, almost as if he can only opperate on straight lines.
http://goallineblitz.com/game/replay.pl?game_id=84788&pbp_id=2661714
Last edited Aug 20, 2008 01:04:00
 
Gazeruth
offline
Link
 
I'm just guessing here, but it looks like your FS may have the vision to choose a decent angle, but he doesn't have the speed to get to the player, on the first play, if he'd have taken a tighter angle, he probably wouldn't have got to the ball carrier as he's not quick enough.. what's the agil/speed.

Also on the second one, there was no chance for him to get to the carrier, and the AI attempted to find the angle that would be able to catch him.. which is so shallow you've have needed a good few pitches to catch him!
 
that1guy
offline
Link
 
The FS has 66speed and 45 agility, plus 3 pts in closing speed.
 
SB
offline
Link
 
Well, that's pretty average speed/agility at his level

I don't see anything wrong with the second play, the FS simply doesn't have the speed to catch the guy. The first play is an awful angle, as it seems like he does have the speed to take a better angle and make the tackle, I guess it could be a bug.
 
chief31
offline
Link
 
Both plays appear to have the defender taking the angle to (eventually) get in front of the ball-carrier. Obviously, the problem is that he needs to take an angle that will get him to the ball-carrier as quick as possible.

That, and he needs to be aware of where the end-zone is at.

I imagine that it will be awhile before we have a solution to this "bug". It seems like it would be a tough one to figure out.

What bothers me, is the way players don't seem to be able to run on any kind of rounded line.

The closest I have seen has been a HB taking alot of short angle-turns, giving the appearence of a round path. But that consists of the HB losing speed, with each of the little angles. It doesn't work.

But I imagine that one is even farther off.
 
SCACE
offline
Link
 
The main issue is with the goalline. A player should be taking the best angle to the ball carrier that ends at the goalline. Or end it a couple yards deep I guess if it is a code for all defenders to all for safeties.

In the second example, the FS had no shot at catching the ball carrier, but it would be a nice visual if he actually took an angle that ended at/around the goalline vs. outside of the field of play or the back of the endzone.
 
G.O.D Turner
offline
Link
 
These are NOT bugs...the angle taken based on the FS's top speed compared to how fast the WR is running, the angles taken in both circumstances are perfect. Your player simply didn't have the ability to catch them before the score, plain and simple.
 
SCACE
offline
Link
 
Originally posted by turnerhero
These are NOT bugs...the angle taken based on the FS's top speed compared to how fast the WR is running, the angles taken in both circumstances are perfect. Your player simply didn't have the ability to catch them before the score, plain and simple.


Agree re: speed, but the angle is far from perfect.
 
G.O.D Turner
offline
Link
 
If his FS had cut the angle tighter he wouldn't have even been near the WR when he caught up to him - in that case, teh angle would be a 'bad angle' but in these cases, they look perfect.
 
SCACE
offline
Link
 
Originally posted by turnerhero
If his FS had cut the angle tighter he wouldn't have even been near the WR when he caught up to him - in that case, teh angle would be a 'bad angle' but in these cases, they look perfect.


Agreed, but what's the point of taking the "best angle" to reach the player if that angle is 50 yards, 100 yards, etc. past the endzone?

The player should take an angle to where the ball carrier / endzone meet, or as stated, maybe 2-3 yards deep if the coding applies to all players to allow for safeties and whatnot. Sure, the FS would not have caught up, but it would "look" better to people whining about angles their players are taking. And, given the "diving tackle" ability, I've seen times where I wish the defender had taken a line to the point where the endzone/ball carrier meet as that may trigger the ability.

Finally, with all the vision / head fake / juke nonsense, the closer i get to the player, the more chance i trigger his moves so again, I don't want to take a meaningless angle out of the endzone
 
drifter
offline
Link
 
I agree that it's not a build issue. As SCACE pointed out, if the angle calculation results in the point of intersect being beyond the goalline, it should automatically adjust to the 1 yard line at the point where the ball carrier will cross it, even if it means he might not get there in time.
 
Checkmate187
offline
Link
 
Pathing AI is a bitch to program.
 
that1guy
offline
Link
 
Originally posted by turnerhero
These are NOT bugs...the angle taken based on the FS's top speed compared to how fast the WR is running, the angles taken in both circumstances are perfect. Your player simply didn't have the ability to catch them before the score, plain and simple.


for the first one, my thought is that since the SS seems to slow the WR down a tighter angle MAY have allowed the play to be made. And its not those two plays.

how many times have u seen defenders run into eachother trying to chase after another player? the best angle isn't the best angle if it makes me run into a team mate and prevents us from making the play.
 
SCACE
offline
Link
 
Originally posted by Checkmate187
Pathing AI is a bitch to program.


QFT

but not impossible. We have a vision ability, and high enough vision should allow you to take a better path (around teammates as well as defenders) and the point of intersection should be right around the goalline.
 
ahnonamis
offline
Link
 
On that first one it looks like the FS could have cut him off after the missed tackle due to the stumbling. Does the AI take that into effect? Offensive players being held up momentarily by defense? He doesn't seem to change direction even a tiny bit, which would mean either it calculated the missed tackle before it happened, or it had no impact on the FS's pathfinding.
 
Page:
 


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