CPU Strike Frequency - Leave It Alone (Discussion)

[TNKNGM]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

Psycho - great post!!

I currently have it set at 2 which like you said is like a yearly ritual to reduce it....but I feel like 2 is working very well for me right now and I'm finishing games in the 62-68% range for strikes from the CPU

Personally, I feel like the users patience, skill level, their ability to judge pitches and lay off while waiting for good pitches to hit is way more of a factor in deciding, pitch counts, strike % and ultimately their success offensively

[Smallville102001]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

I agree, but I also contend that the AI seems to approach DD differently than playing "straight" veteran (or rookie) levels...at least in the large sample I had going last year it did...



VERY familiar with your sets over the years, Sir!

Quality work, indeed...

That being said, I'm hoping someone may have a stat based breakdown on that level, like PsychoBulk did for what I'm guessing, is the All Star level...

It's kind of a moot point, because I will prob end up using QC again this year, but strike percentages and how they vary from level to level, is an annual point of interest for my slider based OCD...

While I am seeing better results compared to this same point in time last year with DD. I am also seeing a more realistic amount of foul balls by both the CPU and user as while. I am thinking this years game is not going to need a lot of changes compared to the past.

[ralphieboy11]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

I always spend the first few weeks with the game running cpu vs. cpu games to perfect sliders before the roster guys do their thing. I have to agree with most of the sentiments here. This is probably the best the game has been out of the box to see realistic results in cpu vs. cpu games.

Without getting into too many details, this is what I've found so far.

Walk numbers seem to be spot on, while usually they are a little low historically.

Batting average is a little low. I've been around .240 so far through over 60 games, although this has been with the better starting pitchers.

Seeing more double plays than I like. 1.11 per game which is pretty high. Just from the eye test, it seems infielders arm strength could be reduced. They really whip it around the infield quickly.

Also, if I could get stolen bases up a bit maybe I'd see less situations where the double play would be a possibility.

Overall, I'm very pleased. Not a lot of work needed this year to get things where I like them.

[Aensland]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

Been running CPU vs. CPU games myself and I do agree things seem well improved over previous years. It could be just me but the CPU seems to hit more ground balls than in 2014. That, coupled with strong infield throws could be a good reason for the excess double plays. Outfield arms still seem a bit too strong as well, and could be toned down a notch. Also, CPU batters appear to chase fewer balls out of the strike zone, compared to 2014.

I've always enjoyed tracking CPU vs. CPU stats through Nomo's spreadsheets. Hopefully he or someone else will continue this year.

[BrianU]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

Ralphie and Aens, I was hesitant before but seeing you guys are doing the same thing as me we should share all of our data to increase the sample sizes.

Nothing will match the effort Nomo puts in, I don't have the willpower or patience to do 75 game sets like he does which is needed to fully appreciate the averages. This is my first year tracking CPU vs CPU stats and I am still figuring it out as I go. I really only have time to do 25 game sets of data. The current set I am on is using exhibition mode using each team at least once. I try to spread out the ratings of the pitchers with a ratio like this:

1 game of high 90s pitchers
2 games of low 90s/high 80s pitchers
6 games of low 80s/high 70s pitchers
4 games of mid 70s/low 70s pitchers

I think that is a pretty fair distribution to replicate the talent of pitching in the MLB.

My next data set I will use the franchise mode method. Simming 2 months in and just CPU v CPUing every game on the schedule.

Right now I see strike percentages on point (first pitch strike % slightly low but early count % is spot on so I am wary of changing Strike Percentage slider.)

I am not best at adjusting sliders so I am hoping I can get help with that part of my tests and ask what should be adjusted to improve the averages.

I am going to PM Nomo and see if he is okay with me using and publishing his spreadsheet to the public. The data is not perfect but I do think it's fun and useful to see. I would love to see what your guys stats look like too if you feel comfortable sharing.

[Bobhead]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

You also have to consider the person's OTHER sliders.

Here's an example:
I actually thought strike frequency was perfect at default. But while strike % was great, I found that the quality of pitching was a little too high (not enough hung pitches and such).

So I lowered Consistency a few clicks, and then quickly realized that those hung pitches were messing with my strike percentages. Pitches that would have ended up outside of the zone instead hung up and counted for strikes.

Thus, literally the only reason I've lowered Strike Frequency at all, is to balance out the change I made to Pitch Consistency.

I think the relationship between sliders is a critical part of achieving that perfect balance!

But yes, I agree, the CPU's tendency to throw outside the zone is probably as spot-on as it's ever been.

[Gagnon39]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

What about CPU's pitch accuracy and pitch consistency? Do you believe these should be changed? I really like statistical analyses like this. Great job.

[CaseIH]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

At last...in my opinion, this one slider that always caused so much consternation, so divided opinion, and almost univerally HAD to be reduced year on year to get realistic ratios/walk totals etc...NO MORE!

Ive played now 17 games since getting the game (not the largest sample size granted) but ive seen enough from my collated stats to tell me this year...its different.

Remember, CPU Strike Frequency only affects EARLY counts, NOT the whole at bat, so whats key here is basically first pitch strike numbers, percentages, basically.

The real MLB first pitch strike percentage was 60.3% last year, in 2014.

From my 17 games on DEFAULT CPU Strike Frequency...

64%
51%
70%
67%
58%
58%
64%
72%
51%
60%
61%
63%
57%
71%
51%
61%
66%

The average of those 17 games?

61.47%

That, fellow slider men, is, based on the history of this series with this slider...INCREDIBLE!

Generally in years past this figure has always been around 70% or above in game, way too high, and its needed the CPU K Frequency slider clipping to 2 or 3 to correct the problem - well no more.

