Warrior General Games

let's not argue over one example

Look at this one tick by tick
http://goallineblitz.com/game/replay.pl?game_id=1636979&pbp_id=6326987
AFTER the wr has the ball, 3 ticks after while the wr is going OUTSIDE of the TE/CB the SS takes 4 steps inside.

Originally posted by bug03
let's not argue over one example

Look at this one tick by tick
http://goallineblitz.com/game/replay.pl?game_id=1636979&pbp_id=6326987
AFTER the wr has the ball, 3 ticks after while the wr is going OUTSIDE of the TE/CB the SS takes 4 steps inside.

You are correct on that play. He DOES head inside for no reason

And it's not arguing it's a discussion..........lol

Originally posted by Rikkhen
You are correct on that play. He DOES head inside for no reason

And it's not arguing it's a discussion..........lol

Semantics

The point is, bug or not, it shouldn't work that way, and if it is something that is coded in to the specific play itself, it should be fixed - if it's open field pathing, why is it only on this play and not on pitches or sweeps?

Originally posted by bug03
SemanticsXD

The point is, bug or not, it shouldn't work that way, and if it is something that is coded in to the specific play itself, it should be fixed - if it's open field pathing, why is it only on this play and not on pitches or sweeps?

That i can't tell you. The 2nd and 3rd replay look to me like the one you and i were DISCUSSING.........lol They move after the ball is caught but others he moves before. I am gonna mark this as needs more info and see if we can't got some more bug mods perspective on this issue.

Let's look at the possible culprits -
1. Vision - 5 different dots, I don't think so
2. Fake - no shrinkage
3. out of position - They started in a better position than they ended up
4. faulty defensive coordinator - Cover 2 on the back side of a formation when wr2 and te KILL it on wr clear out - I don't think so
5. ?????


Sorry if I'm railroading this, but I really don't want to have to set up the SS to cover wr2 in order to avoid this (much like the OC's didn't want to HAVE to keep the TE in to block to stop blitzes so there was change)

It has been filed in Bugzilla as needs more info so let it go through the process.

Look to me like the SS is tracking the HB.

For what that's worth

Fish

Edit -- we all know that we'll need to see more than just this one replay. I could claim vision check failure on the SS

That's really not a very ideal set up to contain/stop runs/screens to the strong side. Now the weak side has plenty of coverage in those examples.

Originally posted by Mightyhalo
That's really not a very ideal set up to contain/stop runs/screens to the strong side. Now the weak side has plenty of coverage in those examples.

Never said it was ideal for anything other than weak I wr clear out - which is pretty much impossible to cover

I think what we need to do here, is compile all of the examples that show the SS moving inside mysteriously, looked like we had maybe 3-4, and try to form a basis off that.

Let's keep it to the Weak I play in question, if we can get a good amount of links on this, we'll be able to build a good file on it and that's usually the best way to go about play specific bugs.

#1 - http://goallineblitz.com/game/replay.pl?game_id=1636927&pbp_id=7504802
#2 - http://goallineblitz.com/game/replay.pl?game_id=1636979&pbp_id=6326987
#3 - http://goallineblitz.com/game/replay.pl?game_id=1636979&pbp_id=6327364

http://goallineblitz.com/game/replay.pl?game_id=1636879&pbp_id=9850113
As the ball is in the air, the ss moves wide, as soon as the wr catches the ball, the ss moves inside

I thought it was just our SS that was broken....will come up with some playe here...

Originally posted by bug03
http://goallineblitz.com/game/replay.pl?game_id=1636879&pbp_id=9850113
As the ball is in the air, the ss moves wide, as soon as the wr catches the ball, the ss moves inside



Because the path of the WR is to the inside. The SS is moving to a point convergence point based on the WRs current path.


I don't like it one bit, but the way the SIM is currently coded, it is working as intended.

Originally posted by Rage Kinard
Because the path of the WR is to the inside. The SS is moving to a point convergence point based on the WRs current path.


I don't like it one bit, but the way the SIM is currently coded, it is working as intended.

I don't agree with this statement due to the fact that the SS was not covering the WR on this play. The SS moves inside for little to no reason allowing the WR a cutback to the outside which led to a big play. The SS is supposed to play his zone but after he moved back into his zone at the start of the play, he then moved inside..

The inside movement is what I don't understand.

Originally posted by Pwned IRL
Originally posted by Rage Kinard

Because the path of the WR is to the inside. The SS is moving to a point convergence point based on the WRs current path.


I don't like it one bit, but the way the SIM is currently coded, it is working as intended.

I don't agree with this statement due to the fact that the SS was not covering the WR on this play. The SS moves inside for little to no reason allowing the WR a cutback to the outside which led to a big play. The SS is supposed to play his zone but after he moved back into his zone at the start of the play, he then moved inside..

The inside movement is what I don't understand.

I took it like Rage...the WR's first move is to the inside, so that's where the SS is heading...to cut off the ball carrier. He doesn't move until the WR catches the ball and runs inside. THEN the WR cuts outside and the SS simply doesn't have the vision/agility to make the same cut.