Cricket 19 Bug Report Thread - READ FIRST PAGE (Report issues with DLC here)

[Arctic_Wolf]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career mode
Match Type: Test, (Ashes series)
Teams used: England vs Australia in this instance, (otherwise the same glitch happens with other teams).
Ground: Headingley in this instance too but guess what ? (This has also now happened to me at multiple other grounds as well.)
Over Count: N/A

Issue: Options to enforce a follow on or bat again are still randomly missing from the top of the scorecard at the appropriate time for some matches.

Bug description: If you're paying attention & the Xbox "A" button is pressed within the allotted time period to actually enforce the follow on it "might" still happen as expected. However, if you don't wish to enforce the follow on & would like to bat again to gain an even greater lead first, then you're utterly screwed as the game completely removes the option & it still enforces the follow on regardless of user input or preference.

 

[Arctic_Wolf]

To add every stadium in my career mode has a randwick road end even the official stadiums

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career mode, (plus all modes).
Match Type: Test, (however, as with many of these bugs it happens in all match types).
Teams used: England vs Australia in this instance, (the same glitch happens with other teams too).
Ground: Headingley & Old Trafford for this example, but the same issue is experienced at every ground that I can recall. (Photos attached.)
Over Count: N/A

Issue: Further to @jabbathehut 's previous post above, every available ground amazingly has a "Randwick End", & a "Paddington End".

Bug description: NO available grounds ever correctly load their actual end names. It's always these two end names regardless. The commentators also incorrectly state these incorrect end names repeatedly at every venue too.




Seriously, I've alpha/beta tested products with considerably less issues than reported in this thread by itself, let alone countless reports directly to the devs or those reported on other forums/mediums too. This is "obviously" well & truly post release, & over a year on for goodness sake, but still the sheer volume of outstanding bugs remains absolutely horrendous !!

 

[Arctic_Wolf]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Ashes series/Test World Championship, also observed this glitch before in career mode too.
Match Type: Tests
Teams used: England vs Australia in this instance, (although the same glitch happens with other teams too).
Ground: Lord's for this example, but the same issue is experienced at other grounds
Over Count: 56, (this time).

Issue: Opposing AI team magically given extra DRS reviews.

Bug description: Australian AI team elected to bowl first in the first innings & had used up both of their available reviews by the end of the second over. However, in the 56th over the umpire turned down an LBW appeal for the opposing team to then magically be awarded an extra UDRS which resulted in the batsman then being given out.

*SIGH* I don't know, even the game is cheating now lol, (in addition to the glitch where the ball goes straight through the bat on an ideally timed shot to also be given out caught behind)!! Perhaps you could also introduce some of the players sandpapering balls or have bowlers deliberately overstepping in their delivery stride to cause no balls for bet fixing too .

 

[Arctic_Wolf]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Ashes series, World Test Series, ODI World Cup, also observed in career mode.
Match Type: Tests, ODI, First Class, T20, Club.
Teams used: England vs RSA in this instance as an example, (same glitch happens with many other teams, however).
Ground: Edgebaston for this example, but also observed at many other grounds.
Over Count: 02, (this time).

