Test Cricket tweak

[crick4life]

Originally posted by radaga@Jun 21 2003, 04:46 AM
these files sound pretty good, even though you havent released a patch or anything yet, could you email the files to me?
my email is: [email protected]

I suggest Ragada, you wait till the other testers confirm it is indeed good, different opinion really do matter. I dont want you to be installing something that will probably not serve much purpose.

 

[radaga]

Originally posted by crick4life@Jun 21 2003, 03:08 PM

Originally posted by radaga@Jun 21 2003, 04:46 AM
these files sound pretty good, even though you havent released a patch or anything yet, could you email the files to me?
my email is: [email protected]

I suggest Ragada, you wait till the other testers confirm it is indeed good, different opinion really do matter. I dont want you to be installing something that will probably not serve much purpose.

ok fair enough B)

 

[amber22]

Now I have been silly , that I forgot to save the screenshot but I will tell you what happened.The resuts were encouraging again.Played on a dry one against WI and bowled first.The 1st over gave me lbw.on 5 runs.The second fell on 39 and 3rd on 73.All 3 of them were LBW.
The 3rd wkt patnership was very good between Hooper(45) and Chanderpaul(69).But then Hooper played a shot in the air and got caught at point.The next over Chanderpaul was run-out.This was the turning point of the match.If anyone would have stayed a bit longer and supported Jacobs who was the last to go , WI might have score few more runs.But that happens in International Cricket (Very realistic)
The CPU scored 209 runs all out in 39 overs.
NOw came my batting.For the 1st 12 overs the runrate was around 3 runs or below but soon as the openers got their eye in the run-rate always kept between 4-5 runs.1st wkt fell on 116 runs as Sachin got caught at the boundary.Ganguly was runout and Sehwag got bowled on 74.the score was 149.The r.rate was 4-5 runs an over.Then Kaif and Dravid took charge and carried on to win the game in the 47th over.
The best thing I liked about the batting files were that the batsman has to play 30-40 runs before he gets on to big shots and the variation in pace from fast bowlers also help.The CPU batting was also good.

So now Ravi, I think we are almost there.Just waiting for jonah's reply.
I have tested the batting files on normal,dry,green and dusty pitches

 

[amber22]

ANd ravi when you will release the patch, please try that no problem is faced when we get all out while batting first because then we have to bowl the 1st over without saving and the cursor is not visible.

