Test Cricket tweak

[crick4life]

Originally posted by amber22@Jun 18 2003, 06:14 PM
:wall: I am most unluckiest fellow.That dll problem is still evident.That error is from my System.I tried installing windows 4 times but nothing.Now when I tried to uninstall it , it does not uninstall properly

Currently I am trying to install the game in ME. But I have heard many of you face problems in ME.I dont know what to do :wall: :wall: :wall:

Well, whats the problem there Amber? Why dont you simply install a fresh copy of windows after reformating the hard disk(well if you can afford to).

 

[sangamm]

can i still get the patch?

 

[amber22]

Well , hopefully the game is running well on Me for me.Now back to the files Ravi , the latest files you sent me on [email protected] I am playing that on hard pitch.Only played 8 overs with batting.I will post the more news after finishing the game

 

[amber22]

can i still get the patch?

Well sangamm , the patch has'nt been released yet.This is just the testing going on.I am sure Ravi will reply to you.

 

[Rangeela]

well good to know amber the game is working fine for you now

 

[crick4life]

Originally posted by sangamm@Jun 19 2003, 04:55 AM
can i still get the patch?

Sangam as replied by Amber above, the patch is still being tested by several others. It may be released after its made sure it is foolproof and worth playing with. It has been given to few willing testers over the last few days and hopefully we are 75%-80% through.

 

[amber22]

Ravi , I started another match against aus on a hard pitch.But this time (not sure about jonah and others) but I found batting a bit hard for me.The only problem was the r.rate kept on declining and by the end of 40th over I was just 150/5.There were 2 outside edges though they felt short of first slip.There were inside edges also one of which nicley carried on to the wicketkeeper.

And for Cpu batting , 80% of CPU runs come in boundaries.It's because most of the time a shot is hit even very lightly it carries to the boundaries .And exactly reverse was happening when i was batting.
And Ravi , a suggestion for you , I think you should retain most of the batting tweaks from the first ODIBATTING.exe you sent me.It was good.If you dont have it , I still have in my inbox and can send you.Just let me know.

Keep it up

 

[crick4life]

Originally posted by amber22@Jun 19 2003, 07:15 AM
Ravi , I started another match against aus on a hard pitch.But this time (not sure about jonah and others) but I found batting a bit hard for me.The only problem was the r.rate kept on declining and by the end of 40th over I was just 150/5.There were 2 outside edges though they felt short of first slip.There were inside edges also one of which nicley carried on to the wicketkeeper.

  And for Cpu batting , 80% of CPU runs come in boundaries.It's because most of the time a shot is hit even very lightly it carries to the boundaries .And exactly reverse was happening when i was batting.
  And Ravi , a suggestion for you , I think you should retain most of the batting tweaks from the first ODIBATTING.exe you sent me.It was good.If you dont have it , I still have in my inbox and can send you.Just let me know.

Keep it up

Sure Amber your suggestions are taken into consideration. Ideal would be to score between 250-280 on a hard pitch by a Human, I have to confess not much tweak has gone into batting and when Jonah posts his batting experience, we should be able to come to a conclusion as to how difficult is it to bat. What score did CPU make? You forgot to mention in your post and also how many wickets could you get? We want to make sure CPU does not lose too many wickets on a hard pitch whereas I expect it to lose quite a few on normal/green/damp/wet pitches. How about the bowling experience, which bowler was the best to use on hard pitch. Also what kind of run rate did the CPU maintain throughout the game. Thanks for your feedback and am sure we should be able to get a decent patch in not much time.

It will also help if you could play a less capable opposition, the batting I suppose will be a lot easier than against the OZs.

 

[jonah]

Originally posted by crick4life@Jun 18 2003, 11:20 PM

Was the batting style of CPU good, was it defensive enough and also the edges were they controlled. What do you also think abou the battting by the lower order? Let me know or post the scorecard.

Cpu batting seemed prettty good Ravi. Edges were OK, not too many, cpu seemed to look for gaps, and field placings were important to stop boundaries.
The top order collapsed (73/4) but there were a couple of good partnerships in the middle order. Lower order chipped in with a few. I really need to try it a few more times to see if there are any major inconsistencies.

As for batting, it sure is a test (but that's OK; for me it's more rewarding to win after a hard test than being able to whack the ball to all boundaries). Patience is rewarded, although some shots seem difficult to play (cover drive for one) to the really quick bowlers. Again, I need to play a few times to get a proper feel for it.
15 overs I'm 45/2, chasing 249.

 

[amber22]

Jonah is right .The cover drive in particularly looks difficult to play against fast bowlers.The CPU batting was ok as it did lost only 4 wickets while chasing the total.The rest looks fine

And you said that after the 49th over, save the game and run the bowling .exe if you are batting first.but what if we get all out before the 49th over.As the game does'nt allowed to be saved just after the 1st inning we have to bowl 1 over before saving.Now for that 1 over , the cursor did'nt appeared so how to do the bowling

 

[crick4life]

