Tutsi's A.I. Patches
- Thread starter tutsipoppy2
- Start date
shahid6995
Club Cricketer
Well Tutsipoppy, here is my review of 7.5 Beta 4.
So far, I guess I like it. This is the first match I am playing with it in the proper way, i.e. on Normal mode. The comparison I have with the previous patch I had (7.4) is mainly that in the previous one the AI was very defensive, not attempting any strokes while this one is adventurous, and plays its strokes once it tries to play itself in. Thats very good. What happened in my first match however is depicted below. I was able to blow out India for 143 in 42 overs with Umar Gul taking 6 wickets on a hard wicket, in India, sunny conditions. Most were catches in the slip cordon. Even though the Indians were on the back foot right from the start, they went for their shots and thats mainly why I was able to take wickets regularly. The batting appears not too different for me because as you can see I am 350 runs ahead at the end of the first day. Maybe its the way I play that I have not seen too much difference in the batting for me. Doesnt look like this match will last too much longer into the second day!
Once I play a couple more matches and if the CPU gives a better account of its batting in the second innings I may be able to update the review. I love how your patches have made this game so much more interesting though. Keep up the good work.
Indian innings
Pakistan bowling
Pakistan batting 1st innings end of 1st day.
So far, I guess I like it. This is the first match I am playing with it in the proper way, i.e. on Normal mode. The comparison I have with the previous patch I had (7.4) is mainly that in the previous one the AI was very defensive, not attempting any strokes while this one is adventurous, and plays its strokes once it tries to play itself in. Thats very good. What happened in my first match however is depicted below. I was able to blow out India for 143 in 42 overs with Umar Gul taking 6 wickets on a hard wicket, in India, sunny conditions. Most were catches in the slip cordon. Even though the Indians were on the back foot right from the start, they went for their shots and thats mainly why I was able to take wickets regularly. The batting appears not too different for me because as you can see I am 350 runs ahead at the end of the first day. Maybe its the way I play that I have not seen too much difference in the batting for me. Doesnt look like this match will last too much longer into the second day!
Once I play a couple more matches and if the CPU gives a better account of its batting in the second innings I may be able to update the review. I love how your patches have made this game so much more interesting though. Keep up the good work.
Indian innings
Pakistan bowling
Pakistan batting 1st innings end of 1st day.
Well tutsi, the thing that I said abt the India - Pakistan match on a dusty wicket, ur patch got really better in the second session and Pakistan went for more runs and have scored 274/6 at the end of Day 1. Great patch. Some things that I want to tell
1. Can you make the CPU not pad up too many deliveries? I bowled lot of balls with the fast bowlers in line with the stumps and the CPU leaves them and gets hit on the pads.
2. Once the batsman is set, he goes for his shots. But he dances down the wicket more to the spinners and most of the times misses it and gets stumped. Since he has full confidence, the dance down the wicket shot should most often connect for him. But thats not the case here. Often, I see well settled CPU batsman get out for 80 or 90 due to this shot. Most of the time, it doesnt connect for them at all. Since this game doesnt have a way where stumpings can be avoided by getting back to the crease in time, you can well turn this feature off of the batsmen dancing down the wicket. Or at least make it connectable for the batsman to score off.
3. Some more penetration of gaps in the field and rotation of strike by CPU batsman in the early stages of their innings can be included! May be, make them play a lot on the on side early in their innings and then as they gain confidence , make them play all kinds of shots.
4. Reduce the amount of aerial shots that the batsman plays after well settling (i.e. after 50, etc). They should play according to the field (i.e.) if the field is spread out,they should not go for much aerial shots and keep rotating and also at times take a risk of going for an aerial shot.
I batted a bit with ur patch and batting was easy. You can work more on the batting now and make it more challenging. Timing can be made perfect but at the same time, wickets should not fall to the cpu in a platter. Sorry if I am asking for much. Just wrote what all I thought. Rest upto U!
1. Can you make the CPU not pad up too many deliveries? I bowled lot of balls with the fast bowlers in line with the stumps and the CPU leaves them and gets hit on the pads.
2. Once the batsman is set, he goes for his shots. But he dances down the wicket more to the spinners and most of the times misses it and gets stumped. Since he has full confidence, the dance down the wicket shot should most often connect for him. But thats not the case here. Often, I see well settled CPU batsman get out for 80 or 90 due to this shot. Most of the time, it doesnt connect for them at all. Since this game doesnt have a way where stumpings can be avoided by getting back to the crease in time, you can well turn this feature off of the batsmen dancing down the wicket. Or at least make it connectable for the batsman to score off.
3. Some more penetration of gaps in the field and rotation of strike by CPU batsman in the early stages of their innings can be included! May be, make them play a lot on the on side early in their innings and then as they gain confidence , make them play all kinds of shots.
4. Reduce the amount of aerial shots that the batsman plays after well settling (i.e. after 50, etc). They should play according to the field (i.e.) if the field is spread out,they should not go for much aerial shots and keep rotating and also at times take a risk of going for an aerial shot.
I batted a bit with ur patch and batting was easy. You can work more on the batting now and make it more challenging. Timing can be made perfect but at the same time, wickets should not fall to the cpu in a platter. Sorry if I am asking for much. Just wrote what all I thought. Rest upto U!
shahid6995
Club Cricketer
I had hardly any yorkers....mannu said:
ravigoteti
Club Cricketer
my first post in this thread...but your patch works really well.. i tried several ones' including some of your previous ones and this one is really good!
1) I like the fact that you get some inside-edges, makes it a bit realistic.
2) Yea, the batsmen go for shots once they settle and sometimes they get out to spinners. If you can decrease that.
3) They do pad a lot of balls that you bowl on line.
4) Edges are fine...but tailenders are a bit weak.
will report later
ravi
1) I like the fact that you get some inside-edges, makes it a bit realistic.
2) Yea, the batsmen go for shots once they settle and sometimes they get out to spinners. If you can decrease that.
3) They do pad a lot of balls that you bowl on line.
4) Edges are fine...but tailenders are a bit weak.
will report later
ravi
tutsipoppy2
International Coach
tjh1989 said:
well yea...in my patch CPU,i.e,Players play according to their strength and weaknessness.
ashwinkm said:
the number one thing to improve in the FINAL version is that making TEST and spl. ODI batting difficult.
tutsipoppy2
International Coach
saisrini80 said:
well i would like to answer to these points.....
1. Do u rememeber in my earlier patches CPU always used to play a front foot defensive shot to every overpitched off-side deliveries irrespective of ball being too wide or not, this thing was highly UN-realistic and produced way too many UN-necessary edges. Now to fix that i have made cpu to LEAVE instead of defending deliveries missing off stump. Now the only side effect is that cpu tends too pad up balls just missing off stump. Can't Really fix this. I hope u understand.
2. Well there is no specific value which determines whether CPU plays advance shots or not....so i cant really turn this feature OFF
. This thing is a part of CPU aggressiveness. If i increase the agg. then cpu will play advance shots against spinners. All these things are interdependent on each other. Now to make cpu NOT play advance shots, i will have to cut down on cpu agg. which will against make things worse.3. Well making them play early on will result in cpu edging early on which will result in low totals. And for CPU too play on-side shots, u will have to bowl on middle middle-leg. U can expect the cpu to move to off-side and play a leg side shot like in real life. Its a GAME man....and don't expect much from EA for us to work on.
4. I will try and improve this, but again the thing is there are NO pacing files for TEST, for ODI we can cut down or increase CPU'S aerial shots by tweaking the pacing files, but NO such pacing files are there for TEST so again this thing is a part of overall CPU agg. But still i will try and improve. Players attributes also affect this thing. Defensive players like DRAVID may not go for aerial shots even at full confidence while agg. players like SEHWAG may go for it even at half confidence.
Yea....i will make batting for TEST & ODI harder and also play and HARD level oin the final version will make it more difficult.
mannu said:
NO. Nobody can reduce or increase that. There is no value for it in the Cricket 2004.
gold639 said:
Well as u know there is NO particular value for it.
Its just that through the exp. of making several patches and updating them, now maybe b'coz of the combination of several values, it makes cpu play more to their attributes than before.
Well really very hard to explain and imp. to implement again on a fresh GOB.
ok thanks tutsi for explaining. you do whatever is possible. but cant the batsman connect the advance shots most often when they play it at full confidence? coz the its easy to get wickets with spinners when they bowl a no power delivery and the batsman advances and misses it and he is stumped. anywayz, its fine if it is not possible
tutsipoppy2
International Coach
well i'll do whatever i can to improve the features. Rest is upto Cricket 2004's brain.
Also can gues tell me as to how do u find the pacing of the CPU in 20,50 overs.
The pacing in 20 overs is divided into - (1-2 Overs here and there)
0-3
4-6
7-9
10-12
13-15
16-18
19-20
The pacing in 50 overs is divided into - (1-2 Overs here and there)
0-7
8-14
15-21
22-28
29-35
36-42
43-50
So plz give a review about the pacing, coz this is another aspect which should be as close to perfect as possible.
Also can gues tell me as to how do u find the pacing of the CPU in 20,50 overs.
The pacing in 20 overs is divided into - (1-2 Overs here and there)
0-3
4-6
7-9
10-12
13-15
16-18
19-20
The pacing in 50 overs is divided into - (1-2 Overs here and there)
0-7
8-14
15-21
22-28
29-35
36-42
43-50
So plz give a review about the pacing, coz this is another aspect which should be as close to perfect as possible.
Last edited:
Tutsi, australia hit 283/5 in reply to 382 all out.I felt the pacing was a little off....they didnt really start going over the top till the 48th over even with a reqd run rate of 8 at the start of the game and almost 15 -20 by then. As you can see , they didnt really lose a lot of wickets because they never took chances till the last two overs. I feel if the pacing is tweaked and the batting is made a little tougher .. this will be a great patch as the cpu definitely tends to score more runs...