FistofRage's Heisman sliders...

[Keyser Soze]

Quote: Originally Posted by bamaboy082

I love the sliders guys..I was Alabama went to Tennessee in my 1st year and lost 24-17. Outgained them by about 150 yards but I threw 3 picks 2 in the redzone and that cost me. Loved the way it played my QB went 31-47 so I really liked the percentage and the fact that it was actually tough to move the ball on UT's defense. Only thing was I moved the CPU Awr slider to 85 just to beef up their defense a little bit. Great job guys these are definitely the best set out!

i am guessing bama has a pretty fast RB although I don't know this for sure. Biggest problem I have with going above 75 CPU AWR is the running game starts to completely disappear since we limit our speed. If you have speed then I agree, raise this all the way up. However, doing so will completely destroy any effectiveness of the slower/power back.

[therizing02]

I like the difficulty sliders for the most part but, is anyone getting anything that resembles pressure on the QB, in my 6 games with these as OSU, I was unable to get any pressure against teams like Northwestern and Purdue. When my defensive line is getting chop blocked ALL GAME LONG by those two teams something is wrong. If you're getting pressure tell me what you're doing. Keep in mind that I do mix coverages (zones are completely ineffective), blitz packages, etc. In other words I'm not trying the same stuff over and over.

Regarding the user running game, it was for the most part non existent, and that's with Chris Wells. I know I know don't use the sprint until....regardless, but I think he ran for something like 51 yards on 24 carries against Northwestern.

Robo QB. This is the worst part of it, I think the USER defensive awareness needs to be higher. Northwestern's backup QB was shredding the Buckeye defense as was Curtis Painter. Something like 20-24. With Awareness that low zone defenses are completely useless because there is no reaction from the DBs and the CPU just dinks the ball over the middle all game long.

I LOVE the challenge that these sliders present and I can see that people are getting good stats so I'm certain I need to work on my game a bit but, the issues above may be unavoidable without a few tweaks.

[fistofrage]

I played some dynasty games with these....

WKU 31 @ CMU 59 (me)
Colo St. 29 vs. Colorado (Me) 32 OT But it felt when I really needed to, I bore down and willed the victory coming from 29-14 down with 3:30 left.
Then I played the MSU @ Cal game 4 times.

MSU (Me) 7 @ Cal 31, turned it off in 3rd Quarter.
MSU 38 @ Cal 0, In the 2nd quarter and it was going to get worse. The Cal QB who is an impact player was 0-8 in the 1st Quarter with 4 picks.
MSU 28 @ Cal 31, full game, exciting.
MSU 25 @ Cal 14, MSU trailed 14-3 going into the 4th quarter. Had a pick 6 on final play of the game when score was 18-14.



I think AI Def awareness should go up to 80 and possibly CPU run block at 100 and possibly AI RBA to 55. My fear is that when I get a really fast Defense, it will be too easy against the AI.

[Keyser Soze]

Quote: Originally Posted by therizing02

I like the difficulty sliders for the most part but, is anyone getting anything that resembles pressure on the QB, in my 6 games with these as OSU, I was unable to get any pressure against teams like Northwestern and Purdue. When my defensive line is getting chop blocked ALL GAME LONG by those two teams something is wrong. If you're getting pressure tell me what you're doing. Keep in mind that I do mix coverages (zones are completely ineffective), blitz packages, etc. In other words I'm not trying the same stuff over and over. Regarding the user running game, it was for the most part non existent, and that's with Chris Wells. I know I know don't use the sprint until....regardless, but I think he ran for something like 51 yards on 24 carries against Northwestern. Robo QB. This is the worst part of it, I think the USER defensive awareness needs to be higher. Northwestern's backup QB was shredding the Buckeye defense as was Curtis Painter. Something like 20-24. With Awareness that low zone defenses are completely useless because there is no reaction from the DBs and the CPU just dinks the ball over the middle all game long. I LOVE the challenge that these sliders present and I can see that people are getting good stats so I'm certain I need to work on my game a bit but, the issues above may be unavoidable without a few tweaks.

Here is how I play and what I do which may or may not help you out.

1) I call ALL PASS plays from the huddle ONLY! Then if I want to run I use an audible to run. Go through your playbooks and save your favorite runs that aren't the formation RUN audible to your audibles. Since there are only a few running plays that even work this year, its not too bad. This is from SG, if you run from under center this is not as much of an issue. But from SG the CPU knows your plays and calls against you plus with the slight delay after handoff you have to have numbers or you have no chance. If you call run from huddle they will bring an extra guy in the box. To avoid this call pass first then audible to run. I only run when I have as many blockers or MORE then defenders in the box. After/if you get your RB going and he turns yellow you can force things more as he seems to gain a step.

