And you thought Cricket 2005 had bugs?

[greencarrot2]

Bug number 1:

On that little cutscene when the bowler is shouting at someone/soemthing after bowling a ball I pressed the run button by mistake and for some reason in the background you could see my batmen crossing and when the bowled was at the start of his run up I gained a run!

Bug number 2:
One of my batsmen on 45, I ran one run. The wicket keeped caught the throw and took the bails off. I was given out. From what I saw he was in by a mile. The replay also showed this. Proof:

 

[Billy Grimwood]

The only bug I've seen so far with my own eyes is that the "out/not out" icons on the third umpire decisions have swapped round for some reason.

 

[Ledme]

is that it? Where do you want me to start with Cricket 2005? If i had a spare few hours i could try and list them for you!

 

[Jdz]

Are you sure his bat is on the ground?

 

[Kevin Pietersen]

can i also add one, the keeper had the ball in his hands and i accidently pressed the run button, my batsman ran and even though the ball had effectivly become dead i was run out

 

[T20]

how is it dead when you are attempting a run?

 

[andrew_nixon]

how is it dead when you are attempting a run?

Exactly.

This would technically be out in real life, unless the umpire had called the end of the over or end of session.

The ball is only technically dead when it's back in the bowlers hand.

A batsman can be run out at any time under the laws, although it's a pretty unsporting team that does it.

 

[Kevin Pietersen]

well what i am saying is when the ball is in the keepers hands most people who play/watch cricket will think its dead, i ran after the ball was in the keepers hands and got run out, its like if a batsman comes to talk with another batsman or flatten the pitch with his bat, the ball would have been dead and you wouldnt expect the fielding side to run the batsman out.

Exactly.

This would technically be out in real life, unless the umpire had called the end of the over or end of session.

The ball is only technically dead when it's back in the bowlers hand.

A batsman can be run out at any time under the laws, although it's a pretty unsporting team that does it.

yes ok in the laws of the game, but you never see it happening, its like a unwritten law imo

 

[andrew_nixon]

yes ok in the laws of the game, but you never see it happening, its like a unwritten law imo

I agree, but it isn't technically a bug in the game if it isn't going against the actual laws.

 

[T20]

well that's the point, since you were going for a run and not just to talk with another batsman/flatten the pitch cpu was right in running you out. it's clearly NOT a bug.

 

[Kevin Pietersen]

yes but surely it should be as realistic as possible and because this isnt realistic it could be interpreted as a bug

also why can you not run on a LBW appeal, if its not out then you can get a leg bye

 

[andrew_nixon]

yes but surely it should be as realistic as possible and because this isnt realistic it could be interpreted as a bug

But if you're setting off for a run, then it is realistic.

 

[Lucky123]

What about when the batsmen run through each other while taking runs

 

[Stephen Bailey]

also why can you not run on a LBW appeal, if its not out then you can get a leg bye

My guess is the cut scene overrides everything else happening at the time.

 

[fanirama]

Don't know if this is a bug or not, the ball physics don't seem to be accurate. Its like the ball is the weight of a bowling ball. It flies easily in the air, but doesn't really bounce. From any height, it literally just drops *plonk* and then rolls along the ground. Not seen the good bounce before a fielder.
Anyone seen proper ball bounce effect ?