Where people don't stack all their coaching points into recruiting and kill. I am still getting to know all this stuff also
Well The CPU pass rush was way too overpowered. Got sacked 3 times first drive and its not like they were bringing the house. They stayed in nickle with 1 safety on the top for most the game. Passing was smoother than I thought and I think we got it right on QBA. For those of you who play a team that likes to run read option, you better lab a way to beat it. I couldnt get off blocks and got gouged for 20 yard runs at a time. I got fed up and got into dime to blitz both inside CB's. I also thought the speed difference was too low. I was running around with Johnny on the first drive and some 270 pound lineman was catching up to him easily.
I felt like that already with the sliders sometimes, so I guess I'm glad I'm playing a user. Are we planning on waiting a few weeks before adjusting or will we address issues early (like super CPU rush if everyone is seeing it)?
I thought someone was using UNC for some reason. I can't wait...effing Renner runs for 200 yards off of RO and completes every pass for the upset!
It shows him as UNC in the game. Knight has just been lazy to not update the Google Doc. Also, Toledo only had 2 sacks in my game. You have to take into consideration different situations (A&M did just lose 2 NFL Linemen right?)
These sliders need fixed before week 2. FAU's running back is averaging 9 yards per carry in the first half and their QB is 9/10 and killing me. Did I mention I'm playing FAU? The second half went better. I still didn't feel like I ran the ball well enough under center, though.
I'll try to address some of the concerns before I advance into week 2 lol yea, google doc means crap now since he said he wanted UNC
Sliders were way tough. I got no defensive pressure at all, no ints and no sacks, were their defense was all over me with just rushing 4. The o- line should be able to block a little longer, not let the qb get hit every play, and the rushing defense needs lots of help. The cheese dick cpu called screen plays on every 3rd down thru 3 quarters.
I often call man against cpu on third down because of this. That or do cover six and send a DE to the flats in the play side and user the LB.
The only problems I came across were CPU rushing (tackling lacked), CPU Accuracy. I got somewhat of a pass rush and their rush bothered me a couple times but I felt that was normal, you have to get the ball out on time and make very good reads. With that said, I will bump up the pass d and look into the user rush along with bumping the cpu QBA up some and our pass defense up. When they completed passes on me the defender was no where to be seen and was buggy coverage.
For Documented record: QB 10/5 PB 35/40 Catch 40/40 RB 50/50 RB 35/40 Cov 65/75 INT 35/45 RD 55/100 Tackle 55/50 FG 40/45 FG A 25/50 PP 35/35 PA 60/60 KP 30/30
And honestly, 35 wasn't that "bad"... you gotta make your reads/progression right on time. I was sacked twice, hit another for an incomplete pass and still went 15-19
Even though I didn't want to overreact and change without a sample size, let us see how these do for week 2 Documented Changes: QB 10/10 PB 40/40 Catch 40/40 RB 50/50 RB 35/40 Cov 70/75 INT 35/45 RD 60/100 Tackle 55/50 FG 40/45 FG A 25/50 PP 35/35 PA 60/60 KP 35/35