Can you try making a single exe by combinig those too(looks impossible :unsure:

 

[amber22]

Lets see what Jonah has to say

 

[T20]

Ravi,

your tweaks produced another wonderful game..though not reflected from the victory margin, it was a high pressure game where I had to fight really hard when bowling and batting.
Eng v Saf on dusty pitch, overcast and mild conditions. England were off to a flying start. I really had to keep my line right as anything on the pads or short was punished. I managed to get some wickets thru runouts when batsmen went for quick singles. Also as you notice some lbws as batsmen were playing across the line a lot but also managed to score quite a few runs there. 100 was reached in 13th over, and at the end of 15th 120(3). I had to keep chaning my bowlers and fields, a tough test in both departments. There was a big partnership for 4th wicket and at one stage score of 350+ looked possible. I was able to get back in the game from 24th over onwards when I finally got my field and bowling combination right. The result was some quick middle order wickets. Lower order scored few runs but England fell well short of the 50 ov. mark, allout for 250 in 33 overs.
Still a decent score and I had to give good opening partnership. After the opening pair put on 50 at 6/over, Gough provided the breakthru a Gibbs was caught in covers. Smith was out in next over and Kallis looked completely out of form was removed by Gough. After 15 overs SA 69/3 and pressure was on. Runs were difficult to score as Anderson bowled a good spell. 4th wicket partnership added 40 runs before Giles removed Rudolph - 109/4 in 25. It was tough to get in the game from there on as asking rate climbed and wickets fell at regular intervals. In the end SA were bowled out for 167 to lose by 83 runs.
Strangely both innings lasted for 33 overs

 

[T20]

Eng(cpu) SA
120/3 - 15 - 69/3
206/5 - 25 - 109/4
250/10 - 33 - 167/10

Clear difference between how both teams progressed in this game. SA made a great comeback from 25 over stage..satisfying when you have to work on field/bowling strategy and it works well. Batting was a challenge but enjoyable.

 

[T20]

btw re the yorkers, I don't think you should include the sweep fix in these tweaks. I bowl very few yorkers and in this game cpu played them well. I feel it's more realistic this way..When batting too I defend them most of the time.

on the other hand cpu bowled some good yorkers to get wickets..those odd ones which beat sweep or defense..and cpu made the most of it <_< :

 

[mani_gamer]

Originally posted by Shailesh@Jun 21 2003, 08:44 AM
btw re the yorkers, I don't think you should include the sweep fix in these tweaks. I bowl very few yorkers and in this game cpu played them well. I feel it's more realistic this way..When batting too I defend them most of the time.

on the other hand cpu bowled some good yorkers to get wickets..those odd ones which beat sweep or defense..and cpu made the most of it <_< :

i completely agree with shailesh
i also dont like my yorkers to b sweeped coz it makes the game
look nonsense :ice:
no way a batsman can sweep a fast bowler

 

[jonah]

Originally posted by mani_gamer@Jun 21 2003, 06:05 PM

i also dont like my yorkers to b sweeped coz it makes the game
look nonsense :ice:
no way a batsman can sweep a fast bowler

You obviously haven't seen any Twenty20 games..both Mal Loye and Nick Knight have played the sweep to seamers :blink: ...

Anyway, sorry for the delay in feedback Ravi (btw I like your 'Lazy Boy' idea...may have to take that up ).

Played the first innings of a match, Eng (me) v Pak (cpu), green pitch, sunny conditions. Pak batted first.
The cpu started briskly, going at 6 an over for the first 8 overs. I took 2 early wickets, Nazir and Hameed in the same over (4th). Then Youhana started his mammoth innings, and built a partnership with Hafeez until the 3rd wicket went down at 118. (Btw, cpu were 81/2 after 15 ).
Kahn went at 144, and after 30 overs Pak were 152/4, again an excellent r/r. Then catastrophe in the 31st over, with both Razzaq and Azhar run out in successive balls.
After 40 overs Pak were 221/6. The next 8 overs were pretty even; I took 3 wickets, cpu kept up the run rate, and I was looking to restrict them to 270-280, especially when Gough bowled Youhana for 124 (134 balls) in the 48th over. However, in the 50th over, Ahmed took 22 runs off Anderson, leaving Pak on 304/9 (50 overs). A tough ask for England there, especially as disaster has struck for England with Solanki c & b Shoaib for a duck in the first over .

All in all a great set of safs Ravi. Cpu kept a good run rate throughout, only going mad in the 48th over onwards (I'm glad to say). Played a variety of shots (cover drive along the ground through extra cover a bit more often would be good). Can't think of much else to say .

re the yorker discussion. I too restrict the amount of yorkers I bowl. I set myself a max of 10 yorkers per cpu innings that I can bowl (marking them off on some paper as I go). Therefore, I have the choice of when I use them...early on to try and get wickets, sapce them throughout the innings, or save some up for the slog overs. Also, I'm only allowed 1 per over. In any case, the cpu doesn't always get out to yorkers. So keep it as it is, IMO. If ppl want to bowl yorker after yorker, it's up to them, but this is a realism patch, and you wouldn't get McGrath, Pollock or Bond bowling continuous yorkers.

Now, onto the run chase... I just hope Tresco's got his magic bat out again, a' la The Oval on Friday :P ...

 

[crick4life]

Jonah, Good to see you back. Thanks for your feedback guys, its excellent. Looking at the scores above it sounds fairly realistic but for the runouts at a crucial times of the game. I will fix the runout issues probably try and restrict runouts. There will be a last set of files I will send out to you guys in which I will try to get the CPU consolidate a bit more and making the middle order a bit more stronger. I will let the Sweep to yorkers issue rest in peace for now. The Cover drive, hmm I will need to see if we bring this shot too often in the game will it affect other shots CPU plays. Will let you guys know very shortly, let us get the game rolling with the new ones I will send out for a week and see how it goes. From then we can turn our attention to Test Matches, that will be a bugger and will take a lot of time to test.

I also noticed from the scores Jonah, the spinners arent very effective on a green pitch which is what we were trying to achieve.

Also the batting setup files, what do you guys think about it? Amber seems to be happy with those.

 

[jonah]

Hi Ravi, don't worry too much about the cover drive; we don't want the balance messed up for just one shot.
I've started my innings, with mixed fortunes (see screenshot). After the first over c&b, runs flowed, not from the bat but from Shoaib's and Sami's (not sure how he got in the game, as Kaneria came in to bat :huh: ) wayward deliveries. take a look at the extras column. The extra bounce on the green top seemed too much for poor old Latif to handle, with short pitched stuff flying past him to the boundary . Certainly helped my run rate!
Tresco got out after getting one on the chin which went onto stumps, and Troughton got a dodgy caught at slip decision - it looked like it went to ground to me, Troughton stood his ground, but the umpires finger went up .
The cover drive is working beautifully Ravi; timing is of the essence . So far the batting safs seem good, with runs available to well timed shots, but you still have to work at it.
15 overs...79/3.

 

[T20]

LOL! I've been bowled few times after ball hit the body but not laying on the pitch like this :o :

 

[crick4life]

Originally posted by jonah@Jun 21 2003, 10:33 PM
Hi Ravi, don't worry too much about the cover drive; we don't want the balance messed up for just one shot.
I've started my innings, with mixed fortunes (see screenshot). After the first over c&b, runs flowed, not from the bat but from Shoaib's and Sami's (not sure how he got in the game, as Kaneria came in to bat :huh: ) wayward deliveries. take a look at the extras column. The extra bounce on the green top seemed too much for poor old Latif to handle, with short pitched stuff flying past him to the boundary . Certainly helped my run rate!
Tresco got out after getting one on the chin which went onto stumps, and Troughton got a dodgy caught at slip decision - it looked like it went to ground to me, Troughton stood his ground, but the umpires finger went up .
The cover drive is working beautifully Ravi; timing is of the essence . So far the batting safs seem good, with runs available to well timed shots, but you still have to work at it.
15 overs...79/3.

You are not doing very badly are you? Thanks to the byes, what do you reckon does it need fixing? If the extras gets a bit too much (it already is) we can fix the bounce, I am sure you will resent this . Good to know the cover drive is working, I will try to get that one going for CPU and see if it doesnt alter the CPU shot selection too much.

Jonah, I have reduced the bounce will send the update out to you guys after you guys are done playing with the current ones.

I have also fixed the cover drive for CPU batting, it really looks awesome. CPU seem to pick the line and length very well while playing this shot, executes brilliantly. There seems to be no ill effects on other shots or the judgement of CPU batsman. With the addition of frequent usage of Cover Drive for CPU batsman it is much more challenging to set the field now. I have tested these against the fast bowlers, will also test against the spinners and swing bowlers.

I have also made some more changes to the current Bowling setting making it less hard for the defensive batsman to get out. When playing any opposition, set couple of batsman to defensive and see what kind of difference it make. The defensive players are made to play a long inning who start slow but in the end will have 80-90% strike rate. The Aggressive ones will always looks to score runs but in the process can end up getting out.

 

[Statman]

Ravi..... What if I only use the bowling ODI exe and play the game. Is the only difference that the cursor appears right at the end of the ball being bowled ? There must be a way to integrate the whole thing.


As for the matches, well one this is for sure you have to be patient! I played a few matches on both hard and normal pitches. It seems to me that it takes too much time for the human player to settle in. I mean on a hard pitch it shouldnt take as much time for the batsment to get settled since hard pitches usually favor the batsmen. I was playing as Pakistan and Taufeeq Umar made 24 from 55 balls, while the minute Razzaq comes into bat he is blasting all over the place. I cant seem to find a balance between batsment ability and the batsmen settling factor. <_<

Also someone mentioned earlier that the reverse sweep seems messed up, well it does. Every time I tried the reverse sweep it goes too slow and almost always mistimed. Has this been deliberalty done.

Jonah.... Pak(cpu) scored 304 on a green wicket ?? :o Thats a bit too much for a green wicket dont you guys think so ?

Keep up the testing