Originally posted by amber22@Jun 19 2003, 09:22 AM
Jonah is right .The cover drive in particularly looks difficult to play against fast bowlers.The CPU batting was ok as it did lost only 4 wickets while chasing the total.The rest looks fine

And you said that after the 49th over, save the game and run the bowling .exe if you are batting first.but what if we get all out before the 49th over.As the game does'nt allowed to be saved just after the 1st inning we have to bowl 1 over before saving.Now for that 1 over , the cursor did'nt appeared so how to do the bowling

I agree with your opinion that the hard pitch settings were a bit tough to bowl on for sure. There was absolute mayhem in the first few overs, I have now tweaked it. The normal pitch settings although looks perfect, its only the hard and dry surface which needed a bit of tweaking. Now we seem to have perfect file settings for hard/dry surfaces although it still is not going to be very easy to restrict the CPU to under 300. One way to bowl economically is to alter line, length and pace of the bowling. Faster you bowl on the hard pitch, faster the ball will go. At the same time the slower ball will not be able to get wickets, you got to bowl faster to get wickets but have to use it as a surprise delivery. You could always turn to spinners to get the score down, these are few things I noticed while bowling. The patch requires some more testing and we will shortly know if there are any shortcomings.

If you get bowled out before 50 overs, hmm not sure how we can counter this one. Let us look forward to what Jonah and others do in such a situation.

 

[jonah]

I always save the game after each over (a habit I got into with BLC, coz it would crash occasionally). Once you get used to doing it, it becomes second nature. Then, when I get to 8 or 9 down (in case I lose 2 wickets in 1 over), I switch to 'bowl.exe', restart the game and bat out.

Ravi, have you tried to bat? What do you think? I'm currently 58/4 (23 overs).

 

[crick4life]

Originally posted by jonah@Jun 19 2003, 09:55 AM
I always save the game after each over (a habit I got into with BLC, coz it would crash occasionally). Once you get used to doing it, it becomes second nature. Then, when I get to 8 or 9 down (in case I lose 2 wickets in 1 over), I switch to 'bowl.exe', restart the game and bat out.

Ravi, have you tried to bat? What do you think? I'm currently 58/4 (23 overs).

I havent tried batting fully yet but I do think you need to win some and you need to lose some to keep the interest in the game. On a wet/damp pitch 200 should be chasable, on a green pitch anywhere around 220 should be chasable, normal say around 230-240 and on a hard/dry pitch we should certainly be able to chase anywhere around 270-280. I am sure we can tweak enough to chase or set this kind of total. I am done with tweaking the bowling setup files for pretty much all the pitches, I am midway through a game against India playing as NZ on a hard pitch and the CPU has put on 74/1 off 12 overs which is all right I suppose. One wicket to fall was Shewaj who scored a brisk 38(22) and edged one to 1st slip while trying to play an ondrive against a ball moving away. So far so good, once you are done with your games let me know I will send the new ones across to you guys. What do you guys think, let me know.

We can probably get the cover drive into action with reducing the frame rate for the shot. I will give it a try once we are over and done with the current tweaks.

Jonah, inspite of making the change to the sdrive.saf to Moderate, it still is played at times and has infact bettered the CPU shot selection.

 

[jonah]

Ready for those new files Ravi!
I'm ashamed to say that, chasing 249, I collapsed to 129 all out (39 overs) . Pretty realistic, as I WAS England!!!
I had a decent 5th wicket partnership building, but lost them both in quick succession, and in trying to up the run rate took too many chances with new batsmen.
I agree Ravi that we should win and lose matches, and these batting files prove to me that you need to get 'in', and then shots becomes more rewarding. I had a batsman (Troughton) on 36 (54 balls) who had just played a lovely lofted straight drive for 4 back over Shoaib's head. I got too cocky, and next ball was caught in the gulley off the sq cut. The rest was history.
If you could make the cover drive(front foot) more playable, that would be great.
Cheers .

 

[crick4life]

Originally posted by jonah@Jun 19 2003, 10:31 AM
Ready for those new files Ravi!
I'm ashamed to say that, chasing 249, I collapsed to 129 all out (39 overs) . Pretty realistic, as I WAS England!!!
I had a decent 5th wicket partnership building, but lost them both in quick succession, and in trying to up the run rate took too many chances with new batsmen.
I agree Ravi that we should win and lose matches, and these batting files prove to me that you need to get 'in', and then shots becomes more rewarding. I had a batsman (Troughton) on 36 (54 balls) who had just played a lovely lofted straight drive for 4 back over Shoaib's head. I got too cocky, and next ball was caught in the gulley off the sq cut. The rest was history.
If you could make the cover drive(front foot) more playable, that would be great.
Cheers .

I have made the batting easy but not that easy you can whack every ball. You will still need to play in but just that you can keep the score tiking, the CPU will still bat very well but it will mistime some of the shots which will result in runs not scored. Again, not much testing from my side has gone into it hence cant really assure the perfect results. Give it a go and anyway we have time on our hand, here they come.