Originally posted by crick4life@Jul 7 2003, 11:53 AM
Originally posted by zimrahil@Jul 7 2003, 10:19 AM
Originally posted by crick4life@Jul 7 2003, 10:27 AM
I wanted to check with you guys if you guys have used Zimrahill's online gameplay patch. If yes then does the CPU sweep every yorker bowled or at times tries to play other shots as well.
ravi, in the Online Gameplay patch, the cpu shouldn't sweep yorkers at all.
Thanks for the info, Zimrahill. One issue I am facing with the implementation of flick shots to play against yorker is that it is being played not only against the yorkers but also against a full length ball bowled on the pads. The frequency of that shot being played by CPU is far less now with further tweaking but I am having trouble getting it to play all the yorkers using this shot. At times CPU attempts Straight drive and gets out, is there a fix you might want to suggest for this if you are aware of. Otherwise the flick shot was the best to happen, I hope other agree with me.
Well I could write an essay about this subject of cpu missing the ball all the time :o
Look at things like
-straight drive (default is set to 2,2,2 -> stumps, batsman length)- amend the length to 1 and reduce slightly the reward value. Cpu will still play the straight drive to yorkers but a lot less frequently
-the difficulty setting - I have used minus values. Eg the cover drive with my current settings hardly ever gets missed by cpu now. My current difficulty setting for cover drive is -9.1000. Cannot remember off hand, but I think straght drive is something like -19.000
-frame values. As you will know, the frame values determine how soon/late a shot is excuted. Too often the cpu gets bowled by yorkers balls because the keyframe 0,1,3 or 4 frame value is used and shots are played far too early/late.
As you again will know, keyframe 2 has the supposed "ideal" frame rate for the shot in question. In my experience, the ideal frame rate is 1 or 2 higher than this. So for shots I anticipate that will be used against the yorker I adopt the following:
Eg, take the ondrive - Cannot remember off hand but say in the default files, the keyframe 2 frame value is 13. In my view frame value 14 would be about perfect. So I would set up the frame values as follows
keyframe 0 (very late) Frame = 15
keyframe 1 (late) Frame = 14
keyframe 2 (perfect) Frame = 14
keyframe 3 (early) Frame = 14
keyframe 4 (vey early) Frame = 13
As you hopefully can see, by making the very late shot played faster than normal, it has a better chance of being hit by cpu - same will very early shot being made to be played later (slower).
I hope you haven't fallen asleep whilst reading this but these are a few things I do to prevent the cpu from missing the yorker ball all the time.