Issue: AI continues to bowl short balls/bouncers above shoulder height even after the umpire has already signalled two for the over in tests or ODI's. The one bouncer limit for T20's is also frequently exceeded as well. (Whereupon the umpire simply gives the bouncer signal again but doesn't actually take the appropriate action when exceeded.)

Bug description: Once again, this is a bug I've observed from time to time in my career modes in particular, but it's another one I've noticed more frequently in the various other modes.

In this instance, for example, after playing a long run of tests I simply wanted a change of pace with some ODI's & initiated another ODI World Cup series. The first match was England vs RSA. AI characters in particular whose strongest skill is the short ball/bouncer do tend to frequently over bowl them, but not exclusively so. Other AI characters whose strongest skill is the yorker also seem to over bowl the short ball for some unknown reason but rarely actually bowl a yorker.

The umpire in turn doesn't award the appropriate penalty & simply continues to signal each additional bouncer bowled. I've just observed another over where the AI bowled FOUR bouncers above shoulder height (as signalled by the umpire).

If a human controlled bowler exceeds the bouncer limit the umpire then correctly calls a no ball immediately respective to the format of the game. (So why is the AI being missed or short balls above shoulder height not being correctly recorded per over?)

Personally, I'm perfectly happy to uppercut/cut or hook these extra short balls over or straight into the boundary rope all day long (especially with the fields the AI continues to set when using the short ball), but it obviously shouldn't be happening in the first place!!!

 

[Arctic_Wolf]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career mode.
Match Type: ALL
Teams used: Dover vs All club teams in the English Kent club league.
Ground: N/A
Over Count: N/A

Issue: ALL of the club teams in the Kent county league are massively imbalanced with left handed fast/medium bowlers.

Bug description: Created another new career on my system for a friend to use, (RHB - opener). EVERY club involved in the Kent county league has an equal mix of left handed & right handed spinners, but they're all grossly imbalanced with left handed fast bowlers. Only ONE team in the entire league has a normal ratio of right arm fast bowlers, otherwise every fast/medium bowler in the league is left handed. Obviously, they're also bowling around the wicket to a right hander the vast majority of the time as well.

(Again, not a problem for me as I know exactly how to deal with them, but for someone new to this game as my friend is in this instance, it's utterly ridiculous.)

Basically, the normal ratio of left handers to right handers has glitched & been completely reversed causing this huge imbalance. (I have three careers of my own that primarily use Notts county, & one is Essex, & this hasn't happened.)

We've tried deleting the career twice & starting it again but the imbalance has been persistent.

EDIT:. Consequently, almost every match played looks like this screenshot from a player's "big wheel", innings after innings, match after match. (Hardly an amazing experience for someone new to the game (or anyone for that matter) if every club level fast/medium bowler they face is left handed & almost every delivery can only be played into the leg side or occasionally straight.) I've tried creating additional careers & swapping to another different county in the English domestic system as well but this issue is now apparently persistent regardless. As such, I'm unable to create a new career with a typical ratio of right handed fast bowlers.

 

[Arctic_Wolf]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career
Match Type: First Class.
Teams used: Nottinghamshire vs Kent in this instance, (same glitch happens with many other teams, however).
Ground: Nottinghamshire stadium, but also observed at many other grounds.
Over Count: 17 onwards.

Issue: Umpire cut scenes signalling a shoulder height delivery repeatedly being displayed for a human or AI spinner bowling good length or fuller deliveries.

Bug description:. Fairly self explanatory really!!! Only ever seen this issue in career mode, however. Can't recall seeing it in an Ashes series or any of the world championships.

 

[Arctic_Wolf]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career
Match Type: Test, (first of this particular career).
Teams used: England vs Pakistan.
Ground: Headingley
Over Count: N/A.

Issue: International debut capping gathering/ceremony cut scene glitched up in to the middle of the crowds in the stadium seats, not on the field.

Bug description:.
Can't seem to recall this issue happening with my own 3 main careers & the debut capping was correctly held down on the field near the boundary each time. These bugs & glitches are now clearly continuing to get worse the longer my careers progress, or with the additional careers being added to the original I began with.

 

[Arctic_Wolf]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career
Match Type: ODI
Teams used: England vs Ireland
Ground: Edgebaston
Over Count: 15

Issue: DRS system not correctly registering the use of a review for human players.

Bug description: I used up the review in the 15th over of an ODI appealing a LBW decision. The umpire's original decision was upheld on umpire's call but I still retained the review which should have been lost. (Previously reported with the AI also retaining a review decision that was also upheld but the AI team also retained their reviews in spite of this.)

 

[wasteyouryouth]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career
Match Type: ODI
Teams used: England vs Ireland
Ground: Edgebaston
Over Count: 15

Issue: DRS system not correctly registering the use of a review for human players.

Bug description: I used up the review in the 15th over of an ODI appealing a LBW decision. The umpire's original decision was upheld on umpire's call but I still retained the review which should have been lost. (Previously reported with the AI also retaining a review decision that was also upheld but the AI team also retained their reviews in spite of this.)

What's the bug here?

 

[Arctic_Wolf]

What's the bug here?

Hi @wasteyouryouth , (& thanks for responding ),

My apologies, I have indeed explained this one somewhat poorly!! I was rushing to post about it before my bowling innings had concluded (rather than waiting which would have been the more prudent course of action & to include all relevant info), but I've now seen this issue crop up several times & kept forgetting to post about it afterwards. Additional info....

I've been experiencing an issue where I've used up my available review(s) but they're not always being registered as spent when they definitely should have been. (Only when bowling, however, can't recall any human player reviews failing to register as spent while actually batting.)

The trigger for this happening.....

If the first appeal I make for a review during a given match is in turn upheld but any aspect specifically comes down to an "umpire's call" (& the review is retained), what then sometimes happens is any subsequent player reviews I make after that won't register as spent even though the review evidence is 100% positive the on field umpire's decision was correct. (I ended up being able to challenge every decision the umpire made during this particular innings (while I was bowling) after the initial review, 3 of these reviews were in the 15th over alone. Each review just wouldn't register as spent when definitely applicable & the option to challenge the umpire's decisions was still being incorrectly offered throughout my bowling spells. (Ultimately, that incorrectly permitted me several extra reviews in this instance that I obviously should never have had. None were actually overturned too & all but 1 of these extras definitely should have resulted in the immediate loss of my review). I was then up to open the batting in the 2nd innings in this instance. However, the review system then functioned normally from there on out & I even ended up having my innings cut short from an overturned LBW appeal. (Poetic justice perhaps!!)

Conversely, if the first player review I've made in any given match (again as a bowler) hasn't come down to an umpire's call & the original decision was upheld without question, as would be expected the game registers that review as spent & I usually don't experience this problem.

Having said that, I've also observed the game successfully registering a used review as spent while bowling earlier in an innings several times, for the game to then magically restore a review in a later bowling spell too. (No obvious reason or pattern as to why that one happens, it just does.)

To be clear, none of these issues are persistent in every single match, but they are intermittently & randomly recurrent.

I can only recall this problem happening (for human reviews) in the career mode as well. I can't ever recall it happening throughout a number of Ashes series I've played, or any of the various world championships, (including both the men's & women's Ashes series/world championships that were completed purely for sh**s & giggles for the Xbox achievements ).

Additionally, I can't ever recall this happening with the original career I created either (but that is specifically based on a specialist batsman & this problem is definitely related to the bowling aspects alone). It's only been a problem whilst using either of the two additional career modes I created later, (one as an all-rounder & the other as a batting all-rounder, & both are leg spinners if that also helps anyone narrow down a potential cause too).

Again, apologies I didn't make this clearer in my original post & I can back edit it to include this additional info if you wish? (Although, I won't edit it now until I've heard back from you again.) I usually exercise a degree of care when entering any of these bug reports as I know it can end up causing additional headaches for all involved if they're not properly explained etc., My bad in this instance, I was rushing, had other things going on too, & I should have included a clearer explanation the first time.

 

[wasteyouryouth]

Hi @wasteyouryouth , (& thanks for responding ),

My apologies, I have indeed explained this one somewhat poorly!! I was rushing to post about it before my bowling innings had concluded (rather than waiting which would have been the more prudent course of action & to include all relevant info), but I've now seen this issue crop up several times & kept forgetting to post about it afterwards. Additional info....

I've been experiencing an issue where I've used up my available review(s) but they're not always being registered as spent when they definitely should have been. (Only when bowling, however, can't recall any human player reviews failing to register as spent while actually batting.)

The trigger for this happening.....

If the first appeal I make for a review during a given match is in turn upheld but any aspect specifically comes down to an "umpire's call" (& the review is retained), what then sometimes happens is any subsequent player reviews I make after that won't register as spent even though the review evidence is 100% positive the on field umpire's decision was correct. (I ended up being able to challenge every decision the umpire made during this particular innings (while I was bowling) after the initial review, 3 of these reviews were in the 15th over alone. Each review just wouldn't register as spent when definitely applicable & the option to challenge the umpire's decisions was still being incorrectly offered throughout my bowling spells. (Ultimately, that incorrectly permitted me several extra reviews in this instance that I obviously should never have had. None were actually overturned too & all but 1 of these extras definitely should have resulted in the immediate loss of my review). I was then up to open the batting in the 2nd innings in this instance. However, the review system then functioned normally from there on out & I even ended up having my innings cut short from an overturned LBW appeal. (Poetic justice perhaps!!)

Conversely, if the first player review I've made in any given match (again as a bowler) hasn't come down to an umpire's call & the original decision was upheld without question, as would be expected the game registers that review as spent & I usually don't experience this problem.

Having said that, I've also observed the game successfully registering a used review as spent while bowling earlier in an innings several times, for the game to then magically restore a review in a later bowling spell too. (No obvious reason or pattern as to why that one happens, it just does.)

To be clear, none of these issues are persistent in every single match, but they are intermittently & randomly recurrent.

I can only recall this problem happening (for human reviews) in the career mode as well. I can't ever recall it happening throughout a number of Ashes series I've played, or any of the various world championships, (including both the men's & women's Ashes series/world championships that were completed purely for sh**s & giggles for the Xbox achievements ).

Additionally, I can't ever recall this happening with the original career I created either (but that is specifically based on a specialist batsman & this problem is definitely related to the bowling aspects alone). It's only been a problem whilst using either of the two additional career modes I created later, (one as an all-rounder & the other as a batting all-rounder, & both are leg spinners if that also helps anyone narrow down a potential cause too).

Again, apologies I didn't make this clearer in my original post & I can back edit it to include this additional info if you wish? (Although, I won't edit it now until I've heard back from you again.) I usually exercise a degree of care when entering any of these bug reports as I know it can end up causing additional headaches for all involved if they're not properly explained etc., My bad in this instance, I was rushing, had other things going on too, & I should have included a clearer explanation the first time.

So, in some game modes, when you retain a review on umpire's call, you retain subsequent reviews whether or not it is umpire's call?

 

[Arctic_Wolf]

So, in some game modes, when you retain a review on umpire's call, you retain subsequent reviews whether or not it is umpire's call?

Precisely, but only when bowling for some games in career mode. (Can't recall it ever happening when playing as a team & therein controlling all bowlers in an Ashes series or one of the various world championships.)

 

[Arctic_Wolf]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career.
Match Type: Test / First class. (Seems to be confined to the longer format as far as I can tell, although obviously massive scores aren't all that common in the shorter formats. )
Teams used: India vs England, (this was just one instance, however).
Ground: Many.
Over Count: Random.

Issue: If achieving a very high scoring innings & especially when hitting a large number of boundaries/sixes early on, the "Big Wheel" can often randomly cease to plot any singles, two's or three's scored later on in the innings. (It still continues to plot any additional boundaries/sixes normally, however.)

Bug description: After monitoring this issue for a while now I had suspected that runs were ceasing to be plotted on the "Big Wheel" at a certain point in a number of my higher scoring innings. (I took an early opportunity in one match to hit a large number of boundaries all around the field earlier on whilst the field was still set in close & more aggressively. Obviously, after a while the field typically spreads becoming progressively more defensive to cut off said boundaries. At which point, also obviously, boundaries are typically reduced but the quick singles, two's & three's in turn become easier with the field set that much more defensively.) When this is happening, I've noticed in several matches that these easy singles/two's/three's simply cease to be plotted on the big wheel any longer. (I spent approx 15-20 overs towards the end of my innings just deliberately knocking as many quick runs as I possibly could specifically into the areas of the field where absolutely no runs had been scored at all & as I'd suspected these runs just ceased to be plotted on the big wheel period. The odd boundary I managed to get through or more obviously a few sixes I risked still continued to be plotted on the big wheel though. For whatever reason, the game just seems to glitch & stops plotting the runs that actually have to be ran.)

As mentioned, I had a reasonable degree of certainty that this glitch had been ongoing for some time as I frequently check my batting stats/analysis during matches, but I can now definitively confirm this particular glitch is certainly ongoing from this particular innings alone.

 

[wasteyouryouth]

Platform: Xbox One X
Game Version: v 0.1.1292
Game Mode: Career.
Match Type: Test / First class. (Seems to be confined to the longer format as far as I can tell, although obviously massive scores aren't all that common in the shorter formats. )
Teams used: India vs England, (this was just one instance, however).
Ground: Many.
Over Count: Random.

Issue: If achieving a very high scoring innings & especially when hitting a large number of boundaries/sixes early on, the "Big Wheel" can often randomly cease to plot any singles, two's or three's scored later on in the innings. (It still continues to plot any additional boundaries/sixes normally, however.)

Bug description: After monitoring this issue for a while now I had suspected that runs were ceasing to be plotted on the "Big Wheel" at a certain point in a number of my higher scoring innings. (I took an early opportunity in one match to hit a large number of boundaries all around the field earlier on whilst the field was still set in close & more aggressively. Obviously, after a while the field typically spreads becoming progressively more defensive to cut off said boundaries. At which point, also obviously, boundaries are typically reduced but the quick singles, two's & three's in turn become easier with the field set that much more defensively.) When this is happening, I've noticed in several matches that these easy singles/two's/three's simply cease to be plotted on the big wheel any longer. (I spent approx 15-20 overs towards the end of my innings just deliberately knocking as many quick runs as I possibly could specifically into the areas of the field where absolutely no runs had been scored at all & as I'd suspected these runs just ceased to be plotted on the big wheel period. The odd boundary I managed to get through or more obviously a few sixes I risked still continued to be plotted on the big wheel though. For whatever reason, the game just seems to glitch & stops plotting the runs that actually have to be ran.)

As mentioned, I had a reasonable degree of certainty that this glitch had been ongoing for some time as I frequently check my batting stats/analysis during matches, but I can now definitively confirm this particular glitch is certainly ongoing from this particular innings alone.

I noticed something 'off' when I scored my epic Joe Denly double hundred. I actually assumed that because of the probability of hitting the same shot more than once, and the lines being quite thick, that it was just overwriting (so one shot would appear on top of the other). Possible that it does cease to plot them though.

 

[Pruthul Gajjar]

Platform: PC
Game Version: (V13.00)
Game Mode: Online and offline both.
Match Type: any
Teams used:. Any
Ground: any
Over Count: any
Issue (one line description): DRS LBW

Bug description (detail):Umpire doesn't Overturn his decision from"NOT OUT" to "OUT" if even the ball is hitting to Middle stump and pitching is outside the Off stump.Also Umpires Doesn't overturn his decision from "OUT" to "NOT OUT" if the pitching is outside the leg stump.