CPU Pacing - can't get it right!!

[CaptainOZ]

I'm having problems finding the best patch to keep the CPU pacing realistic in ODI's. It seems that no matter which patch I use, the CPU is very aggressive right from the outset and in a 50 over game, they are all out for 100 in 10 overs. So not only are they too aggressive, but they lose their wickets easily as well.

I just want the CPU batsmen to settle down a bit and preserve their wickets and build a partnership. It's wierd when I have them at 35/7 and they are still trying to hit every ball for four or six.

 

[The_gas]

your tredding a fine line my lad, i suggest using tutsi patch 7.0 and hard setting if u r finding them all to easy! I find with tutsi patch you can score runs, but so can they, in abundance! normally makes for an exciting game

 

[Chris Reilly]

I agree with CaptainOz. This is something that has frustrated me for sometime. I'm playing a National League game at the moment (Kent v Hampshire) on a normal pitch with Tutsi's 7.0 patch on hard setting and Hants are 87/7 off 15 Overs and I know my bowling ain't that good!! I also notice that at least 4 of these wickets were to diving catches at Gully. I suppose one possibility is to go into Savtweak and save the pitch settings to Hard as I've heard that can result in higher scores by the CPU but I think that brings its own limitations. I've tried various patches (all of which are very good in in other respects) and it seems a problem common to all. I think Ravi suggested somewhere in the forum that raising the CPU Random Factor makes the CPU harder to get out but I've tried this as well and it makes absolutely no difference as far as I can see. Bless 'em even Yorkshire managed to get around 250 a couple of times this season with wickets in hand on some of my visits to Headingley so if it's possible in reality it would be nice to reflect it in the game.

 

[CaptainOZ]

Good points, Chris. I used a patch from the cricket.co.uk website that seems to be pretty good for CPU pacing. Still, I had Australia at 202/8 with 10 overs to go and Gillespie and Symonds were slogging....it wasn't long until they'd given their wickets away. Which goes against one of the most important pieces of advice in one-day cricket: you have to preserve your wickets and bat out the full 50 overs.

The CPU just doesn't seem to understand that.

 

[Radaga]

if you change the settings to make the CPU play less 6Hit shots in the last 10 overs they shouldn't give up easy catches.
If you still have problems after changing that then try changing some of the shots from defensive or moderate to aggresive and then the CPU will play more defensive shots, providing in the pacing file you have set the aggresive shots to a high value.