Summary of issues/anomalies thread

[TripleM]

The issues/anomalies thread is start to get quite long, so I thought it would be helpful for people who wanted to report issues to be able to see whether their issue has been previously reported.

Here is a summary of most (have left out a few that weren't clearly stated / are feature requests rather than issues / etc) things that have been discussed in that thread, under a rough category system (though some apply under multiple categories).

Disclaimer: this is a list of reported issues/bugs, not necessarily a list of actual bugs.

Appearance

1. Automatic replays often don't show what you would expect to see - eg missing the ball going over the boundary for 4 or 6, concentrating on batsman's strike rather than a catch, or showing bails falling off in slow motion rather than the batsman being beaten and bowled.
2. Difficult to spot fielders in the outfield. [Confirmed to be patched by having position names appearing as text over their heads.]
3. Difficult to judge whether a run is on or not after a shot due to the way the camera reacts slowly.
4. Bowlers/fielders run through the umpire.
5. Temperatures of over 200 degrees celsius have been reported.
6. HUD for batsmen running between wickets can show the batsmen flipped and running towards the wrong ends.
7. Several close runouts/stumpings are given out directly without going to the third umpire.
8. BARS for catches/LBWs are only showing if reviewed - never available for any other close calls.
9. Red circle around ball cannot be turned off. [Confirmed - to be patched at a later stage.]
10. Scorecards have innings listed in the wrong order.
11. Occasionally various letters can disappear from scoreboards, team lists, etc. Fixed on rebooting.
12. Big Eye once showed lots of unusual lines rather than just the path of the ball.
13. Players can get stuck in position/glitch for up to 10/20 seconds, often concluding with getting run out.
14. 4-day match scoreboard said 'match tied' at the end of a session, despite the game continuing afterwards.
15. Bails can sometimes fly away a long distance up the pitch
16. Frame rate may decrease severely after playing 6 or 7 games continuously.
17. Square-leg umpire also raises his hand when the batsman is viewing the field.
18. Ball shown actually inside the middle of the bat.
19. Ball passes directly through the bowler after he drops a catch.
20. Players do not react to getting hit by the ball.
21. Replay shows ball travelling straight through middle of bat.
22. After returning from lunch, scores were reset at 0/0 until an over had passed, when the score corrected itself.
23. Same umpire is always shown for every cutscene despite setting two different umpires.

AI

1. AI hits too many reverse sweeps [Confirmed to be the go-to shot for a bad delivery, and will be patched at a later stage.]
2. AI bowls too straight / on the leg-side.
3. AI sets very unusual fields, defensive when a batting team is under pressure and vice versa, often with unnecessary very close fielders.
4. AI gets run out too frequently, including occasionally diving too early and making no attempt to get into crease.
5. AI sometimes doesn't take singles when ball goes to fielders near the boundary.
6. AI struggles to score runs against human bowling, but scores easily in simulated bowling.

Reviews / Umpire's decisions / Wickets

1. Reviewing for an LBW after being hit on the thigh pad only checked for an edge, not LBW.
2. Decisions are sometimes overturned despite BARS returning a verdict of umpires call.
3. Ball getting caught off the glove was given not out even with a review.
4. Ball getting caught off the bat was given not out; review just showed one replay and didn't check for a hot spot or BARS.
5. Decision to review was requested after the umpire chose to go upstairs, but before the 3rd umpire verdict occurred.
6. Ball slowly rolled into stumps after hitting the batsman's pads, dislodging bails, but recorded as a dot ball.
7. A wide was given as well as a wicket when someone was bowled around their legs.
8. A run out was given as soon as a player left the crease after bails had already been dislodged.
9. Wicket was awarded on a free hit after the bowler first pulled out of his runup.
10. Both LBW and caught have been given out on a free hit.
11. Umpire doesn't signal wide if you appeal.
12. Given out stumped when replays clearly show batsman in crease.

Fielding

1. Fielders are lightning fast and barely ever drop a catch, making it almost impossible to pick up quick singles (especially due to bowler's rapid fielding).
2. Direct hits are too easy and happen nearly every throw, even from a long distance away.
3. Keeper/bowler take off the bails / throw down the stumps repeatedly when unnecessary.
4. Field settings are not saved and revert regularly [Unlikely to be a bug - caused when batsman, bowler, or over/around wicket setting changes.]
5. Fielders slide too much. [Confirmed to be somethings Ross doesn't like, but not much more.]
6. 4 runs are not given when a fielder touches the rope while tapping the ball back in.
7. After running a single and having overthrows going for 4, only 4 runs are awarded.
8. Bowling very fast can still result in the ball bouncing twice before it reaches the keeper, with no option of moving the keeper closer.
9. Ball sometimes warps from keeper attempting runout to bowler attempting runout in a fraction of a second.
10. Without sprinting, batsman take too long to get back in crease, and are often run out when all they had to do was ground their bat. This also happens regularly when players are backing up out of their crease, even after the O (PS3) button is hit, or getting run out when getting up after diving, diving too early, or leave crease after initially getting there safely. [Confirmed to be improved in upcoming patch.]
11. Fielders can push the batsman out of the crease, then run him out.
12. Fielders suddenly appears in a new position just after the bowler releases the ball.
13. Slips don't come into play due to agility of keeper and lack of thick edges.
14. Close catchers don't come into play due to lack of bat-pads.

Commentary

1. Commentator remarks on catches being dropped over the boundary.
2. Occasional stutter in the commentary every few minutes.
3. Commentators refer to a 16 year old out for 0 on debut as a huge wicket.
4. Commentator says 'we now look forward to the innings reply' after the second innings of a one dayer
5. Commentary stopped after making a change to the field.
6. Commentary stopped after a catch was taken and badge awarded (and then not given out)
7. Commentator says "They will be happy with that win" for a draw.
8. Commentator acts like a ball was hit directly for 4 when overthrows add up to 4.

Career mode

1. Roles are incorrectly linked, with batsmen bowling all the time and bowlers batting well. [Confirmed to be fixed in upcoming patch.]
2. Bowlers fatigue too fast and lose 30km/h in speeds within a few overs. This isn't regained after a break in play.
3. Captains choose not to let you bowl despite having extremely good figures.
4. Extremely easy to get wickets as a bowler, compared with high difficulty of batting
5. Scorecard once showed blank first innings for your turn when opposition is batting second in the first innings.
6. Other players' stats don't change from game to game, only your player.
7. First year of career ends still with games to play. [Confirmed to be fixed in the first patch.]
8. Trophy received for bouncer when you bowled the previous over and the AI is bowling.
9. Bowler repeatedly switches from over the wicket to around the wicket.
10. XP received for two sweeps in an over, when the AI played the first one.
11. Cannot view the confidence meter.

General

1. Game sometimes freezes between innings.
2. Changing to custom field results in a black screen after game was reloaded.
3. In a default 6-league T20 competition with a bowling bonus point of 1 with min/max 10 wickets, bonus points were received despite getting bowled out and losing.
4. Cannot save the game and continue playing in case of powercuts / crashes [Confirmed to be a deliberate decision.]
5. Default sides + kits for casual T20/ODI selects test match by default.
6. After completing the first innings of an ODI the same team were put into bat to chase their own score, until the game was simulated.
7. Game freezes attempting to save.
8. Some controls, most importantly spin controls, in the manual are wrong. [Confirmed - corrected pages here: http://www.planetcricket.org/forums...um/manual-corrections-88997.html#post2733415] ]
9. 12th man credited with having played a game in stats.
   [/B]

Online

1. Game occasionally crashes to a black screen.
2. Short flashes of black screen just after playing a shot. [Confirmed as a sound bug - to be fixed in the first patch.]
3. Not enough time to change lineup before a match.
4. Likely due to some lag, ball hit along the ground is picked up and then given out as caught. Similarly issues are being caught behind when it bounced after hitting the bat, or umpire signalling a bouncer for a full length delivery.
5. Loading sometimes gets stuck trying to resume saved match.
6. Bowler occasionally warps when running in to bowl.
7. Pressing the run button immediately after a hit is not registered; must be pressed another time.
8. Once the umpire stopped counting balls until a wicket fell, resulting in 14nb.
9. Holding the view field button often does not work in time after a field change as the bowler runs in immediately.
10. Ball marker often not visible when lagging during the delivery.

 

[barmyarmy]

That's a fantastic post so thanks for doing it. We've been looking for ways to make the bugs thread more useful for Big Ant and this is a big help.

----------

Incidentally this is my favourite bug. Must try with the computer batting...

Fielders can push the batsman out of the crease, then run him out.

 

[zombieian]

Good grief. I might very well cancel my order!!

 

[ashwinpai]

Good grief. I might very well cancel my order!!

Don't Cancel,
It's still by far the best cricket game out there.

 

[Acid Burn]

Great Work TripleM !!!!

Now just to keep this up to date , and all will have an easy reference point to work from.

Will defnitly make BigAntStudio`s life a little easier as well , trying to keep up with all the playing aka Stress-testing of the game.

 

[zombieian]

Don't Cancel,
It's still by far the best cricket game out there.

I was joking, hence the .

 

[Gurjot95]

This list is nightmare for developers to fix even half of them. That said, the game is lot better than what the list may appear to as most of them are minor issues.

 

[Acid Burn]

@Friend863

This list is never ever going to be patched top to bottom , I`m pretty sure about that , as some of the problems might only be rectified in the next version because of programming issues etc. etc.

But it sure helps everyone see all the stuff in one place , even if 95% of them is not game-breakers . You know us cricketers are very nit-picky and will allways try and see improvement . Thats the nature of the human being.

But I understand , looking from the outside in , this list sure looks to the newcomer as a helluvah bugger-up of a game ,which it obviously is not.

 

[sami ullah khan]

None of the above is a game breaking bug. Just little nuances that can ruin the experience little bit. As Ross said, a patch is already done and will be user tested by Matt on Friday.

 

[St0ney]

WOW thats a lot of bugs in only 1 week of play.
Was the game tested Ross.

 

[Lord Sajjad]

I think you forgot to write that the fielders are hard to spot.

 

[Kiko_97]

How many of these am I likely to see come Thurs/Fri when I get this game and never leave my room?

 

[cricket_online]

@TripleM,
Can you add the following for AI...

6. AI batting is too fragile against human/user bowling. AI tends to score well when you simulate innings (or in career mode) but in matches vs AI, the AI hardly puts up a decent total for games which are longer than T20. In a 50 over match or in 4 day/Tests you can easily bundle AI for less than 200, which shouldn't be the case.

 

[_Sam_]

How many of these am I likely to see come Thurs/Fri when I get this game and never leave my room?

All of them still by then .

 

[Kiko_97]

Doubt i'll experience them all. But which are the more common occuring?