Playmakers Madden 12 Custom Sliders

[Playmakers]

Quote: Originally Posted by mikeb88

thanks for clarifying that PM. Im gonna do a test game as a mediocre team in the jags vs the packers. Aaron rodgers should be able to carve up my defense. I will post stats after the test game

ok you test him out from the higher end and i have a feeling if the higher end doesn't work the lower end can be asserted.

In fact the lower my actually surprise a lot of people because there are more passes that are out of reach of both the WR and defender which leads to more realistic incompletions

So i always have a backup plan....LOL!

[CarpCarter]

I also have to echo others' concerns that the CPU run game is really overpowered. It breaks too many tackles and just takes off into the open field for huge chunks of yardage and long scores. Pretty much unless you have a second player in the vicinity to immediately tackle the RB after he breaks the initial tackle, he's gone.

[Playmakers]

Quote: Originally Posted by CarpCarter

I also have to echo others' concerns that the CPU run game is really overpowered. It breaks too many tackles and just takes off into the open field for huge chunks of yardage and long scores. Pretty much unless you have a second player in the vicinity to immediately tackle the RB after he breaks the initial tackle, he's gone.

This i simply don't understand because if you go back to yesterday there were several guys who reported the CPU simply couldn't run the ball with this setup

Broken Tackles-12
Run Block-24
Fumbles-49

So all i really did was switch it to 12, 34, 54 there was not a single change in the CPU Broken Tackle slider or the Human run defense setup

Unless the actual Blocking slider or Fumble slider gives the CPU that much of a boost up I'm totally confused

I'm sure there are others who saw those post yesterday with concerns regarding the CPU running game being easy to stop with Run Block at 24

[mikeb88]

Quote: Originally Posted by Playmakers

ok you test him out from the higher end and i have a feeling if the higher end doesn't work the lower end can be asserted. In fact the lower my actually surprise a lot of people because there are more passes that are out of reach of both the WR and defender which leads to more realistic incompletions So i always have a backup plan....LOL!

Results are in from first test game. jaguars(user) 14 vs packers(cpu) 34
sliders set at

passing
qb acc 18(gabbert)/92(rodgers)
pass block 76/76
wr catch 60/60

pass D
reaction time 0/0
int 0/50
pass rush 90/90

Gabbert 16/23 164 yds, 0td 1int / rodgers 16/23 217 yds, 4td 0int
Jones-Drew 19att 47yds 1td / grant 21att 84yds

I use the all madden rushing sliders, user rushing 0/24/50. Rushing became ineffective for me as rodgers came out firing in the second half and turned a 14-10 deficit into a 34-14 victory so I had to become one-dimensional and attempt to comeback with a rookie qb, which obviously did not happen. CPU rushing felt realistic. Packers D sacked me 3 times while I failed to sack Aaron Rodgers

What is your opinion on these test results PM?

[CarpCarter]

Quote: Originally Posted by Playmakers

This i simply don't understand because if you go back to yesterday there were several guys who reported the CPU simply couldn't run the ball with this setup Broken Tackles-12 Run Block-24 Fumbles-49 So all i really did was switch it to 12, 34, 54 there was not a single change in the CPU Broken Tackle slider or the Human run defense setup Unless the actual Blocking slider or Fumble slider gives the CPU that much of a boost up I'm totally confused I'm sure there are others who saw those post yesterday with concerns regarding the CPU running game being easy to stop with Run Block at 24

I suppose a lot of it is up to individual experiences, but in both games I noticed the CPU consistently either shrugged off initial linebacker and lineman tackles or was able to sidestep CPU defenders making bad plays on the ball (unlike the CPU defense which consistently swarms to the ball).

Interestingly, the stats from this game went:

Mathews: 3 carries, 0 yards
Tolbert: 14 carries, 140 yards, 125 after first hit, 3 20+ runs (20, 48, 51)

That's a ton of yards after contact, both as a result of broken tackles and poor reactions by CPU defenders. On both long runs Tolbert broke through linebacker wrap-up tackles and went untouched through the second level. Neither defensive playcall was a blitz.

[Playmakers]

Quote: Originally Posted by CarpCarter

