Any of you guys still using my patch V.10

[tommyhorn33]

Hope this is not your last piece of work
Looking forward to this patch

 

[crick4life]

Guys attached are the file and the list.txt file. I have had problems installing this using the configs editor for some reason. Batting was ridiculously hard owing to the ball conditions not being changed.

The 10/20 overs pacing files are not in place in this patch. I will look forward to updating it in a day or two. Please do not expect not to score over 300 on a hard pitch; it is possible to score over 300 on a hard pitch although the aerial shots and the advance shots are to be used cautiously. The CPU batting may be good but am not fully convinced it is perfect. I need more time to sort this one out so if anything you guys notice or do not like with CPU batting please let me know. I expect CPU to be very competitive in both forms of cricket but expect a slump in a total every now and then for realism. Shot selection of CPU will vary from pitch to pitch (hopefully) and will set good targets for us to chase.

When bowling and particularly when playing longer version games I suggest you guys use the software !xspeed to add realism to the game. This software will speed up the game by quite some pace making it hard to hit the same spot while bowling. It is also challenging to bat using this software as we get very little time to time a shot. Initially you guys may want to set the speed to 1.14, once the game starts to get easier then start upping the speed by .10+ till you get to a stage where you can?t speed any further and still play the game sanely.

Also there can be few little tweaks performed by you guys to suit your style of play. For those who find it hard to bat can use the configs editor and increase the BatWindowIdealSize to 1.5 in hard level. You can to start with play with easy settings and see how you go. If playing in easy/medium settings suits you fine for now then I suggest you continue to play in such modes. Once the patch starts growing on you, you can switch to hard level. Have fun and sure do let me know if anything. Make sure you use the list.txt attached in the message too.

 

[Radaga]

Ravi, i got your email, but if you have been sending me PM's i havent got them because my inbox was full.

I will give this one a go when i have some time.

But if you want to chat to me on msn i can tell you about the version i was using. I found a few bugs in it and some good stuff too.

 

[tomcress2000]

Hi Ravi,

I've installed your patch, but what do I have to do with the list.txt file?

Thanks

 

[Radaga]

Originally posted by tomcress2000
Hi Ravi,

I've installed your patch, but what do I have to do with the list.txt file?

Thanks

Put it into the folder where your Config Editor V2 is.

 

[tomcress2000]

Originally posted by crick4life
Guys attached are the file and the list.txt file. I have had problems installing this using the configs editor for some reason. Batting was ridiculously hard owing to the ball conditions not being changed.

The 10/20 overs pacing files are not in place in this patch. I will look forward to updating it in a day or two. Please do not expect not to score over 300 on a hard pitch; it is possible to score over 300 on a hard pitch although the aerial shots and the advance shots are to be used cautiously. The CPU batting may be good but am not fully convinced it is perfect. I need more time to sort this one out so if anything you guys notice or do not like with CPU batting please let me know. I expect CPU to be very competitive in both forms of cricket but expect a slump in a total every now and then for realism. Shot selection of CPU will vary from pitch to pitch (hopefully) and will set good targets for us to chase.

When bowling and particularly when playing longer version games I suggest you guys use the software !xspeed to add realism to the game. This software will speed up the game by quite some pace making it hard to hit the same spot while bowling. It is also challenging to bat using this software as we get very little time to time a shot. Initially you guys may want to set the speed to 1.14, once the game starts to get easier then start upping the speed by .10+ till you get to a stage where you can?t speed any further and still play the game sanely.

Also there can be few little tweaks performed by you guys to suit your style of play. For those who find it hard to bat can use the configs editor and increase the BatWindowIdealSize to 1.5 in hard level. You can to start with play with easy settings and see how you go. If playing in easy/medium settings suits you fine for now then I suggest you continue to play in such modes. Once the patch starts growing on you, you can switch to hard level. Have fun and sure do let me know if anything. Make sure you use the list.txt attached in the message too.

Hi Ravi, Ive test on a match seems very good, batsmen playing lots of different shots. Only problem Ive found so far is CPU batsmen get bowled to easily by yorkers, has anyone else found this is it just me?

