Cricket 2004 bugs list

[squiz]

Originally posted by Lanokota
So this means even if I play the match without saving, eventually I can't resume after an over is bowled anyway. On the bloody final. That is hours of time lost. Anyone know how to contact EA Sports? I'm going to crap them out and demand they fix my savegame (and the game)

That can be fixed using the Save Game Tweak. Change team, load the game, change bowler to sum1 who hasn't completed their full overs, save the game, change team again then it should work. I think that's what your talkin bout

 

[sachin]

hwhen i was playing today i pressed the run button to go for a second run but changed my mind a second later.one of the batsman just stayed i his crease but the other ran all the way down to the other end.and m the bowler whipped off the bails at the end where bothe batsman were and appealed. it wasn't gven out.is that some sort of bug?sorry if someones already mentioned this.it was real funny.i think that is a pretty good bug.lol

 

[Lanokota]

***check third post, this thing won't let me edit a file back into it***

This was the field setting I wanted to post.
The trick to getting the suicidal runouts and also the "dancing slip cathey just can't tch" is to bowl to a right handed batsman on his right hand side and to a left hand batsman on his left hand side

Sometimes the ball slips through for 4, or there is an ocassional single run...but you'll get them out below 100 every single time. If not for the wickets, then for the runs seem to get.

 

[Lanokota]

Argh...the field is not right...they are'nt edging the ball anymore. Stupid buggy game changed my field!...nooo...and I can't get it back to how it was...

Try tweaking the field a bit. As it is in the screenshot it works still, but the AI don't get out for low scores under 50 anymore it seems...damn.

 

[Lanokota]

screenshot

 

[groobz]

what kind of field is that? any shot played on the onside will pretty much go to the boundry!

 

[squiz]

and any shot down to mid off will be a run out

 

[madmattg]

India Bug

After last nights tri nation Aust vs India I think the fact that India can hit the ball is a Bug.

What a white wash...............

Smashed to death.

 

[Lanokota]

The point of the field setting is to bowl to the right handed batsman's right and the other way around for left handers so...the AI batsman does not understand that he can actually move to hit the ball where there are no fielders.

So...he hits in the fielder loaded place all the time. Affective bug!!! bug because the stupidity is so bad that the AI can't get any runs. Oh there are some 4's and maybe a 6 or two. But nothing compared to a decent score with all the runouts they get

 

[schase]

Would the fact that the game crashes every time I reach 23 overs count as a bug? Well, that is, when I reach 23 overs, and then get to the inter-over menu, I can select every option (statistics, save, etc.) EXCEPT continue! If I select continue, it makes the BOING noise, but the menu just stays there and I can't continue. I noticed this the first day I got the game (i.e. beginning of December), and have been TRYING to get help from EA Sports ever since. Eventually, EA's "tech support" sent me to this site to see if I could get help. Any ideas?

 

[Ste]

Does this happen in both tests and ODIs? And there is absolutly no pattern to it happening, just every time after 23 overs, no matter what teams you choose etc? What happens if you use autoplay and keep going forward 5 overs until you reach after 23 overs, does the game crash or let you keep playing, or perhaps you could get hold of a save game with a match after 23 overs and see what happens then.

Ste

 

[SteveG]

Eventually, EA's "tech support" sent me to this site to see if I could get help. Any ideas?

Anyone else find that pathetic? Apparently, EA Support know diddley squat about their own game...just another reason to not buy EA games.

 

[sagar]

Yea, I am having the same problem *save bug* If you are batting and the save bug occurs, go to the bowling stats for the CPU and 9/10 times it will be trying to use a bowler that has already used their 10 overs *Only in ODI's* Hopefully someone can create a patch (or EA Sports) that will stop the CPU from choosing a bowler that has already used their 10 overs.

 

[squiz]

sagar try searching the SavTweak thread for the resolution to your problem.

 

[schase]

Ste, you are correct, there is no specific pattern to this. It happens only in ODIs, but regardless of what teams I choose, etc. Yes, every time at 23 overs, regarldess of what competition I am playing. Hmmm, interesting point there sagar. This has never happened to me in a test match. What's up with EA? In Cricket 2002, bowlers in ODIs almost ALWAYS bowled more than 10 overs, and there was no crashing there! SteveG, I DO think it is rather pathetic that EA can't find a solution to their own games, especially after more than 2 months! Okay, squiz, excuse my utter ignorance here, but whatsa "SavTweak thread"? I'm pretty new to these forums etc. (i.e. this is the first time I have ever posted anything on a forum for help!).