Ashes Cricket 2009

Remove this Banner Ad

Still a few glitches that need sorting. I attempted a catch in the gully and timed it perfectly in the green circle, yet the catch was dropped. :thumbsdown:
That's strange, did the circle still show green once you had pushed the button to catch it?
EDIT: Oh and by the way, how super-awesome is Cameron White? He has a higher bowling rating than any other Australian spinner! Who needs Hauritz or Krezja when you have White! xD
LOL I noticed that, seems someone payed Transmission for some extra ratings.:rolleyes:

Love Cam though, so I'd play him anyway.:eek:
 
Had a go at the game 20/20 Aus vs England, 0/167 after 6 overs :D :thumbsu:
Could have been 6 or 7 down by now, cpu umpire missed 2 obvious LBW appeals, dropped a catch and misfielded the ball a few times (thus i got a few let off run out chances. Had a bit of a head turning moment, the ball was thrown at the stumps, i was way out of the crease, the ball MISSED the stumps and rolled to the boundry :thumbsu:.

I had a quick go at bowling just to get a feel for it, didn't get very far - was slogged for 4 in one delivery, had a chance for a wicket, hit the button to time the catch and the game froze :thumbsdown:. Console is fine, but will see what happens over more game time.
 

Log in to remove this ad.

That's strange, did the circle still show green once you had pushed the button to catch it?

I'm quite certain it did, unless there's a similar colour to green that I haven't noticed before. The only other colours that I know of are orange (possible catch) and red (no catch). If it wasn't those, it was definitely green.

It looked like a pretty difficult catch though. The ball flew low to Michael Clarke in the gully, and he caught it about half a foot from the ground, then fell down. From the moment he caught it to the moment he touched the ground, the circle was green. I even jumped up in triumph until the commentator (what's his name? The non-Grieg/Warne one...) said "Oh no he's dropped it!". I was pretty pissed. :(

I went through my batting innings against SA last night. Won the game by 4 wickets :D. I cheated though, lol. The SA bowling attack was ferocious (because the tail wagged a fair bit when they were batting, so they all had high confidence), and I was 4 wickets down in the first 3 overs. I restarted the game and saved after every other over from then on. I ended up bringing the required run rate down from 9 to 4 in the last 10 overs. However, if I had played this one properly, I would have been all out by the eighth over, lol. I think I'll stick to normal mode from now on. or at least until a patch fixes the AI slog-fest and bowling lines.:thumbsu:


EDIT: I just played a T20 match against England on normal. The result was a much more realistic experience. Batting may have been a little too easy, but England still bowled well. Sidebottom got Warner out with a beautiful ball to just outside off stump which edged Warner into the stumps. The final result was:

Australia won the game by 7 wickets

ENG - 7/128 off 20 overs (6.40 RR)

O. Shah - 41
A. Flintoff - 29


B. Lee - 4 - 2/19 - 4.75 RR
M. Clarke - 2 - 2/20 - 10.00 RR
Custom Player - 4 - 1/21 - 5.25 RR
M. Johnson - 4 - 0/10 - 2.50 RR


----------

AUS - 3/131 off 12.4 overs (10.50 RR)

D. Warner - 50
R. Ponting - 42*


R. Sidebottom - 2 - 1/20 - 10.00 RR
J. Anderson - 2 - 0/10 - 5.00 RR
A. Fintoff - 2 - 0/21 - 10.50 RR
S. Broad - 4 - 0/46 - 11.50 RR


The AI acted a lot more realisticly than when playing on hard. The AI batting didn't go on a slog fest from the get-go, despite it being a T20 match. They scored a fair few boundaries, but only when the occasion called for it (unlike on hard, where they slog nearly every ball). When bowling, the AI tried to keep the length full as to prevent me from scoring quickly, which was a good tactic on their behalf. I think I only scored one or two sixes for the match because of this. They also bowled really restrictively whenever I got a free hit, which was nice and realistic. :thumbsu:
 
Any PC users wanting a game tonight or some other time? It's really impossible to play against overseas players due to lag.

I'm waiting for the planetcricket.net player editor to be released before I hop into an Ashes series. I don't want to face Anderson at 120 km/h and Collingwood at 80.

I've had some fun in the other games though. Pakistan got about 180 off me in a 20/20 and I was going very well at the start, 0/40, but collapsed to be all out for about 110 in 12.
 
played the wii version last night (aquired it via means that i won't be mentioning here... ;))

its pretty cool, but nowhere near as amazing as i thought it would be. Graphics are pretty lame in comparison to the HD versions..
 
Played a match online against my boss and had the worst LBW decision in the history of the game!!!

Pitched and hit outside the line and wouldn't have hit a 3rd set of stumps. Hawkeye had it missing by crap load too

I lost it laughing though. Its the only bug i have seen so far
 
Just finished my 1st innings of the 2nd Ashes test at Lords. Things started off well and it was very realistic. England's run rate started off low (around 1.50) and slowly crept up to around 3.00 as the game went on. The final run rate at the end of the innings was 3.97, which was spot on for what you'd expect in a real test. The only problem is that they only scored 117 runs for the innings. I managed to bowl them out in the 29th over. By the 15th over they were 6/59, but Flintoff and Broad put on a good partnership to make it 6/97 by the 25th over. But England soon collapsed, all out only 4 overs later. If only the AI batsman wouldn't fall so easily, I could see them scoring around 300 runs in a days play, which is very realistic. The only solution to a higher score is to put the game on hard. But even then, you get the downside of having the AI go on a massive slogfest from the first ball, putting the run rate into double figures.

The way I see it, you have two options when bowling:

1. Play on normal, keeping the run rate realistic but giving away far too many wickets.
2. Play on hard, where the AI hold their wickets but leak a shitload of runs.

I'm torn between choices. I haven't played a test innings on hard, but if my ODI innings was anything to go by, England would be scoring upwards of 800 runs from a single days play...o_O

Oh and by the way, I GOT MY FIRST EVER LBW! Brett Lee bowled a fantastic string of balls including two successive balls just wide of off stump followed by a speedy yorker. The yorker got the batsman off guard (it was either Cook or Bopara), and hit him right in the right shin guard. :D
 
I just had a crack at bowling for the first time in hard mode. OMFG. They hit just about every gap possible. On the 3rd ball of the innings, i got hit for 6 off a late cut lol.

However, they hit the stumps way less on runout chances which was good.

The running between the wickets is not responisble enough, when you hit the ball it takes them ages to react and run. And when you want to quickly cancel a run, it just doesn't happen. They have the one animation of turning around and thats it. Nothing in between.
 
What is batting and bowling like using the WII remote?
batting is meh.. bit like baseball, all you have to do is swing, you still control where the ball goes with the d-pad

bowling is cool, how much you flick your wrist on the release of the "ball" will dictate how much swing/spin you get

as i said, it's ok, but not as revolutionary as i would have hoped
 

(Log in to remove this ad.)

Have had a good go at this from Saturday to today. And it isn't too bad, TSTL. There are some stupid bugs and glitches, and the unofficial names are quite annoying, but the gameplay isn't too bad.

Probably 7/10 for me.
 
Played a match online against my boss and had the worst LBW decision in the history of the game!!!

Pitched and hit outside the line and wouldn't have hit a 3rd set of stumps. Hawkeye had it missing by crap load too

I lost it laughing though. Its the only bug i have seen so far

So they have got the realism of a Rudi Kuertzen decision perfect :D
 
My comments (and have played recent cricket xbox360 games):

- Online lag is ridiculous (and I have ADSL2+), and this is after trying against 3-4 different opponents

- Although improvements have been made, the game is still weighed too much in favor of the batting

- Having said that, the batting dynamics are great fun

- Overall I'd say it's a 25% improvement on Ricky Ponting Cricket, however it still has a few areas to improve in.
 
Playing test series on hard... scored 650 odd last night..in about 65 overs... got a trophy then bowled England out for 90 in around 18 overs... Hauritz getting 8-45... I just custom the field to be strong on the offside get catches and have just discovered that by dropping short with the off spinner outside off you can get stumpings at ease... bloody stupid!! I think 6 of Hauritz wickets were stumpings...:(
 
In the last cricket game, I used to be able to get a team bowled out for under 10 runs easy.

If they ever do make a good cricket game, I'll be a happy man.
 

Remove this Banner Ad

Ashes Cricket 2009

Remove this Banner Ad

Back
Top