Sliders, CPU vs. CPU, and stats

[Redacted01]

First off, I want to know if sliders are even relevant in computer only games. I find it much more realistic to test in these applications to see if results are even close. If sliders do have an impact, then I need some help!

I watched 2 CPU games this morning, one on Heisman and one on AA. I know am going with AA because of the dumb field goal logic on Heisman and I don't have to brag to the max that I play on Heisman. I had some good AA sliders on NCAA years ago but I'm actually into this game and want it to work. The problem is the stats. The unbelievably unrealistic and **** stats!

I used teambuilder teams for this which may be part of the problem, but they were all closely rated; poor, but closely rated. I need to it with teams more like Auburn vs. Alabama and see if it still happens. Any way, the stats. The quarter lengths are producing almost the correct number of plays (~147 per game, but I doubt 8 minute quarters fixes it), but these plays are god-like, or the defense is horse**** haha. Warning: there are no typos below.

Heisman - 9 minute quarters
McNeese State - 59
Lamar - 38

Mcneese: 13/20, 185 yards, 1 TD; 50 rushes, 450 yards, 7 TD; 5 interceptions; 635 yards of offense on 70 plays
Lamar: 14/32, 216 yards, 1 TD; 36 rushes, 168 yards, 3 TD; 1 intereception, returned for TD; 384 yards of offense on 68 plays

AA - 9 minute quarters
Colgate - 87
Holy Cross - 62

Colgate: 36/59, 638 yards, 7 TD; 25 rushes, 72 yards, 3 TD; 2 interceptions, 3 fumbles recovered; 710 yards of offense on 84 plays
Holy Cross: 12/28, 345 yards, 5 TD; 44 rushes, 420 yards, 4 TD; 765 yards of offense on 72 plays

Really??? 1475 yards of offense in a single game? Sure, 156 plays is too many. I wish the computer did not rush so much, but 10.6 yards/play for a team? That's twice the average last year.

I'm going to run one more game with two good teams and see if this keeps up, but if sliders do affect CPU vs. CPU games...

CAN THIS BE FIXED???

At least when I play I can try to slow the game down a bit, but I doubt I can slow it down that much.

[petty43]

Try SNs slider set ,they will improve your stats greatly.I use them and I'm finding there pretty darn good.

Sent from my PB99400 using Tapatalk

[Redacted01]

Re: Sliders, CPU vs. CPU, and stats

Will do immediately. Georgia just broke a 75 yard touchdown run on the first play against Auburn. Way way way too much offense.

[fldash]

Re: Sliders, CPU vs. CPU, and stats

For CPU vs CPU games, 9 minutes is WAY too long. Should be 6-7... Try to get around 120 plays (pass attempts + rush attempts for both teams).

[petty43]

Maybe turn down run block,turn up run D and turn up tackle ,bump 5 at a time until you find a happy middle.plus when I test sliders turn off home field advantage or use a neutral site.
Sent from my PB99400 using Tapatalk

[Redacted01]

Re: Sliders, CPU vs. CPU, and stats

For CPU vs CPU games, 9 minutes is WAY too long. Should be 6-7... Try to get around 120 plays (pass attempts + rush attempts for both teams).

I cut it down to 8. 136 was the average number of plays last year in FBS. First the problem was time of possession, but I was like, as long as the number of plays is right. Now they get so many yards on each play that it's the yardage you have to try and get right, even if it means they are cut short 20+ plays.

edit: Thanks for the home field tip. I'll try that for the next game. I'm trying SN's for Auburn/Georgia again and it already seems a bit better, but it's early. Georgia drove down field, but they got slowed in the red zone.

[petty43]

Try this. Tackle ability 55
Run block 45
Run defense 55
Pass rush 35
Int 25
Pass defense 40
QB 20
WR catch 45 to 50

The rest at 50 ... And this is only for CPU vs CPU

Sent from my PB99400 using Tapatalk

[Redacted01]

Re: Sliders, CPU vs. CPU, and stats

I think at this point, it is safe to say that CPU vs. CPU is never going to converge to the mean. Guess I'll try the sliders out in an actual game and maybe get some better results. It's not has bad as 80 whatever points, but at the end of the 3rd, it is 43-26 Georgia and the Bulldogs are about to score again. Auburn's no huddle just kills it because they go 3 and out in 30 seconds or less every other drive. Wish there were more options to slow the computer down with clock management. I doubt removing the homefield advantage will fix it up either.

Teams are on pace for 138 plays which is right in that range. It may not turn out to be as bad as I thought, but every game should not be a shootout with 90+ points scored combined.

[petty43]

Keep tweaking...you will get it.look more at your runs per carry stat ,and Qb percentage after you get that right,then work on your time to get the right amount of plays.

Sent from my PB99400 using Tapatalk

[Redacted01]

Re: Sliders, CPU vs. CPU, and stats

Final score...
Auburn 40
Georgia 59

These teams are scoring enough points in a game to cover 2 games and getting enough yards to cover at least that.

Auburn: 10/25, 255 yards, 2 TD; 24 rushes, 177 yards, 3 TD
Georgia: 12/26, 235 yards, 1 TD; 57 rushes, 415 yards, 2 TD; in the red zone TWELVE TIMES.

Almost 1100 yards of total offense is not fixable. 132 plays is dead on in the range of normal number of plays, but cutting that 8+ yards per play down to about 5 is probably hard to do. So I'll probably stick to 8, but I tend to run slower so 8-9 is probably going to keep the plays in that 140 +/- 10 range.

I'm burned out right now, but I'm hoping that Human vs. CPU will turn out to be great with these, which is what the sliders were intended for in the first place.

Thanks for the info. I probably haven't worked hardcore on sliders since NCAA 06 so I'd like to get a great set here. SN's are hopefully a good starting point. I will also remember to turn off home field or play at a neutral site or something. Probably will use even teams as well just to get a good base. There are things broken that I know can be corrected because people have said they've gotten great games with sliders thus far. I'm looking forward to it.

[fldash]

Re: Sliders, CPU vs. CPU, and stats

Adjust the offensive CPU sliders down, like pas accuracy and RB ability, and blocking, increase the the defensive CPU sliders, like pass rush. It's not that hard.

[Redacted01]

Re: Sliders, CPU vs. CPU, and stats

Adjust the offensive CPU sliders down, like pas accuracy and RB ability, and blocking, increase the the defensive CPU sliders, like pass rush. It's not that hard.

I'll crank them all the way up/down depending on which one later and see if it has a dramatic effect. It's going to take something dramatic to cut offensive production down by 50%, but at the same time, QB's are already not completing passes so turning QB accuracy is going to hurt that. If anything, I need to turn accuracy up and hope the turning running down and defense up gives a solid result.

[drob2342]

Re: Sliders, CPU vs. CPU, and stats

Try Varsity at 8 mins....it was ok at default. Needs less run d and cut down on the fg kicking.

[dxdude2004]

Re: Sliders, CPU vs. CPU, and stats

I'm actually rather satisfied with mine:

Varsity
7 minutes
0 speed threshold

I've seen breakaway runs with these, it just all depends on the play calling. QB scrambling is also very nice too (as long as your QB is scrambling at the right time and not directly towards an opposing player lol). Seriously, give these a try.

[MI88]

Re: Sliders, CPU vs. CPU, and stats

Try Varsity at 8 mins....it was ok at default. Needs less run d and cut down on the fg kicking.

What he said. Varsity 8 min default is perfect.