User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Serious Bug Issue: Pathing for Defense at the Goalline
Page:
 
saintedix
offline
Link
 
Originally posted by Swiftus
I actually don't think that this is really a bug.

Think of it this way:

The LB's pathing is set to put him at an angle where he will catch and hopefully tackle the WR. It is like triginometry. If he is heading straight down at XX speed, at what point with LB starting 15 yards east of him running at YY speed catch him? The answer is the negative 30 yard line.

Okay, that's just an example.


Swiftus, you wanted "triginometry", well, here you go:

http://i473.photobucket.com/albums/rr98/saintedix/GLB/PathingExample.jpg

I went into the second example I gave to do some studying. I measured the distance the SS traveled (in pixels) from the tick when both players hit the 50 yard line to the tick just before the WR crosses the goalline. I then drew a line from the SS's initial position to his final position to get an approximation of his "range" of travel in the time it took the WR to get from the 50 to the goalline. I drew a black circle representing the area that can be traveled by the SS in this time. The yellow lines are of equal length, and the SS markers are centered on the end points of the lines. Long story short, with this visual representation, is there any doubt that Bort needs to add a cutoff point at the goalline? The SS CLEARLY has a tackle chance.

Note: The path on the left is the ACTUAL path traveled by the SS.
Last edited Oct 30, 2008 17:59:11
 
NiborRis
offline
Link
 
Looking at that image, this probably comes down to the fact that the pathing is based on points, but the tackling has a range. In your example, the dot for the SS doesn't *quite* cover up the WR, so the pathing picked a shallower intercept angle.
Usually this won't make much difference, but in long nearly parallel runs it could easily make 5+yards difference.
This is certainly fixable, and there's some computational hacks to make this not really any more expensive sim-wise, but changing a basic pathing algorithm is pretty expensive testing-wise to make sure it doesn't screw up anything else.
 
saintedix
offline
Link
 
Originally posted by Bort
I suppose it would be easy enough to make the cutoff point's Y axis always get set to the goalline if it's beyond it, but would it make a difference?


Bort said himself it wouldn't be very hard.

And yes Bort, I think it WOULD make a difference just looking at my diagram. Short distances probably wouldn't be affected much, but longer distances make a HUGE difference.
 
saintedix
offline
Link
 
bump
 
RMiller517
offline
Link
 
Thread locked by moderator.
 
Page:
 


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