2) ROBO QB. I do not see this a whole lot but I like to put my CBs in man to man on almost EVERY play. I like to run a lot of cover 1 and cover 2 man stuff with safety over the top. I then mix up my LB play by either covering the short middle (key on TE first) or I manually blitz him. I also mix up pressing and not pressing. I agree that zone stinks for HUMAN against CPU and I hardly ever use it. I like to use one of the LBs who are in a zone by play call. This way I can gamble a little bit to try to get a coverage sack or blitz without giving up a TD. You don't want robo QB to go away entirely or CPU will just be too easy. Get pressure on QB by manually blitzing off the edge with your OLBs, it really helps and you can get to the QB a lot with elite LBs which you have. Raising DEF awareness creates a pick 6 festival and breaks the game IMO. If you absolutely feel the need to tone down the CPU lower their QB ACC to 40 but that will simply make game easier and CPU even more unlikely to throw the ball down field.

3) Shift your front line around a LOT. I like to move them after the CPU center does the blocking assignments with the pointing. I am not sure if this really helps or is just placebo but it sure feels like I get more sacks when I move my front line around after he points. I typically do this if I am going to set back and cover for a coverage sack.

4) Use "PASS COMMIT" a LOT if you are playing back with the safety or LB. Again, I am not sure if this helps but when the CPU starts roboing me and I can't get to the QB with my LBs, I will set back and defend myself and call "PASS COMMIT" on every play. Since I am defending I am not too worried about giving up a big run and it sure seems like you get more knockdowns with your CPU controlled guys when I call "Pass Commit".

That is what I do and I sometimes hold CPU QB's under 50% completion. If you can get lucky and get a pick early and rattle the CPU it can make all the difference. Since you are using OSU you should have no trouble racking up sacks and getting CPU QB pressure so keep practicing and try things above. I have been getting 3-5 sacks/game with Michigan in year 1 personell which does not compare to what you have.

[Keyser Soze]

Quote: Originally Posted by fistofrage

I played some dynasty games with these.... WKU 31 @ CMU 59 (me) Colo St. 29 vs. Colorado (Me) 32 OT But it felt when I really needed to, I bore down and willed the victory coming from 29-14 down with 3:30 left. Then I played the MSU @ Cal game 4 times. MSU (Me) 7 @ Cal 31, turned it off in 3rd Quarter. MSU 38 @ Cal 0, In the 2nd quarter and it was going to get worse. The Cal QB who is an impact player was 0-8 in the 1st Quarter with 4 picks. MSU 28 @ Cal 31, full game, exciting. MSU 25 @ Cal 14, MSU trailed 14-3 going into the 4th quarter. Had a pick 6 on final play of the game when score was 18-14. I think AI Def awareness should go up to 80 and possibly CPU run block at 100 and possibly AI RBA to 55. My fear is that when I get a really fast Defense, it will be too easy against the AI.

I think as you continue to play the game you will continue to want to adjust everything up, up, up for the CPU until you hit all 100s. The game has some randomness to it, largely how the CPU QB plays. If he is hot game feels hard to sometimes impossible. If he is ice cold it can feel like you are on varsity. I am sure defensive coordinators in real life feel about the same way.

[kgx2thez]

Fist,

How much different are these from the OS Pro Style one's we're using?

I love the fact that these make it difficult and people are losing to or getting good games from the CPU. What can we do to improve on the human running game (from a slider tweak perspective)?

[fistofrage]

Quote: Originally Posted by kgx2thez

Fist, How much different are these from the OS Pro Style one's we're using? I love the fact that these make it difficult and people are losing to or getting good games from the CPU. What can we do to improve on the human running game (from a slider tweak perspective)?

These are different, actually may be a little harder. But I think these are the real deal. Because the AI Def AWR needs to be at least 75, they will have a speed advantage over the offense. I can run pretty decent with these sliders, but if you had to do anything, just up human run block a bit, if you mess with RBA, your receicers will go nuts once they catch the ball.

[therizing02]

Quote: Originally Posted by Keyser Soze

