NOTICE: This league is using the BLEEDING EDGE game engine. For more information, click here.

The new user interface is in preview!

Want to check it out? Click here! (If you don't like it, you can still switch back)

League Forums

Main - Beta Chat

Re: [Beta Update] M2M Juking Tweaking

By jdavidbakr - Site Admin
9/01/2018 11:27 am
I couldn't reproduce #10, I ran hundreds of that play combination and never had that happen. The specific issue is the DB playing off the LOS and approaching the WR (instead of letting him come to him), when the WR is past him he is going the wrong direction and doesn't recover his momentum enough to stay with the WR. Every time in the dev environment the DB properly stays with the WR unless he gets juked - but I know that the DB was not juked in the play you reference. So I'll keep looking.

I have pushed an update to address the DB spinning render error. I also reduced the speed of the passes - this is giving more vertical velocity to the pass, and should help the ball clear the linebackers better. Not sure if there will be secondary effects of this or not. Also, I've reduced the diving catch probability and conversely increased the catch probability a tad more. Running heavier tests over the next few days but I'm pushing this to MFN-1 for tomorrow's games as well.
Last edited at 9/01/2018 11:28 am

Re: [Beta Update] M2M Juking Tweaking

By Ragnulf-le-maudit
9/03/2018 2:59 am
The LB is in good place but doesn't react to the ball in the air.
https://mfn1.myfootballnow.com/watch/8605#1560517


The Lb who covers the FB is completely lost
https://mfn1.myfootballnow.com/watch/8605#1560529


The Db turns way before the WR comes to him
https://mfn1.myfootballnow.com/watch/8605#1560529


Overall the passes look slower and with a different trajectory. Is it because of the decrease in speed you implemented ?
Last edited at 9/03/2018 3:26 am

Re: [Beta Update] M2M Juking Tweaking

By Tecra031
9/03/2018 5:23 am
[quote=
Overall the passes look slower and with a different trajectory. Is it because of the decrease in speed you implemented ?
[/quote]

Passing game is broken now would be more appropriate. All passes are high floaters. QB passing/dumping to RBs on most plays, and also passing to them WAY out of bounds. Still, wide open receivers drop passes, while triple coverage almost guarantees a catch.

It seems EVERY "fix" breaks 2 other things.

Re: [Beta Update] M2M Juking Tweaking

By setherick
9/03/2018 8:05 am
1) https://mfn1.myfootballnow.com/watch/8604#1560295
a) Here's a good one. The top CB doesn't get beat off the line when I think he would have before. The bottom CB stays with the WR. The WR makes the catch, but he has position.

2) https://mfn1.myfootballnow.com/watch/8604#1560313
a) Here's another one where the CBs are in press coverage and both CBs engage at the LOS. Pretty sure neither would have engaged before. The bottom CB also peals off as soon as the ball is in the air. I'm not sure how he knows to do that.

3) https://mfn1.myfootballnow.com/watch/8604#1560317
a) Where is the deep safety going on this play?

4) https://mfn1.myfootballnow.com/watch/8604#1560318
a) DB engages downfield. WR gets the inside position on a stutter. Not sure what would happen if the WR was as fast as the DB tho.

5) https://mfn1.myfootballnow.com/watch/8604#1560337
a) This one is really bad. The safety ends up way out of position on this RB pass. Is this because his M2M is 66/98? Because the RB only has 67 route.

6) https://mfn1.myfootballnow.com/watch/8604#1560338
a) Interesting one-on-one battle here. It looks like DBs are still playing trail coverage and giving up the inside position too easily. But I'm not mad this is a TD.

7) https://mfn1.myfootballnow.com/watch/8604#1560344
a) This one is really bad. The DBs start mirroring the WR's movements instead of playing the WR or the ball. This shouldn't be an easy catch.

More later.
Last edited at 9/03/2018 8:05 am

Re: [Beta Update] M2M Juking Tweaking

By setherick
9/03/2018 9:18 am
Here's the rest.

General Observations

1) Passes are going over LBs and DBs now, but they are also more off in terms of distance and placement. QBs consistently throw behind WRs instead of letting WRs run under the ball. The goal of long passes is throwing the ball in front of the WR and letting the WR make the play.

2) The penalty for passes < 20 yards from the LOS needs to go ... seriously. It just needs to go.

3) Why don't QBs throw the ball away? They haven't since 0.4.3 started in development. That needs to be turned back on. And QBs need to run more often when they are out of the pocket and under pressure.

---

8) https://mfn1.myfootballnow.com/watch/8604#1560364
a) I'm point this out because I'm not sure what's wrong or how to fix it. The 113 Posts play exploits the defense. The DBs get too deep in the well and go out of bounds, and then they can't recover when the WR cuts back to the inside. This was more explicit when the WR would make a 45 degree cut across the field, but it's as much as an exploit now.

9) https://mfn1.myfootballnow.com/watch/8604#1560368
a) This is why QBs need to THROW THE **** BALL AWAY again or run when under pressure. The lofters downfield just look ridiculous.

10) https://mfn1.myfootballnow.com/watch/8604#1560384
a) Posts exploit again.

11) https://mfn1.myfootballnow.com/watch/8604#1560389
a) 91 M2M LB gets way out of position. Like #5 above.