I suppose a lot of it is up to individual experiences, but in both games I noticed the CPU consistently either shrugged off initial linebacker and lineman tackles or was able to sidestep CPU defenders making bad plays on the ball (unlike the CPU defense which consistently swarms to the ball). Interestingly, the stats from this game went: Mathews: 3 carries, 0 yards Tolbert: 14 carries, 140 yards, 125 after first hit, 3 20+ runs (20, 48, 51) That's a ton of yards after contact, both as a result of broken tackles and poor reactions by CPU defenders. On both long runs Tolbert broke through linebacker wrap-up tackles and went untouched through the second level. Neither defensive playcall was a blitz.

Ok now put CPU Run BLock at 24 play the same game when you have time and then show me your results

It might just be CPU Run Block needs to reduce down to 28 or 30

[Playmakers]

Quote: Originally Posted by mikeb88

Results are in from first test game. jaguars(user) 14 vs packers(cpu) 34 sliders set at passing qb acc 18(gabbert)/92(rodgers) pass block 76/76 wr catch 60/60 pass D reaction time 0/0 int 0/50 pass rush 90/90 Gabbert 16/23 164 yds, 0td 1int / rodgers 16/23 217 yds, 4td 0int Jones-Drew 19att 47yds 1td / grant 21att 84yds I use the all madden rushing sliders, user rushing 0/24/50. Rushing became ineffective for me as rodgers came out firing in the second half and turned a 14-10 deficit into a 34-14 victory so I had to become one-dimensional and attempt to comeback with a rookie qb, which obviously did not happen. CPU rushing felt realistic. Packers D sacked me 3 times while I failed to sack Aaron Rodgers What is your opinion on these test results PM?

this is what i kinda expected......i believe the INT slider is making the CPU hold the ball or not force throws which leads to sacks....

I believe the CPU WR's don't get open for some reason and the QB's in Madden who mostly suck in awareness have a hard time finding the open guy.

That is basically what i was getting when i did the initial test for CPU QB's

The only thing i can't figure out is why the QB's are acting weird duing Franchise games as opposed to Play Now games

[The Reedo]

I used the viks. with these settings. THOUGHTS????????????

22/78
76/76
54/60

6/12
24/34
44/54

0/10
50/50
90/100

22/22
10/12
14/14

Minnesota Vikings at Oakland Raiders
Sep 25, 2011	1ST	2ND	3RD	4TH	SCORE
Minnesota Vikings ()	0	14	3	14	31
Oakland Raiders ()	7	7	0	7	21

Team Stats Comparison
	MIN	OAK
Total Offense	375	280
Rushing Yards	152	161
Passing Yards	223	119
First Downs	18	16
Punt Return Yards	7	2
Kick Return Yards	56	143
Total Yards	438	425
Turnovers	0	0
3rd Down Converstion	8-11	4-8
4th Down Conversion	0-0	0-1
2-Point Conversion	0-0	0-0
Red Zone Touchdowns/Field Goals	2-1	3-0
Penalties	0-0	0-0
Posession Time	28:46	19:14

Minnesota Vikings PASSING C/A YDS TD INT d.mcnabb 18/24 233 2 0 RUSHING ATT YDS AVG TD a.peterson 22 125 5.6 2 d.mcnabb 3 -6 -2.0 0 t.gerhart 2 20 10.0 0 r.d'imperio 1 4 4.0 0 p.harvin 1 9 9.0 0 RECEIVING REC YDS AVG TD v.shiancoe 5 89 17.8 2 m.jenkins 3 46 15.3 0 p.harvin 3 14 4.6 0 d.aromashodu 2 17 8.5 0 r.d'imperio 2 7 3.5 0 b.berrian 2 28 14.0 0 j.kleinsasser 1 32 32.0 0 DEFENSE TACK SACK INT TD r.ayodele 3.0 b.robinson 1.0 d.reed 1.0 j.allen 1.0

Oakland Raiders PASSING C/A YDS TD INT j.campbell 18/19 168 2 0 l.houston 1/1 2 0 0 RUSHING ATT YDS AVG TD d.mcfadden 17 86 5.0 1 m.bush 5 74 148 0 j.campbell 1 1 1.0 0 DEFENSE TACK SACK INT TD l.houston 1.0