Playing a test match without the previous patch (without editing straight drive). I am india and the Cpu are the Windies. I found it easy at first and I was going along at 8 an over. However to compensate for such a high run rate, I have been losing wickets regularly and now I am around 300/8. The patch is really good and I have found all shots require correct timing and carry a risk. Dravid was clean bowled becasue i mistimed a defensive stroke! HoweverI have noticed the computer makes huge adjustments for you, which I didn't notice with the default settings for Cricket 2004. E.g. I played the reverse sweep and my batsman slid about 4 foot to the right in order to play the stroke. I will download the straight drive patch and try it out. Btw, what is xspeed?
Any of you guys still using my patch V.10
- Thread starter crick4life
- Start date
crick4life
International Cricketer
- Joined
- May 23, 2003
- Online Cricket Games Owned
The first and foremost when produced this patch was to ensure we enjoy high quality batting as well as bowling. Fair enough it may be a touch easy but to compensate that the values were tweaked to make sure we lost enough wickets. That way we know if we keeping playing strokes right through we will stand to lose wickets and may even get bowled out to a paltry score while keeping the run rate really high. In turn if you look forward to accelarate only in the death and preserve wickets there are more chances of lasting full 50 overs.
Also who wouldnt want to play shots around the wicket and that too against quality attack
. I thought we should have the ability to score as many as CPU and vice versa.
I think you are fair enough to say the batting is a touch easier. Although its not very easy to score too many against the spinners and swing bowlers I am finding it fairly easy to get runs of faster bowlers. In line is a little tweak to this patch which will make faster bowlers bowl tight and give away less runs.
As for !xspeed, Brad's already answered your question. You may want to search in google to find the software.
Also who wouldnt want to play shots around the wicket and that too against quality attack
. I thought we should have the ability to score as many as CPU and vice versa. I think you are fair enough to say the batting is a touch easier. Although its not very easy to score too many against the spinners and swing bowlers I am finding it fairly easy to get runs of faster bowlers. In line is a little tweak to this patch which will make faster bowlers bowl tight and give away less runs.
As for !xspeed, Brad's already answered your question. You may want to search in google to find the software.
Ravi, i agree with you here.
The top order goes out much too easily, for human and CPU.
Maybe if you change it to like you said, so at least 1 of the top 4 makes runs, and also i think the tail bats too well.
I think that number 9, 10 and 11 should be a lot easier to get out.
I played a few one dayers, and everytime it came down to the lower order to save the innings because the top 4 all failed.
Ravi,
Am not sure why. But, with the modification that you have put in I am able to restrict the batsmen with fast bowlers itself. See attached image.
I am bowling at that length outside off and the CPU either misses the ball or even if it hits, it goes to a fielder. I am using fielding option, Open 1. Zimbabwe have till now scored only 18 off 5 overs. I swing into the batsmen so that it does not go for a wide.
Am not sure why. But, with the modification that you have put in I am able to restrict the batsmen with fast bowlers itself. See attached image.
I am bowling at that length outside off and the CPU either misses the ball or even if it hits, it goes to a fielder. I am using fielding option, Open 1. Zimbabwe have till now scored only 18 off 5 overs. I swing into the batsmen so that it does not go for a wide.
In the above image, the ball is yet to pitch. It will pitch a little further down and the ball will swing in. The batsmen seem to miss this. Should I try to restore the original GOB and then install from it. This is your latest version 12 patch.
Maybe I am talking too soon. I will continue and see how well Zimbabwe do. I scored 248 all out in 43 overs. Zimbabwe have not lost any wickets, so they might still win.
Will keep you posted.
UPDATE: After 15 overs Zimbabwe are 48/1. Bowling figures:
I. Pathan: 8 overs 28 runs 0 wickets
L. Balaji: 7 overs 20 runs 1 wicket
I went from your previous version 12 to the new version 12 in the middle of this match. Maybe the new patch has not taken effect ??
UPDATE 2: After 25 overs, Zimbabwe are 83/2.
Bowling figures:
I. Pathan: 8 overs, 28 runs, 0 wickets
L. Balaji: 8 overs, 22 runs, 1 wicket
A. Kumble: 5 overs, 27 runs, 1 wicket
H. Singh: 4 overs, 5 runs, 0 wickets
To me, it seems like the CPU has a problem with balls bowled a little wide outside off-stump for spin bowlers as well as fast bowlers. Notice the difference in figures between A. Kumble and H.Singh. I made H. Singh bowl outside off always, while A. Kumble did not do that. The CPU tries to hit the balls to the on-side and misses most of them leading to the slow run-rate.
Maybe I am talking too soon. I will continue and see how well Zimbabwe do. I scored 248 all out in 43 overs. Zimbabwe have not lost any wickets, so they might still win.
Will keep you posted.
UPDATE: After 15 overs Zimbabwe are 48/1. Bowling figures:
I. Pathan: 8 overs 28 runs 0 wickets
L. Balaji: 7 overs 20 runs 1 wicket
I went from your previous version 12 to the new version 12 in the middle of this match. Maybe the new patch has not taken effect ??
UPDATE 2: After 25 overs, Zimbabwe are 83/2.
Bowling figures:
I. Pathan: 8 overs, 28 runs, 0 wickets
L. Balaji: 8 overs, 22 runs, 1 wicket
A. Kumble: 5 overs, 27 runs, 1 wicket
H. Singh: 4 overs, 5 runs, 0 wickets
To me, it seems like the CPU has a problem with balls bowled a little wide outside off-stump for spin bowlers as well as fast bowlers. Notice the difference in figures between A. Kumble and H.Singh. I made H. Singh bowl outside off always, while A. Kumble did not do that. The CPU tries to hit the balls to the on-side and misses most of them leading to the slow run-rate.
Last edited:
crick4life
International Cricketer
- Joined
- May 23, 2003
- Online Cricket Games Owned
Murali, there were couple of weak spots left for CPU not able to put it away particularly the length balls outside off and the ball bowled on the body without any width to score off. These may have been the reason you may have been able to restrict them bowling there. When I said I wanted the faster bowlers to be potent I meant when we are batting, I felt it was easy to cart around even the world class bowlers like McGrath, Gillispie et al.
You were fair to say you are restricting the CPU from scoring by bowling a particular length but at the same time Zimboks are not much of a team to write home about. I have seen instances where better teams and players score better. That said there were few changes to make CPU a little less aggressive to ensure it doesn't lose one too many wickets in the first half of its batting. The accelaration should and will happen from 35 overs onwards. There were little accelaration at the start as well so it evens out in the end I think. There are couple of changes lined up i.e, making the top order score better and also time better. Do keep me posted of your progress it means a lot to this patch.
You were fair to say you are restricting the CPU from scoring by bowling a particular length but at the same time Zimboks are not much of a team to write home about. I have seen instances where better teams and players score better. That said there were few changes to make CPU a little less aggressive to ensure it doesn't lose one too many wickets in the first half of its batting. The accelaration should and will happen from 35 overs onwards. There were little accelaration at the start as well so it evens out in the end I think. There are couple of changes lined up i.e, making the top order score better and also time better. Do keep me posted of your progress it means a lot to this patch.
crick4life
International Cricketer
- Joined
- May 23, 2003
- Online Cricket Games Owned
ND are not so good in terms of team strength which may have contributed to the above score. Another reason may be the top order batsmen failing quite often as I mentioned couple of posts above. There are couple of things that can be tweaked if you want lesser teams to score as well, you can lower the ScoreBias in the ODI hard, lower the BatEdgeBias as well and see if it makes any difference.
I have completed this match, Ravi. You are right. The acceleration does happen after the 35th over. I was able to see a difference in the way the CPU was batting from the 30th over onwards. But, still was able to restrict the CPU using a slightly short pitched delivery outside the off-stump similar to the ones that I have attached here.
I think the CPU did play reasonably well. But, the acceleration seemed to happen a little too late. But if I erred from that line, the CPU did bat well. I will follow your suggestion and try it against other teams. It may just be Zimbabwe. There were no wickets by stumping, which was great. A few Zimbabwe batsmen did come down the pitch, but connected the ball.
I will be trying this ploy against SA in the tri-series finals. Overall, yours is the only patch where I have seen the CPU bat well. There was no collapse but still the CPU was competitive. Hopefully, SA will score some runs from this length and line bowling.
Great job and thank you for your effort.
Great job and thank you for your effort.
crick4life
International Cricketer
- Joined
- May 23, 2003
- Online Cricket Games Owned
Good win mate, you seem to have been getting better and better of late.
I will see what I can do about the perfect timing for accelaration. Maybe let them consolidate between 15-25 and get a bit aggressive post 25 overs. I will tweak a little to ensure CPU hits well when offered width outside off. I think we need to keep certain spots open for good bowling otherwise CPU may post huge scores and win over us every other time.
I will see what I can do about the perfect timing for accelaration. Maybe let them consolidate between 15-25 and get a bit aggressive post 25 overs. I will tweak a little to ensure CPU hits well when offered width outside off. I think we need to keep certain spots open for good bowling otherwise CPU may post huge scores and win over us every other time.
Thanks, Ravi. I am getting better in batting but as you know I have always been all right in bowling.
Yes, I agree that some shots need to be kept tight to contain the run-rate. If width is offered on the off-side, the CPU should be able to play shots to the off-side, instead of trying to hit it to the on-side. This will ensure that the CPU scores well and be realistic.
Regarding pacing the innings, it will be good if the CPU accelerates after 25 overs. But, it should also not lose wickets. Is there a way to make the CPU steady the innings if it lost a wicket or two suddenly ?
Yes, I agree that some shots need to be kept tight to contain the run-rate. If width is offered on the off-side, the CPU should be able to play shots to the off-side, instead of trying to hit it to the on-side. This will ensure that the CPU scores well and be realistic.
Regarding pacing the innings, it will be good if the CPU accelerates after 25 overs. But, it should also not lose wickets. Is there a way to make the CPU steady the innings if it lost a wicket or two suddenly ?
Similar threads
- Locked
- Sticky