thanks

 

[crick4life]

I have deliberately tweaked the shots to ensure we get wickets occassionally by bowling yorkers but not sure if that happens one too often. Attached is the scorecard from the game I just played as Pakistan against the Srilankans. It seems to me the CPU batting is perfectly tweaked. This was on a dry wicket in hot and humid conditions. Notice the wicket fall and the recovery by the CPU in the middle and late middle order. The spinners did not do too badly but still were taken to good enough runs on a dusty pitch.

I felt the batting was a bit too difficult, not sure if you felt the same. I have had to make batting far easier from what I posted here maybe its to do with my using of the !xspeed software. I will be eager to hear from any of you guys if the batting is a bit hard on the hard level for ODIs.

Tom, did you say CPU gets bowled out to yorkers quite frequently in ODIs or Test matches?

 

[tomcress2000]

Originally posted by crick4life
I have deliberately tweaked the shots to ensure we get wickets occassionally by bowling yorkers but not sure if that happens one too often. Attached is the scorecard from the game I just played as Pakistan against the Srilankans. It seems to me the CPU batting is perfectly tweaked. This was on a dry wicket in hot and humid conditions. Notice the wicket fall and the recovery by the CPU in the middle and late middle order. The spinners did not do too badly but still were taken to good enough runs on a dusty pitch.

I felt the batting was a bit too difficult, not sure if you felt the same. I have had to make batting far easier from what I posted here maybe its to do with my using of the !xspeed software. I will be eager to hear from any of you guys if the batting is a bit hard on the hard level for ODIs.

Tom, did you say CPU gets bowled out to yorkers quite frequently in ODIs or Test matches?

It was a ODI cpu v cpu though. Im painting room at the moment so don't have time to try myself, just wanted to see how the cpu batting was playing. In both englands innings and nz innings they were about 100/5 after 15 overs about 2 of the first 5 wickets were yorkers. England recovered to 250 all out, which is good, after about 35 overs (maybe trying to score bit too quickly aswell, but was on a hard pitch). In total england had 5 people bowled, nz currently 123/6 after 19 overs with 3 people bowled to yorkers.

 

[crick4life]

Thats a shame the yorker thing but I did not experience any such issues with the yorker. I may have bowled anywhere between 20-30 yorkers in the 50 overs I bowled and could bowl out only one batsman. Just in case you experience it a bit too much when you bowl let me know, its no big we can fix it. If in case you find batting a bit too hard I can upload the one I am currently playing with, its fairly reasonable to bat with.

 

[Radaga]

Ravi, a big problem with the one i was testing was that they rarley play front foot shots. (this is in ODI's)

The left the ball sometimes when they should have played a front foot drive. Actually i don't remember them playing any front foot shots besides the on drive.

So the problem was that they were playing all back foot shots and leaving deliveries on the stumps that were pitched up.

I played 2 matches, one with IXSpeed and one without.

Without i bowled them out for 126 in 23 overs.

and with IXSpeed i bowled them out for 118 in 21 overs.

 

[tomcress2000]

Originally posted by crick4life
Thats a shame the yorker thing but I did not experience any such issues with the yorker. I may have bowled anywhere between 20-30 yorkers in the 50 overs I bowled and could bowl out only one batsman. Just in case you experience it a bit too much when you bowl let me know, its no big we can fix it. If in case you find batting a bit too hard I can upload the one I am currently playing with, its fairly reasonable to bat with.

Hi Ravi,

If you could let me know what value to change to reduce the amount of people being bowled by yorkers, I can have a little play around with it?

Mnay thanks

 

[crick4life]

Tim, the one I sent to you was not the final version. You may have liked to test the one attached here.

Anyways, the one that makes batting easier and also the yorker thing fixed is attached. This will make batting a little bit more easier too.

 

[msamina]

Was out on vacation for the past few days. Will be downloading and testing this patch.

 

[crick4life]

You may want to wait a day prior trying this one out Murali. The one I will be uploading will have the front foot shot bug as pointed by Tim sorted and other little issues fixed.

 

[msamina]

Thanks Ravi,

I will wait for your update.