If by chance you had been running cricket2002.exe already and tried to process the ODI batting.exe file then this error may come up. If it did otherwise, I have absolutely no idea what that means.
You should be choosing the one I sent today for bowling, thats the only one which has changed. Well, I suppose I will resend both now so that there is no confusion with those files. While I resend those, discard the old ones as it will add to more confusion.
...
Well such tests are a bonus Jonah, need not be sorry about that one. Infact it is good to notice these ones before we seriously start playing with this patch. I suppose this can only be happening on normal pitches, it might just be the height of the ball CPU is expecting. It might be trying to play a straight drive to a ball that is not low enough to play. On a green and hard surface it doesnt seem to have too many problems. Do send me the Straight Drive saf I will implement that one in the install, the one you used to bowl is it the one I have sent just sometime ago.Originally posted by jonah@Jun 18 2003, 10:42 AM
Sorry Ravi, I just can't get the cpu to bat out it's 50 overs. This one was played on a normal wicket, cloudy conditions. Edges were pretty good, not too many, but I've spotted a definate weakness.
If you bowl an off cutter or leg break with a seam bowler (fast or med/fast), on a good line/length, the cpu often misses the straight drive, so resulting in the batsman getting bowled. All the bowled wickets shown on the attached scorecard were out in this way. Other than that, cpu seemed more sturdy, although the run rate a little high (although that's probably my bowling!!).
I've tinkered a little with the straight drive saf (opened up the angle a little, and reduced the height in the early one so stopping the c&b I kept getting). I'll send it over to see what you think If you don't like it, that's fine...no worries
...
Fair enough, you might still get an odd wicket or two using this delivery but for sure it should happen once or twice a game and not every now and then. Can you do this before you play another game just to make sure we have countered this issue. Set the Type Aggressive to Type Moderate in the sdrive.saf saf file. This will ensure Straight Drive will be sparingly used.Originally posted by jonah@Jun 18 2003, 11:20 AM
It's difficult to give an exact percentage Ravi, but just by the scorecard you can see that it was a rewarding delivery for me! I'll try your latest batch to see how it goes, again on a Normal pitch.
I haven't tried batting yet, I want the cpu to play out it's 50 first
... .
.
Jonah, the next time you play do change the sdrive to moderate. The moderate shots also are played very frequently but not as much as an aggressive shot though. Making the Type Aggressive to Type Moderate will certainly reduce the number of batsman getting bowled although I am sure you can get one or two out in a game. The Straight Drive will still be played but most of the time to the right kind of delivery.Originally posted by jonah@Jun 18 2003, 03:35 PM
That's more encouraging Ravi
Pakistan (cpu) finished on 249 all out (44.1 overs). The straight drive problem was still evident, albeit not as much. Seemed more to the offspin of Vaughan (who bowled three with missed straight drives).3 more wickets fell to the seamers in that way. I must admit that I didn't change the sdrive to 'moderate', so maybe that would help, although I personally like that shot, so would like the cpu to still use it. Much better though
Anyway, now onto the run chase :unsure: ...
