After studying these I think this is a diving tackle attempt. I may look at this and see about at least tweaking the timing so they don't execute it as soon as the ball is caught.

Bye everyone. See you when 0.4.5 is ready: https://mfn1.myfootballnow.com/box/7938

I have no energy to look through this film and figure out why my 100 Accuracy QB threw 13 Interceptions!

Or why Ray's pass long only offense completed more than 50% for more than 1000 yards! And scored more than 100 points against my secondary that doesn't start a single DB that has less than 80 M2M (and my starting corners and nickleback are 90-100 and my LBs in coverage are 100 and 78).

I also have no energy to try and figure out why all of the changes that were improving 0.4.3 suddenly went away.

Yikes, well that puts another stay on releasing 0.4.3. Nothing significant has changed, I don't think, but I will look closely at this game.

Can we please split up the 0.4.3 release? Release the draft updates, the QB fatigue, the holding adjustments, and the play matrix bug fixes? Every time another league rolls over without those, it's a bummer. The passing fixes can then go into a 0.4.4 release.

Your qb caught the wobbly pass bug from a pass key blitz one cover one defense . And your defenders caught the stop covering bug on those deep flags . Not to mention my LB with 64 man coverage was looking like a 15 man cover defender about dozen times. It's been this bad the whole release .

This is categorically untrue. The Sunday commit (the one Sunday night, not the one that crashed) was stable and much improved. I have no idea what happened the past two days.

Update: I guess I should give an explanation why I'm just done with the beta leagues. The fix that I'm sure caused most of the problems with my game (having looked at a few plays) should have never been made in the first place.

There were times when the DB appeared to stop in coverage because he dive tackled immediately and the WR was faster than he was. THIS IS EXACTLY WHAT HE SHOULD DO IN THAT SITUATION.

While I had noticed a few of those plays, I noticed more of them when the slower DB pushed the WR all the way down the field, the WR got behind the DB, WR caught the ball, and the DB tackled him immediately even though the DB was 10-15 points slower than the WR. I assume he was catching the WR in those situations BECAUSE of dive tackling not IN SPITE of dive tackling.

I'm not going to beta test if we aren't going to rigorously examine and explain points. I hadn't been paying close enough attention to the boards when this change was decided to dissent then, and I'm shocked that it was made so quickly without a thorough examination of the game film.

52 points in one quarter? That is absurd.

I almost feel like we're trying to change too much in one release if this is happening. Too many sudden changes can break certain codes (I would think at least) and the offense obviously has a distinct advantage in this version that's being tested, mainly in the Medium/Long passing game.

Good thing I'm not in this league anymore because I would have freaked the F@#$ out over that game

The crazy thing is, not that much has changed in the core ... it's just, as it always is, one change breaks something else, and you go back and forth until you get it solved.

I have identified that the long passing game is overpowered again, but I have not yet been able to reign that in. All of this is stemming from one change to the QB logic, that one change required other changes to balance the defensive side of the ball.

The biggest issue here is that for as much physics there are in the game, Speed is not based on any game-measurable physics. That's why a 60 SP player looks like he's doing nothing when up against a 100 SP player when, really, we should be talking about the difference in 0.1s of a second.

I've only watch a few clips, but here are the two things that I'm sure are causing almost all of the remaining problems with 0.4.3. The only two things:

1) The code "fix" to prevent immediate dive tackling now causes CBs to stand around after a WR catches a pass. That means if there is any separation, it's a long gain.

2) Stutter stepping still "ends" the route. This is why this is important. Defenders DO NOT KNOW how to defend a WR that is free running. THEY NEVER HAVE KNOWN. That's why plays that changed direction when a player touched the LOS or side line and started free running were always so effective. Stutter stepping is just compounding the issue.

And, now, I am completely done.