Review Demo impressions thread

I posted elsewhere that I think that a 3 over test was a strange choice for a demo. It feeds into the whack-it-around frenzy that I thought they were trying to get away from. From a purely cricketing and gaming point-of-view a scenario from the first test would have been great. Survive 6 overs as Monty and Jim; super aggressive fields etc. Aus's target would be to take one wicket.
That said I can see why from a marketing point of view that is less accessible than just biff the ball around.

Agreed, especially as 20/20 cricket has opened up cricket to less "traditional" fans, looking for big totals and more wickets. A 3 over game in colours would have made more sense, not a 3 over test match???:facepalm

This would have appealed more to casual gamers and hard core crickets fans would not be so worried of 10 runs an over test matches!!

Was an odd choice but I spose we at least got a demo and shouldn't complain too much.............:hpraise:hpraise:hpraise
 
No the AI doesnt seem to react to you hitting it consistently in the same place in the demo. Hopefully thats different in the full game in a normal over match but as stated the AI has not been optimised for this 3 over game demo.:D

It does most of the time in my experience. Eg M.Johnson was bowling bouncers at me as he hit me with a short ball and followed this up with more. I walked across my stumps twice and hooked square for 4, then next ball there was a deep square leg :-)
 
Run outs must be a priority issue, if that makes it through into the final game I'm gonna be pissed.
 
one more day for the pc demo! Cant wait!

Just to get you drooling. Top edged a hook that went to the wickey with KP, looked mint!!

sorry but I seem to have been focusing on the negative with this game since the demo and thought I would post something positive which it deserves:banana2
 
Why would Codies release the demo on the day of the test match, that means i won't hardly play the game. Surely, it would make sense to release it today!
 
Just one day left. Come on codies please no delays this time like XBOX live. You wont have Microsoft to blame for the delay now.... So you better stick to your word.;)

And Kshitiz we want a Demo [cough] Ex[cough] [cough]pander;) as quickly as possible.
 
Ok guys I have a question which is probably premature or kinda left-field - but then again thats the way i roll :P

Anyhoo, bear with me and tell me what you think of this..

As ive said a few times i havent played the game but followed all the youtube vids closely, most of them ive watched a few times. And ive noticed that, as with most previous cricket games, this game is also somewhat devoid from reality in the sense that its pretty much a batsman's game.

What i mean with that is that in real life the same is true but to a lesser extent and in real cricket you sometimes come across a complete jaffer of a delivery which is just too good for the batsman - I havent noticed this in any previous cricket games or in fact in AC2009. Sure you can "bluff" the batsman and so on but that is more to do with building pressure and bowling a good spell - not necessarily bowling a ball that is particularly hard for the batter to play.

So last night I thought of perhaps an implementation for future games which brings the bowler's strike rate more into play, we all sometimes focus on a bowler's average but having a strike rate of 60 also shows that the dude takes a wicket roughly every 10 overs. Dont you guys think that the "jaffer" situation could be somehow tied into a bowler's strikerate? So that every now and then a bowler will bowl a ball that is seriously good and you dont have to bank on a batsman just playing a poor shot? Because thats the way it seems at the moment, you can fool him into expecting a short one and in fact crush his toes etc, but as i watched the vids I saw some deliveries which would (in real life) be terribly difficult to play yet in the game it doesnt cause the batsman problems because he got his timing right...

Im not saying it should be an over-used implementation, for instance for Steyn who has a strike rate of 39 in tests it could mean he would bowl (for instance) 3 such deliveries in a test match whereas someone else with a poor strike rate would trouble the batsmen less. This also doesnt mean it should be "auto-wicket" but I mean if you bowl and inswinger at pace, which straightens then I dont care how good you are, but it takes some batting trying to keep it out or even get bat to it. At the moment an occurence like that within AC2009 or any other game for that matter, is handled a little too easily by batsmen for my liking.