Of course there will always be differences here, due to play styles/whos pitching etc, if you swing at what was going to be a ball its a strike etc, that can distort the figures, i get that, we all know that, but never, ever, in the history of this series has it been so damn good, this slider, on DEFAULT!

Now, the reason for this thread is because ive read through all the other respected slider makers sets and, aside from one, youve all (automatically probably from years past and i dont blame you for this) clipped the CPU Strike Frequency down...im here to say i dont think you need to, in fact if you are going down to 2/3 and even 4 to a degree, you are putting the CPU at a likely disadvantage in early counts, because my stats show (and yes, 17 games, yada yada) that its not needed.

Of course you will still get some games in the 70's and some in the low 50's etc, and you SHOULD, the 60.3 in real MLB last year is just an average, doesnt mean every game should regress to the mean, but my overall average, when i calculated it, staggered me, knowing the history of this slider, that i simply had to start this thread.

Id like to hear other slider gurus thoughts on this, you may not be seeing it, you may, i dont know, but i can guarantee you this...this key slider is NOT working the same way it did in years gone by and there definitely needs to be adjustments made for it.

Discuss away!

This is something I have always dropped way down every year. This yr it does seem different and I haven't moved it from Default. Been really happy with how all the sliders are this year. Other than pitch speed I have had to drop, but that's on me because of health, that I haven't had to adjust anything except lower foul ball frequency and as usual reliever stamina, and that has always had to be dropped with this game as its never been realistic.
This yr imo the sliders at default are near perfect, and it plays as realistic as ever. Now I do use QC's, so that might be why the strike frequency seems perfect at default, but I had to drop it last yr with QC's.


Only thing I might change is it seems with analog that throwing is quite challenging to bases this year. Only throw I have ever had trouble with is going to home using analogI had to really pay attention, but this yr its all the bases, so I might lower throwing errors down 1 to see if that helps, as I have never had any issue with analog throwing till this yr.

[mlblover15]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

how does this affect those of us that are QC users???

[ParisB]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

I'm at 3 for now, but generally agree. I just haven't seen any reason to bump it up yet any further.

I started at 0, but just like previous years, turning it down just leads to higher pitch counts. Most of the 2-0 and 3-0 counts just end up being 3-2 counts. The CPU will throw "get me over" strikes to either even up the count or for you to crush it.

Bottom line, I don't find it leads to more walks...just higher pitch counts in general (and easier pitches to crush).

At 3 it's been balanced so far. I might go to 4 after I test a lot more.

For walks, I usually just turn down Pitch Speed. You would be amazed how many balls the CPU throws on the black/corners, which are easier to take if you have enough time to judge it..

Anyway, just like Psycho, I'm otherwise at Default for everything else.

[coreyerb]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

I'm at 3 for now, but generally agree. I just haven't seen any reason to bump it up yet any further.

I started at 0, but just like previous years, turning it down just leads to higher pitch counts. Most of the 2-0 and 3-0 counts just end up being 3-2 counts. The CPU will throw "get me over" strikes to either even up the count or for you to crush it.

Bottom line, I don't find it leads to more walks...just higher pitch counts in general (and easier pitches to crush).

At 3 it's been balanced so far. I might go to 4 after I test a lot more.

For walks, I usually just turn down Pitch Speed. You would be amazed how many balls the CPU throws on the black/corners, which are easier to take if you have enough time to judge it..

Anyway, just like Psycho, I'm otherwise at Default for everything else.

Sounds like my experience too in looking to make walks more realistic. I'm not hacking too much but everything in a 3-ball count is either right down the middle or painted perfectly and they get every borderline strike call. I have strike frequency at minus-3 just to make pitch counts more reasonable.

If I tweak pitch speed does that carry over to non-online Diamond Dynasty matches and such, or is that locked on default pitch speed?

[bukktown]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

how does this affect those of us that are QC users???

This is my first year using QC and I lead the league in batting walks. I think I will need to up this slider and was hoping to find some other QC users feedback here.

[PsychoBulk]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

Just as a point of reference.

Through 7 games in my franchise im leading the entire league in walks with 31, yes, over 4 a game, with 9 in the last game alone!

This slider really should be left at default this year.

[jpreston4]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

Is anyone playing on Veteran? I'm a relative newbie to the game. I played my buddy's Show 13 on his PS3 a good bit, so I generally know how to play, but this is my first attempt at my own franchise. I'm just going with the progressing settings that adjust as I get better, and right now, I'm on Veteran (about 6 games into the season). I've noticed that I get relatively few walks, and I have to adjust the CPU control and strike frequency quite low to even draw one or two a game. The most ridiculous example was RA Dickey. I had CPU control at 3 and Strike Frequency at 1, and he had something like 76 out of 88 pitches thrown for strikes. It was insanely frustrating. I mean, I got some hits off him and won the game, but the ratio was way off. If I didn't jump on the first pitch, it was 0-2 every at-bat. Other games haven't been nearly that bad...I usually draw at least 1, maybe 2 walks. But it's still not optimal, and the control and strike frequency sliders are still at 3 and 1, respectively.

Is All-Star more realistic? Will I get thrashed as a newbie?

[Bobhead]

Re: CPU Strike Frequency - Leave It Alone (Discussion)

Just as a point of reference.

Through 7 games in my franchise im leading the entire league in walks with 31, yes, over 4 a game, with 9 in the last game alone!

This slider really should be left at default this year.

I actually put mine back at default about a week after my original post in this thread (the one where I mentioned having it at 4 because of other changes).

I too am happy with it there.