12) https://mfn1.myfootballnow.com/watch/8604#1560390
a) This is the same as #11, but harder to see because other defenders are in the way.

13) https://mfn1.myfootballnow.com/watch/8604#1560391
a) Bottom of the screen. Foster has 98 B&R and 78 M2M. The WR has 64 B&R Avoid and 79 Route. That play is just ridiculous.

14) https://mfn1.myfootballnow.com/watch/8604#1560392
a) Weeks has awful M2M, but he takes the exact path he needs to take to defend this pass against the 67 route RB. I would expect Weeks to overrun the play. Why are the high M2M players overrunning?

15) https://mfn1.myfootballnow.com/watch/8604#1560394
a) The entire OL quits blocking. I thought this bug was fixed months ago.

16) https://mfn1.myfootballnow.com/watch/8604#1560400
a) Another one where the QB should have thrown it away.

17) https://mfn1.myfootballnow.com/watch/8604#1560404
a) QB throws it pretty far behind the play.

18) https://mfn1.myfootballnow.com/watch/8604#1560407
a) What happens here? 20 yards past the LOS really shouldn't be that hard to throw.

19) https://mfn1.myfootballnow.com/watch/8604#1560413
a) This pass is just bad.

20) https://mfn1.myfootballnow.com/watch/8604#1560432
a) This pass is also bad.

21) https://mfn1.myfootballnow.com/watch/8604#1560440
a) He's not even under pressure when he throws this.

23) https://mfn1.myfootballnow.com/watch/8604#1560441
a) Top DB is covering the drag route. He starts too deep and does not take the right angle to close the gap. Then he gets confused by the WR that cuts across his face. Lots of things here. Not the worst play, but shows some problems.

24) https://mfn1.myfootballnow.com/watch/8604#1560466
a) Who is the QB throwing to?

25) https://mfn1.myfootballnow.com/watch/8604#1560467
a) This one too.

Re: [Beta Update] M2M Juking Tweaking

By jdavidbakr - Site Admin
9/04/2018 8:39 am
Tecra031 wrote:
[quote=
Overall the passes look slower and with a different trajectory. Is it because of the decrease in speed you implemented ?


Passing game is broken now would be more appropriate. All passes are high floaters. QB passing/dumping to RBs on most plays, and also passing to them WAY out of bounds. Still, wide open receivers drop passes, while triple coverage almost guarantees a catch.

It seems EVERY "fix" breaks 2 other things.[/quote]

Do you feel like this is just because you're used to the passes being faster? I've had a really difficult time finding any data on the actual velocity of an average NFL pass. All I've found is the answer to what is the fastest that a QB can throw the ball, but I'm not even really sure how many times during a game the ball would go at 60MPH (which is what that number is). I did finally find a study that had what I was looking for and the numbers right now are in that range. But it may be that I need to put the max higher, and maybe even bring the min up a bit.

I have looked over and over at the code that determines the catchability of a ball and cannot see where an open WR has a higher probability of the catch than a WR in triple coverage. But I'll keep looking again, because surely there's something to the high level of anecdotal evidence.

Re: [Beta Update] M2M Juking Tweaking

By Beercloud
9/04/2018 9:44 am
QB velocity
They give a left and right velocity during the last combine only.
http://blogs.ourlads.com/2017/03/16/quarterback-ball-velocity-at-nfl-combine-2008-2015/


QB Charts
https://nextgenstats.nfl.com/charts/list/qb-grid

Re: [Beta Update] M2M Juking Tweaking

By raymattison21
9/04/2018 12:55 pm
The velocity is allowing for more recovery time during coverage . You see the safeties and LBs really over run coverage plays now . Before the ball was traveling too fast and or low .

Brady was clocked in game well over 60 mph and right now pressure is effecting general accuracy .
Last edited at 9/04/2018 12:56 pm

Re: [Beta Update] M2M Juking Tweaking

By setherick
9/04/2018 1:25 pm
raymattison21 wrote:
The velocity is allowing for more recovery time during coverage . You see the safeties and LBs really over run coverage plays now . Before the ball was traveling too fast and or low .

Brady was clocked in game well over 60 mph and right now pressure is effecting general accuracy .


The problem with closing speed on plays is a problem with the game physics of SP. Players are either too fast or too slow - most often too slow - based on their SP rating. More later.

Also, I didn't really notice this being much of a problem in my game as I did other things, so if y'all want to point me to some games to review, I will.

Re: [Beta Update] M2M Juking Tweaking

By raymattison21
9/04/2018 5:45 pm
Prior to the pass angle/velocity change I watched my high speed DE get a pressure and quickly turn and run as fast as the ball only to end up with a pass defended 12 yards away. He was faster that the pass !

That wobbly ball code made the pass trajectory / speed so bad IRL the ball would be at least double the height to cover that ground at that speed..

To me all that says the pass height needs to be upped. Max ball speed should be a little more than 3 times the speed of the fastest players.

Increasing the angle of the pass should technically slow the ball from point A to point B as it is now traveling a farther distance . Is that how it works here?

If so when bad passes occur smart strong armed guys should over throw long ***** ( away from the defender) and put short ones in the dirt ( away from the defender)