Just looking for an explanation as to why this MIGHT not be?
https://cust33.myfootballnow.com/gamecenter/view/2453#475321

Thanks-

i think what happened is the RB got the 1st down then he ran back to the spot before the 1st down so then your team was forced to kick a field goal on 4th down.

If that explanation is not what happened then really is a serious bug that needs fixing.

lol...yeah
anywho, It looked like the guy that tackled him knocked him back after the 1st down was made, then got tackled. Forward progress should be in effect.

The Zebra's strike again!

Iv'e had that happen to me recently, can't remember what game it took place in though.

I think its a bug in the code that falsely accuses the RB of deciding to run backwards, thus losing his forward progress.

I did this to an opponent in 76. My opponents WR clearly has the first down, gets pushed back, but not tackled. The player then tries to run and gets tackled short of the marker: https://cust76.myfootballnow.com/gamecenter/view/223#42840

Long story, short, I don't think there is such a thing as forward progress currently in the game.

Its on the list !

There is, but I think the runner re-establishes himself more quickly here than he would in a real game.

By jdavidbakr - Site Admin
1/25/2015 1:18 pm
I think the glitch is that the defense fails to make the tackle but immediately starts a new tackle that the forward progress is reset by. I do have that in the bug list. But forward progress is being calculated correctly, it's a bug with allowing th defense to start a new tackle too soon after it has been broken


I felt the the new tackle is what was played with.....but "reestablish more quickly " is that? Or is it something new?

I just always thought he was charged the same in any direction , but IRL when going backward the whistle comes sooner? Allowing for a better spot.

To me the stamina hit taken by the ball carrier would allow for little movement after contact.....

Though I do remember a back getting stuffed in the back field only to break a tackle to then scamper 30 yards for the TD(Barry Sanders like). But that happens way less than getting scalped a yard here and there due to spots.

I see my line on top of the first down too often. "Bring out the chains!"

Still, I rarely am bothered by this in my games....more bothered by the size of the ball is not counted.....

My general point is that is is getting looked at.....but who knows where it's at right now, but not bad enough to warrant a more in depth change, because it seems as forward progress is not counted. Or at least the way I see it should be counted.


But based on two years ago the same system seem in place but less time between tackles has been added? Or I am way off....?

Sometimes in the real game you'll see WR's making a 1st down then come back only to lose it..This doesn't happen with RB's in my opinion (or it's extremely rare) and the ball is always spotted where forward progress is stopped.

Not necessarily, it a player opts to 'come back' and is tackled short, the ball will be spotted where he is tackled. The only time 'forward progress' comes into play is when the defense pushes a player back when tackling him.