Here is how I play and what I do which may or may not help you out. 1) I call ALL PASS plays from the huddle ONLY! Then if I want to run I use an audible to run. Go through your playbooks and save your favorite runs that aren't the formation RUN audible to your audibles. Since there are only a few running plays that even work this year, its not too bad. This is from SG, if you run from under center this is not as much of an issue. But from SG the CPU knows your plays and calls against you plus with the slight delay after handoff you have to have numbers or you have no chance. If you call run from huddle they will bring an extra guy in the box. To avoid this call pass first then audible to run. I only run when I have as many blockers or MORE then defenders in the box. After/if you get your RB going and he turns yellow you can force things more as he seems to gain a step. 2) ROBO QB. I do not see this a whole lot but I like to put my CBs in man to man on almost EVERY play. I like to run a lot of cover 1 and cover 2 man stuff with safety over the top. I then mix up my LB play by either covering the short middle (key on TE first) or I manually blitz him. I also mix up pressing and not pressing. I agree that zone stinks for HUMAN against CPU and I hardly ever use it. I like to use one of the LBs who are in a zone by play call. This way I can gamble a little bit to try to get a coverage sack or blitz without giving up a TD. You don't want robo QB to go away entirely or CPU will just be too easy. Get pressure on QB by manually blitzing off the edge with your OLBs, it really helps and you can get to the QB a lot with elite LBs which you have. Raising DEF awareness creates a pick 6 festival and breaks the game IMO. If you absolutely feel the need to tone down the CPU lower their QB ACC to 40 but that will simply make game easier and CPU even more unlikely to throw the ball down field. 3) Shift your front line around a LOT. I like to move them after the CPU center does the blocking assignments with the pointing. I am not sure if this really helps or is just placebo but it sure feels like I get more sacks when I move my front line around after he points. I typically do this if I am going to set back and cover for a coverage sack. 4) Use "PASS COMMIT" a LOT if you are playing back with the safety or LB. Again, I am not sure if this helps but when the CPU starts roboing me and I can't get to the QB with my LBs, I will set back and defend myself and call "PASS COMMIT" on every play. Since I am defending I am not too worried about giving up a big run and it sure seems like you get more knockdowns with your CPU controlled guys when I call "Pass Commit". That is what I do and I sometimes hold CPU QB's under 50% completion. If you can get lucky and get a pick early and rattle the CPU it can make all the difference. Since you are using OSU you should have no trouble racking up sacks and getting CPU QB pressure so keep practicing and try things above. I have been getting 3-5 sacks/game with Michigan in year 1 personell which does not compare to what you have.

Thanks man. I will give number 4 (Pass commit) a shot because with regards to 2 and 3 it sounds like we play a very similar type of game because I use ALL of those tactics. Maybe the zone defenses cannot be fixed. I use a TON of man press with one or two safeties over the top. Jenkins (All American) and Donald Washington are really tough to beat one on one.

How's your running game with Brandon Minor?

[kgx2thez]

Quote: Originally Posted by Keyser Soze

4) Use "PASS COMMIT" a LOT if you are playing back with the safety or LB. Again, I am not sure if this helps but when the CPU starts roboing me and I can't get to the QB with my LBs, I will set back and defend myself and call "PASS COMMIT" on every play. Since I am defending I am not too worried about giving up a big run and it sure seems like you get more knockdowns with your CPU controlled guys when I call "Pass Commit".

How do you call "Pass Commit"?

Even though they supposedly improved the zone coverages the CPU still picks you apart because the pass rush is too slow in getting pressure. They play a "little bit" closer but overall its nothing to noticeable like the KO/Punt coverage tweak.

[Keyser Soze]

Quote: Originally Posted by therizing02

Thanks man. I will give number 4 (Pass commit) a shot because with regards to 2 and 3 it sounds like we play a very similar type of game because I use ALL of those tactics. Maybe the zone defenses cannot be fixed. I use a TON of man press with one or two safeties over the top. Jenkins (All American) and Donald Washington are really tough to beat one on one. How's your running game with Brandon Minor?

My running game is pretty much dictated by what the CPU gives me. I run all SG sets with 3 and 4 WRs. If the CPU runs a lot of dime or that really spread out D (forget name) then I will run all day and for good yardage. However, if the set in a lot of nickle or 4-3 then i will not try to run much at all.

One thing that has helped my running game as of late (tidbit from Fist) to use the aggressive line UP more. If I have as many blockers as they do defenders (5 on 5 versus Dime for example) I will use the line shift UP every time. Really seems to help get a line push and opens up holes. Unlike most people, I use the SPEED button as soon as I see a hole to get my 4 yards and if I can make someone miss and get more great, but when I have my hole I go, go, go. I don't hit speed though until I have my hole so some plays I never even hit it as no clear hole developed.

If you are taking your LBs and blitzing off the edge you should get pressure. Sometimes the OT will pick me up but then the DE might get to the QB himself. I like to call plays where my OLB is in a zone coverage and then manually hot route him to Blitz. I will line him up on the LOS almost touching my DE and pre-push the analog stick as far down as I can without making him move. Then when the ball is snapped I hit the speed button and push down trying to get a step around the OT. If I get this step I will immediately start to slant in and try to decapatate the QB. If I get picked up then I pray that my DE gets in. If the OT peals back nicely or i get a slow jump i just go deep behind the qb as my presense typically helps to get the qb to poorly.

I haven't played with OSU but I assume that you should be terrorizing the CPU QBs big time. If you can get around the CPU QB fast, you will see him throw some ****ty floating passing that can be picked easily.

Oh, I get success manually blitzing the CPU's TE side as well when the TE backs up and I am able to cut in front of his face to the QB. This doesn't happen a ton but when it does its an almost sure sack as the OT is blocking the DE.

hope this helps.