Statistics and Sliders NCAA12

[lbowbb2]

As a follow-up to my earlier enquiry about ECU, I checked their stats from last season and found out the number was just flip-flopped. The table has 36, but they actually ran 36% of the time and passed 64% of the time. Of their season total of 990 plays, 632 of them were passes. Just letting you know if you want to update the front page.

[aerovt]

ArkSt-me		VT
24	Score	38
24	1st Downs	9
361	Total O	191
49-184-2	Rushing	28-141-2
18-26-1	C-A-TDs	6-10-1
177	P Yards	107
3-1(27%)	3rd Downs	2-7(28%)
1-1 (100%)	4th Downs	0-0 (0%)
0-0 (0%)	2pt	0-0 (0%)
4-3-1(100%)	Red Zone	2-1-1(100%)
2	TO	0
1	Fum Lost	0
1	INT	0
22	PR Yds	1
145	KR yards	110
528	Total Yrd	359
4-31.5	Punts-Avg	4-40.3
2-20	Penalties	0-0
28:01	T.O.P	11:03
6	Sacks	4

I was using a one-back offense and the 4-2-5 defense.

For the CPU (VT) this was really a tale of 2 halves. The first half, they had 54 yds of total offense. Part of this was my ToP and turnovers (gave them 2 defensive TDs), but they just couldnt move the ball. I did notice they kept trying to do sweeps/pitches with D. Wilson and since I was running a 4-2-5 I was usually blitzing the edges and easily stopped this. They were 1-6 on 3rd downs the first half. It had me very worried about the game being that Wilson had 8att, 20 yds, 2.5 avg in the first half.

The second half, it was almost like the CPU made halftime adjustments, because they came back out unstoppable on offense (as I was expecting for the whole game) and started doing more power running. I believe they scored every possession they had in the second half. The only reason their 2nd half stats dont blow anyone way is they did not have the ball much on offense (see below for ArkSt rushing) VT running backs were:

Wilson: 19att-116yd-6.1 avg (note, thats 8.7 yds/att for the second half)
Gregory: 1att-55yd-55 avg

So for the AI offense, I started off worried, but they turned it around. Might need a tweak, but not necessarily. What did concern me was the CPU run defense and the number of sacks I was able to get.

My running back:

Lawson: 32att-188yd-5.8 avg
Robertson: 6att-29yd-4.8 avg

Arkansas State isnt that good, and shouldnt be putting up those kinds of rushing yards. That said, however, I did notice running out of the Ace-Spread formation (and most Ace-4wide sets) gave the CPU problems, which might mean sliders cant fix it. These numbers are estimates, but I found that for the user, when running out of:

I-Form/AceBig sets - 2.5-3.3 yd/att
Ace4Wide sets - 6.0-6.4 yd/att

[fldash]

VT only had 141 total offensive yards... ...

[aerovt]

141, was typo. Still, 191 (what they got) wasnt great either

but as I said, I was real worried for the first half when they did nothing offensively (54 yds total). Second half was low because they only got the ball 3 times as they couldnt stop my run out of the Ace-4wide sets

[Oraeon1224]

Quote: Originally Posted by aerovt

ArkSt-me VT 24 Score 38 24 1st Downs 9 361 Total O 191 49-184-2 Rushing 28-141-2 18-26-1 C-A-TDs 6-10-1 177 P Yards 107 3-1(27%) 3rd Downs 2-7(28%) 1-1 (100%) 4th Downs 0-0 (0%) 0-0 (0%) 2pt 0-0 (0%) 4-3-1(100%) Red Zone 2-1-1(100%) 2 TO 0 1 Fum Lost 0 1 INT 0 22 PR Yds 1 145 KR yards 110 528 Total Yrd 359 4-31.5 Punts-Avg 4-40.3 2-20 Penalties 0-0 28:01 T.O.P 11:03 6 Sacks 4 I was using a one-back offense and the 4-2-5 defense. For the CPU (VT) this was really a tale of 2 halves. The first half, they had 54 yds of total offense. Part of this was my ToP and turnovers (gave them 2 defensive TDs), but they just couldnt move the ball. I did notice they kept trying to do sweeps/pitches with D. Wilson and since I was running a 4-2-5 I was usually blitzing the edges and easily stopped this. They were 1-6 on 3rd downs the first half. It had me very worried about the game being that Wilson had 8att, 20 yds, 2.5 avg in the first half. The second half, it was almost like the CPU made halftime adjustments, because they came back out unstoppable on offense (as I was expecting for the whole game) and started doing more power running. I believe they scored every possession they had in the second half. The only reason their 2nd half stats dont blow anyone way is they did not have the ball much on offense (see below for ArkSt rushing) VT running backs were: Wilson: 19att-116yd-6.1 avg (note, thats 8.7 yds/att for the second half) Gregory: 1att-55yd-55 avg So for the AI offense, I started off worried, but they turned it around. Might need a tweak, but not necessarily. What did concern me was the CPU run defense and the number of sacks I was able to get. My running back: Lawson: 32att-188yd-5.8 avg Robertson: 6att-29yd-4.8 avg Arkansas State isnt that good, and shouldnt be putting up those kinds of rushing yards. That said, however, I did notice running out of the Ace-Spread formation (and most Ace-4wide sets) gave the CPU problems, which might mean sliders cant fix it. These numbers are estimates, but I found that for the user, when running out of: I-Form/AceBig sets - 2.5-3.3 yd/att Ace4Wide sets - 6.0-6.4 yd/att

This is a really wierd game. VT had 5YPC and you had 3.9 so your running wasn't actually that dominant in a YPC sense but I suspect they weren't able to prevent you from picking up the first down so you had long drives and ate up the clock. This was compounded by your turnovers resulting in touchdowns which removed 2 possessions and probably 14-16 plays from their side which would have added potentially another 50-70 yards of total offense.

Also you only had 113 total plays in your game unless I miscounted. The NCAA average is 130 even for running heavy games. You probably carefully select your playcalling and use more clock than I do. You might try increasing your quarter length by one minute and that should improve the overall yardage in your games.

Recommendations:
1. Increase quarter length by 1 minute to get more plays

2. As to your seeming ability to pick up first despite a low YPC I would recommend increasing the rushing defensive awareness slider or reduce your RB ability back down to 50. To allow big plays to keep up YPC but reduce time of possession you could increase run block as needed.

3. Too many human sacks is a general problem I have noted as well if you control the D-line. I mostly use LB and so don't experience this. Either move to controlling a LB or up CPU pass blocking until you have the correct number of sacks.

[Oraeon1224]

You guys are killing me. I went ahead and recompiled my own list of stats this year again and have posted the update on the first page. The coaching sliders will be updated as well. Please post suggested changes based on coaching changes as I don't have the time to research each team.

[Oraeon1224]

Will add statistics here as can't add to front page. Coaching is updated.

[Oraeon1224]

Finished testing FG in practice mode. On default CPU can hit a 50 yarder everytime. With FG accuracy and power to 40 this drops to around 20% with no wind and straight on. At chipshot with a very average kicker the CPU will still occassionally miss and all shots look stressful like real-life. Give it a try. Punting will require in game testing as will kick return. From my preliminary games punting is too strong and I am going to reduce to 40.