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: Version 0.4.1 RC 5

By setherick
4/10/2017 6:19 am
Gave up 11 sacks in my game including 6 to underweight DEs. How did 0.4.1 go from great to **** in the past four games?

Re: Version 0.4.1 RC 5

By raymattison21
4/10/2017 6:55 am
setherick wrote:
Gave up 11 sacks in my game including 6 to underweight DEs. How did 0.4.1 go from great to **** in the past four games?



Only about 7 percent above the average . On the other hand my small team cannot stop the run. We play a pass defense . Have been for 3 seasons . Virtually the same defense /defenders .

Hayes has poor mobility also. Like Culpepper , my end are severely explosive. 3 or 4 were run down sacks. Davis is a LB and my slow DT got one.

My complaints are rooted in how both our QBS missed plenty of wide open short passes vs. A deeper zone. FOV is near max for my guy who gets zero hot reads agame.

So, IDK you sacked me on eight percent of pass plays, but my guy has the mobility of Aaron Rogers . ....great carry, good acceleration and decent speed. Still, it seemed my guys were on fire he last few games, but they were league leaders before then, but my DT was a beast.

I prefer the pressure to be this way with small DEs leading the league in sacks. Not Blitzers from the middle/ DTs.

My QB has missed all the short reads on the run, but has turned it up field very nicely . (Intelligence ? IDK) 3 or 4 times of my guy getting ran down in those same situations would have put our sack numbers at equal levels, but like I said he turned it up feild .

I would note your ignorance towards the acceleration rating, and ex LB Beazs lack of man/or zone cover rating. His speed /punish gave him a clear advantage over my elite wr Park.

This code was the first to force me to play different . ....slightly different it may be. These are cover sacks IMO which cause this, but I upped blitzes half way through the season.

Still, worthy of a look, but nobody else has said anything about pressure . You got remember I do not scout either or sub players.....so that even more broke imo.

Re: Version 0.4.1 RC 5

By setherick
4/10/2017 7:30 am
Hayes was sacked 40 times in the regular season, but 21 of those came in the last four games (WarEagle's blitz every down defense, your lightweight DE defense, and two others that I didn't bother to look into). And then 11 times in our playoff game. Hayes threw the ball more than 50 times in one of those games, so it can't all be blamed on the number of dropbacks.

Something that JDB pushed in around game 12 messed up edge blocking again. If 0.4.1 is going to be as bad at sealing the edge as 0.4.0. Your DE numbers are also as bad as 0.4.0 -- 279# DT with 29 sacks, 256# LB playing DE with 23 sacks, 237# LB playing DE with 22 sacks. There is no difference between what you're doing and what everyone in 0.4.0 is doing.

Forget it. I don't see a point in any of this anymore. Blocking on this game isn't going to improve until SP is taken out of the blitz algorithms and strength/weight is calculated correctly and actually matters in pass block.

Re: Version 0.4.1 RC 5

By jdavidbakr - Site Admin
4/10/2017 8:28 am
setherick wrote:
Something that JDB pushed in around game 12 messed up edge blocking again. If 0.4.1 is going to be as bad at sealing the edge as 0.4.0. Your DE numbers are also as bad as 0.4.0 -- 279# DT with 29 sacks, 256# LB playing DE with 23 sacks, 237# LB playing DE with 22 sacks. There is no difference between what you're doing and what everyone in 0.4.0 is doing.


Still trying to find the balance, pendulum keeps swinging. I'll tone it back down a tad for the playoffs.

Re: Version 0.4.1 RC 5

By jdavidbakr - Site Admin
4/10/2017 8:38 am
raymattison21 wrote:
My complaints are rooted in how both our QBS missed plenty of wide open short passes vs. A deeper zone. FOV is near max for my guy who gets zero hot reads agame.


The FOV doesn't impact hot reads - that's based on intelligence and play familiarity. I'll look at increasing the odds that he'll throw to a shorter route, there is some logic to prevent him from dumping it off short all the time.

Re: Version 0.4.1 RC 5

By raymattison21
4/10/2017 8:26 pm
jdavidbakr wrote:
raymattison21 wrote:
My complaints are rooted in how both our QBS missed plenty of wide open short passes vs. A deeper zone. FOV is near max for my guy who gets zero hot reads agame.


The FOV doesn't impact hot reads - that's based on intelligence and play familiarity. I'll look at increasing the odds that he'll throw to a shorter route, there is some logic to prevent him from dumping it off short all the time.


Yes , my references where noting that not a one hot read was ever called by my QB ever. 56 is low and maybe I am blind, but it has been a several games now. No (hot read) for QB Shelton .

Re: Version 0.4.1 RC 5

By raymattison21
4/10/2017 8:44 pm
setherick wrote:
Hayes was sacked 40 times in the regular season, but 21 of those came in the last four games (WarEagle's blitz every down defense, your lightweight DE defense, and two others that I didn't bother to look into). And then 11 times in our playoff game. Hayes threw the ball more than 50 times in one of those games, so it can't all be blamed on the number of dropbacks.

Something that JDB pushed in around game 12 messed up edge blocking again. If 0.4.1 is going to be as bad at sealing the edge as 0.4.0. Your DE numbers are also as bad as 0.4.0 -- 279# DT with 29 sacks, 256# LB playing DE with 23 sacks, 237# LB playing DE with 22 sacks. There is no difference between what you're doing and what everyone in 0.4.0 is doing.

Forget it. I don't see a point in any of this anymore. Blocking on this game isn't going to improve until SP is taken out of the blitz algorithms and strength/weight is calculated correctly and actually matters in pass block.


I don't think anyone has beat on blocking. My line is not very good. We did well running the ball with a ravaged line. My Gs are decent, but a small FB, TE and and undrafted C who boomed.

I did a team in 76 with RBs and FBs as Gs and Ts and TE s at C. Same for D, they had DBs and LBS on the line. Ever since Ares had LBer Terry Lamb lite up my interior in 75 I have done the same.

Running is different under this code, but sub 50 speed DTS should rarely get sacks under any code.

I liked pressure prior to game twelve . My guys were getting enough pressure but DTS were over powered and so was blitzers .

Look at the weird numbers punisher put up blitzin his CB 3. Penalty for over use or not that's alot of tackles . Blitzers B line backs......if anything only top LBs and Ss should heat seek backs like that.

And it more that just speed for me....it's about using mobility to get into position to make a play.

Re: Version 0.4.1 RC 5

By jdavidbakr - Site Admin
4/10/2017 8:49 pm
raymattison21 wrote:
Yes , my references where noting that not a one hot read was ever called by my QB ever. 56 is low and maybe I am blind, but it has been a several games now. No (hot read) for QB Shelton .


If you don't scout the play your odds of calling a hot read are pretty low unless your opponent overuses that blitz. But if your QB intel is 56 that's not going to help matters either.

Re: Version 0.4.1 RC 5

By setherick
4/10/2017 8:54 pm
jdavidbakr wrote:
raymattison21 wrote:
Yes , my references where noting that not a one hot read was ever called by my QB ever. 56 is low and maybe I am blind, but it has been a several games now. No (hot read) for QB Shelton .


If you don't scout the play your odds of calling a hot read are pretty low unless your opponent overuses that blitz. But if your QB intel is 56 that's not going to help matters either.


I guess it's time to up INT in my QB weights again...

Re: Version 0.4.1 RC 5

By setherick
4/12/2017 10:05 pm
Dump off logic bug in WarEagle-Krazy game. 81 is blocking on this play: https://mfn1.myfootballnow.com/gamecenter/view/6323#1142801