In real cricket its not ONLY about building pressure, bowling to your field or roughing up the batsmen...sometimes it takes a piece of brilliance from a class bowler to swing the momentum.

Hope this wasnt TOO off-topic...i just saw a lot of repeated arguments going on in this tread and would like your thoughts on something a bit different.

Cheers!
 
Ok guys I have a question which is probably premature or kinda left-field - but then again thats the way i roll :P

Anyhoo, bear with me and tell me what you think of this..

As ive said a few times i havent played the game but followed all the youtube vids closely, most of them ive watched a few times. And ive noticed that, as with most previous cricket games, this game is also somewhat devoid from reality in the sense that its pretty much a batsman's game.

What i mean with that is that in real life the same is true but to a lesser extent and in real cricket you sometimes come across a complete jaffer of a delivery which is just too good for the batsman - I havent noticed this in any previous cricket games or in fact in AC2009. Sure you can "bluff" the batsman and so on but that is more to do with building pressure and bowling a good spell - not necessarily bowling a ball that is particularly hard for the batter to play.

So last night I thought of perhaps an implementation for future games which brings the bowler's strike rate more into play, we all sometimes focus on a bowler's average but having a strike rate of 60 also shows that the dude takes a wicket roughly every 10 overs. Dont you guys think that the "jaffer" situation could be somehow tied into a bowler's strikerate? So that every now and then a bowler will bowl a ball that is seriously good and you dont have to bank on a batsman just playing a poor shot? Because thats the way it seems at the moment, you can fool him into expecting a short one and in fact crush his toes etc, but as i watched the vids I saw some deliveries which would (in real life) be terribly difficult to play yet in the game it doesnt cause the batsman problems because he got his timing right...

Im not saying it should be an over-used implementation, for instance for Steyn who has a strike rate of 39 in tests it could mean he would bowl (for instance) 3 such deliveries in a test match whereas someone else with a poor strike rate would trouble the batsmen less. This also doesnt mean it should be "auto-wicket" but I mean if you bowl and inswinger at pace, which straightens then I dont care how good you are, but it takes some batting trying to keep it out or even get bat to it. At the moment an occurence like that within AC2009 or any other game for that matter, is handled a little too easily by batsmen for my liking.

In real cricket its not ONLY about building pressure, bowling to your field or roughing up the batsmen...sometimes it takes a piece of brilliance from a class bowler to swing the momentum.

Hope this wasnt TOO off-topic...i just saw a lot of repeated arguments going on in this tread and would like your thoughts on something a bit different.

Cheers!

In AC 2009 Some balls that the bowler bowls are soo good that you just have a "|" to hit the ball perfectly. I have seen so many times when I m hitting them around I get a delivery like that and all I end up doing is sky it or get an edge. So I think the AI is much much smarter than any of the previous cricket games. Also when we talk about BLC 99 we forget how easy it was to score in that game at around or more than 10 RPO. The only reason I can think about being that is most of us were young and liked to go after that bowling and its not the case anymore hence we want something test match type.

I was playing BLC 99 the other day and had a run rate of around 17 in 10 overs game.

In this game if you try that you have 3-4 wickets down in 3 overs game so that at least is a plus.
 
In AC 2009 Some balls that the bowler bowls are soo good that you just have a "|" to hit the ball perfectly. I have seen so many times when I m hitting them around I get a delivery like that and all I end up doing is sky it or get an edge. So I think the AI is much much smarter than any of the previous cricket games. Also when we talk about BLC 99 we forget how easy it was to score in that game at around or more than 10 RPO. The only reason I can think about being that is most of us were young and liked to go after that bowling and its not the case anymore hence we want something test match type.

I was playing BLC 99 the other day and had a run rate of around 17 in 10 overs game.

In this game if you try that you have 3-4 wickets down in 3 overs game so that at least is a plus.

Ahhh ok cool, see thats where actually playing the game helps lol Glad theres is a BIT more for the bowlers out there this time around..
 

Users who are viewing this thread

Top