Cricket 22 General Discussion thread (Use bug report thread for issues/bugs/crashes | Patch notes in first post)

[Arctic_Wolf]

I've checked in to find out where this landed, as your post was passed on, and the note about those shots given to the team working on that aspect of the game. The feedback I got back was that there wasn't enough to go on to work out what was being referenced, so other items where we had clearer information got focus instead.

Possibly took too long to go back to you to try and seek more detail, but a post that says "x is broken" is often really hard to make right. Even if you might think a problem stares at you in the face, people play the game differently, different control schemes, different sliders, different approaches to batting, etc. That's one reason the bug report thread template asks for an example, rather than "any", as even if you might not think it's a factor, it's a starting point.

That's not saying there's no problem - just that from the posts I have, it wasn't enough info for the people working on the batting aspects to work out what you're referring to. Maybe you might think that's a gotcha - "ah, they don't even know what they broke" - sure - but it's just as likely that if we had a video demonstrating it - knowing your inputs to what sort of delivery - then we might go "oh, that's this" and be able to sort it.

We know a lot of people have issues with batting, and we're in general working to find improvements, but as we couldn't work out what you were referring to in your post, that fell down the list. I believe there's a few batting shot improvements that will go into tomorrow's patch as a result of that, and while people keep bringing it up, it'll be something that continues to get further work.

This goes on to show the people developing the game don't play this game at all, such a basic obvious issue, late cut getting triggered when playing square cut is a very disturbing thing for the people who care about cricket, one the best shots the square cut is missing since many many days.

Thanks at least for the response @MattW . That much is indeed appreciated.

The absolutely infuriating thing is, is this broken back foot square drive / back foot late cut glitch has now existed in EVERY mode of the game for the past 6 weeks & it's absolutely IMPOSSIBLE to miss. And I do honestly mean impossible!!

It doesn't matter what mode, what ground, what team, what match type, which individual player, which individual batting style, the broken shot is present regardless. (Ergo, anyone entering "any" in a bug report is irrelevant as any is actually 100% accurate.)

Countless users have been constantly complaining about this glitch since it was introduced weeks ago & you're telling me nobody at BA can see this at all? (If they can't then honestly what hope is there?)

It's simple, & if you'd like a specific example load the main Ashes tour, Australia vs England. (I'm Xbox Series X but users on ALL platforms have mentioned this same glitch/broken shot, it's not platform specific, it's universal.)

Have your devs attempt to play a back foot drive/punch through POINT, square of the wicket, & see what they get instead!!

You WON'T get a back foot square drive as the shot is now broken but it was working just fine until approx 6 weeks ago. What we have been getting instead for weeks now is the game glitching to a ridiculous back foot late cut that would ordinarily run the ball down to the third man.

However, because of this glitch this results in the ball weakly pinging off the bat & going straight & directly to backward point/gully every single time.

Load a new career mode & repeat. Attempt a back foot square drive through point & it WILL glitch to this broken back foot late cut. Again, it's impossible to miss. (I've now recreated this with EVERY choice of specialty, specialist batter, batting all-rounder, all-rounder, bowling all-rounder, bowler, with EVERY batting style. And still BA can't see it?)

It's unmistakable, present in every mode, match type, player, style, pitch, dynamic weather condition, & it can't possibly be missed.

 

[sashu_91]

Thanks at least for the response @MattW . That much is indeed appreciated.

The absolutely infuriating thing is, is this broken back foot square drive / back foot late cut glitch has now existed in EVERY mode of the game for the past 6 weeks & it's absolutely IMPOSSIBLE to miss. And I do honestly mean impossible!!

It doesn't matter what mode, what ground, what team, what match type, which individual player, which individual batting style, the broken shot is present regardless. (Ergo, anyone entering "any" in a bug report is irrelevant as any is actually 100% accurate.)

Countless users have been constantly complaining about this glitch since it was introduced weeks ago & you're telling me nobody at BA can see this at all? (If they can't then honestly what hope is there?)

It's simple, & if you'd like a specific example load the main Ashes tour, Australia vs England. (I'm Xbox Series X but users on ALL platforms have mentioned this same glitch/broken shot, it's not platform specific, it's universal.)

Have your devs attempt to play a back foot drive/punch through POINT, square of the wicket, & see what they get instead!!

You WON'T get a back foot square drive as the shot is now broken but it was working just fine until approx 6 weeks ago. What we have been getting instead for weeks now is the game glitching to a ridiculous back foot late cut that would ordinarily run the ball down to the third man.

However, because of this glitch this results in the ball weakly pinging off the bat & going straight & directly to backward point/gully every single time.

Load a new career mode & repeat. Attempt a back foot square drive through point & it WILL glitch to this broken back foot late cut. Again, it's impossible to miss. (I've now recreated this with EVERY choice of specialty, specialist batter, batting all-rounder, all-rounder, bowling all-rounder, bowler, with EVERY batting style. And still BA can't see it?)

It's unmistakable, un-missable, present in every mode, match type, player, style, pitch, dynamic weather condition, & it can't possibly be missed.

I doubt it is getting fixed tomorrow, @MattW Why is lofting so easy then timing grounded shots, so easy to time these lofted shots after you set yourself, there is no fun playing as you know you will hit sixes at close to hardest, why AI doesn't vary the pace when balling, they never deceive with change of pace and you keep connecting sixes, what is the use of legend AI then?

 

[Ragz]

Everytime a new patch is released, the first thing I do is load up a t20 game and bat first just to check if the back foot cut against pacers bug is fixed.

You can very easily really reproduce it in the very first over or at max second over itself using any batting style - a short wide ball and the user input is left stick around 12 o clock, right stick around 9 o clock (on fixed close cam).
Output is always a weak late cut irrespective of whether it is a normal shot, aggressive grounded shot or aerial shot and all 3 parameters are good to ideal.

After reading Matts response that the team is not able to reproduce it, I'm super disappointed because all these weeks I was hoping this issue was being worked on as a top priority but now it looks like this bug relating to a fundamental & one of my favourite stroke in batting is here to stay.

 

[cricboi]

I've noticed a small glitch with the standard controls and wondering if anyone else is struggling with it. I should note, it only happens against spin. When playing an offside front foot defensive shot pointing to 3 o'clock it will instead play a front foot defensive shot to the leg side (10 o'clock). It usually just leads to a play in miss, because most balls I try it on end of missing the wickets, but it has caught me out a few times.

 

[Arctic_Wolf]

I doubt it is getting fixed tomorrow, @MattW Why is lofting so easy then timing grounded shots, so easy to time these lofted shots after you set yourself, there is no fun playing as you know you will hit sixes at close to hardest, why AI doesn't vary the pace when balling, they never deceive with change of pace and you keep connecting sixes, what is the use of legend AI then?

I doubt it'll be fixed tomorrow either & not only can BA apparently not see a painfully obvious glitch. It actually seems more accurate that they haven't actually bothered to even look for it despite the bug reports & other accurate descriptions of how to recreate this glitch because it is truly impossible to miss.

@MattW , I'll also add that I mainly use the standard controls (or what have now been labelled "arcade") should that make any difference. However, I've also recreated it with the pro controls as well & I've read posts under this thread complaining of the same broken shot/glitch from users known to use pro controls. Again, it's universal there too.

It's also specifically off fast bowlers. (The lofted back foot late cut (that everyone hates & dreads the AI playing) is also broken off a spin bowler too as it won't go above head height but sod that one for now. For the love of God PLEASE fix this broken back foot square drive.)

Everytime a new patch is released, the first thing I do is load up a t20 game and bat first just to check if the back foot cut against pacers bug is fixed.

You can very easily really reproduce it in the very first over or at max second over itself using any batting style - a short wide ball and the user input is left stick around 12 o clock, right stick around 9 o clock (on fixed close cam).
Output is always a weak late cut irrespective of whether it is a normal shot, aggressive grounded shot or aerial shot and all 3 parameters are good to ideal.

After reading Matts response that the team is not able to reproduce it, I'm super disappointed because all these weeks I was hoping this issue was being worked on as a top priority but now it looks like this bug relating to a fundamental & one of my favourite stroke in batting is here to stay.

That's exactly what I do, & I also load a brand new Ashes series match to confirm it's still there with each new patch as well, & each time end up bitterly disappointed & binning the game for another week because it hasn't been fixed. I'd hoped they were working on it too but couldn't find the cause, only to now find out they never even bothered to look despite it being impossible to miss if just one competent individual had actually bothered to check it out.

As noted above, I've gone on to reliably recreate it under nearly every possible condition because it's so damn annoying & frustrating. Thanks for confirming what we're seeing now at least !!

However, all one needs to do is read back through this thread over the past 6 weeks & there's countless complaints about this broken shot, descriptions of exactly how it's happening & the effect it ultimately has. Still they haven't bothered to even look.

Honestly, what more can be said to that after the state of C22 the day it was released & everything that's happened with C22 since release?

 

[sashu_91]

• 
  

• I doubt it'll be fixed tomorrow either & not only can BA apparently not see a painfully obvious glitch. It actually seems more accurate that they haven't actually bothered to even look for it despite the bug reports & other accurate descriptions of how to recreate this glitch because it is truly impossible to miss.
  
  @MattW , I'll also add that I mainly use the standard controls (or what have now been labelled "arcade") should that make any difference. However, I've also recreated it with the pro controls as well & I've read posts under this thread complaining of the same broken shot/glitch from users known to use pro controls. Again, it's universal there too.
  
  It's also specifically off fast bowlers. (The lofted back foot late cut (that everyone hates & dreads the AI playing) is also broken off a spin bowler too as it won't go above head height but sod that one for now. For the love of God PLEASE fix this broken back foot square drive.)
  
  
  
  That's exactly what I do, & I also load a brand new Ashes series match to confirm it's still there with each new patch as well, & each time end up bitterly disappointed & binning the game for another week because it hasn't been fixed. I'd hoped they were working on it too but couldn't find the cause, only to now find out they never even bothered to look despite it being impossible to miss if just one competent individual had actually bothered to check it out.
  
  As noted above, I've gone on to reliably recreate it under nearly every possible condition because it's so damn annoying & frustrating. Thanks for confirming what we're seeing now at least !!
  
  However, all one needs to do is read back through this thread over the past 6 weeks & there's countless complaints about this broken shot, descriptions of exactly how it's happening & the effect it ultimately has. Still they haven't bothered to even look.
  
  Honestly, what more can be said to that after the state of C22 the day it was released & everything that's happened with C22 since release?

  The thing is we need testers/ppl close to them who care about batting, unfortunately people close to BA team is all about making AI bat sensibily, make AI play variety of shots , variety of AI dismissals etc, as all they do is bowl. Lol they are still waiting for enough evidence for that late cut bug, what is the role of dev director then, letting there employees work randomly on stuff where there is enough evidence.

 

[Arctic_Wolf]

I've noticed a small glitch with the pro controls and wondering if anyone else is struggling with it. I should note, it only happens against spin. When playing an offside front foot defensive shot pointing to 3 o'clock it will instead play a front foot defensive shot to the leg side (10 o'clock). It usually just leads to a play in miss, because most balls I try it on end of missing the wickets, but it has caught me out a few times.

I'd say your issue is you're simply trying to defend outside of the scope/range of a normal front foot defence, or what the actual shot selection itself will allow so it's defaulting to the leg side defence animation & you miss altogether. (C19 also did this if you defended the wrong line completely.)

Otherwise, why are you actually attempting a front foot defence that square of the wicket ?

It's asking for an edge even if you do make contact with the bat face technically being that open. (And yes, C22 can pick up on inappropriate shot angle selection or footwork to the actual delivery, especially on the harder difficulty levels or if the bowling quality slider is drastically increased. (Edges will ensue & not just from poor/bad timing alone .))

Try to defend in the typical 11 (mid on) to 1 O'clock (mid off) "V", or maybe a defence as far round as the 2 O'clock off the right delivery (extra cover/cover) at the most if you're trying to nudge a defence into the offside for a cheeky single. (Works infrequently as even a sluggish AI spinner will suddenly pounce upon the ball & accurately throwdown the stumps in a split second.). 3 O'clock for a forward defence is a tad too square.

Any change/improvement?

If you are trying to do it to run cheeky singles off a spinner & provided there are no short fielders in play (short leg, silly point etc.), then dribble the ball straight back to the bowler & run the instant you make contact. (The AI reacts much more slowly to this than a ball directly nudged into the offside .)

 

[cricboi]

Thanks for that explanation, I think that makes the most sense. I had a feeling maybe it was me just chasing the ball too far outside and over-extending from 2 to 3. Now that I think about it, I sort of like that it can end up with me getting bowled because I enjoy the idea of losing a wicket for such a stupid mistake

 

[Arctic_Wolf]

Thanks for that explanation, I think that makes the most sense. I had a feeling maybe it was me just chasing the ball too far outside and over-extending from 2 to 3. Now that I think about it, I sort of like that it can end up with me getting bowled because I enjoy the idea of losing a wicket for such a stupid mistake

LOLOL .

There are countless other stupid mistakes you could make to get yourself out that would at least be more fun hehe .

 

[andrew56]

Has anyone had alot of bowleds in the last patch

 

[Abcd9994]

Hi @MattW request you to please take a look at this video (just 1:20 mins), have tried to explain the issue with back foot shots through the off side (cover point region):

Basically when user tries to hit the ball through cover-point region (standard attacking shots) against pace bowler, I think it would either be a cut shot or a back foot drive/punch. Now the issue that we face is 2 fold:

a. Many times the computer simply executes the guide to third man shot instead of the cut or the drive/punch. I think this is a bug because we are trying to place the ball in front of square whereas the batsman plays the ball behind square, even when we have 3 greens on our input.

b. Sometimes the computer does play the back foot punch/drive shot. When this happens however, the ball simply goes straight to the standard cover position- this issue was earlier present in both front foot and back foot play but was resolved for front foot play some patches ago, I am thinking now, that maybe it was never resolved for the back foot play.

In addition, I personally feel the backfoot cut shot is underpowered compared to drives especially straight drives- even with 3 greens on my input it is a bit difficult to hit the ball far when playing a backfoot cut shot. Now I am not sure if it's the front foot drives that need to be toned down or if it's the backfoot cut that needs to be powered up. I also don't feel like this is the burning issue, the primary concern is the first 2 points I think.

In Cricket 19, obviously (b) was not an issue- it worked perfectly. For (a), I think that in such cases where computer is playing guide to 3rd man- it was actually the back foot punch/drive that was played in C19- not 100% sure but I feel that's how it was. Hope this helps, request everyone to please correct me if any of the above is wrong / feel free to add to this.

 

[gkvarma18]

Thanks at least for the response @MattW . That much is indeed appreciated.

The absolutely infuriating thing is, is this broken back foot square drive / back foot late cut glitch has now existed in EVERY mode of the game for the past 6 weeks & it's absolutely IMPOSSIBLE to miss. And I do honestly mean impossible!!

It doesn't matter what mode, what ground, what team, what match type, which individual player, which individual batting style, the broken shot is present regardless. (Ergo, anyone entering "any" in a bug report is irrelevant as any is actually 100% accurate.)

Countless users have been constantly complaining about this glitch since it was introduced weeks ago & you're telling me nobody at BA can see this at all? (If they can't then honestly what hope is there?)

It's simple, & if you'd like a specific example load the main Ashes tour, Australia vs England. (I'm Xbox Series X but users on ALL platforms have mentioned this same glitch/broken shot, it's not platform specific, it's universal.)

Have your devs attempt to play a back foot drive/punch through POINT, square of the wicket, & see what they get instead!!

You WON'T get a back foot square drive as the shot is now broken but it was working just fine until approx 6 weeks ago. What we have been getting instead for weeks now is the game glitching to a ridiculous back foot late cut that would ordinarily run the ball down to the third man.

However, because of this glitch this results in the ball weakly pinging off the bat & going straight & directly to backward point/gully every single time.

Load a new career mode & repeat. Attempt a back foot square drive through point & it WILL glitch to this broken back foot late cut. Again, it's impossible to miss. (I've now recreated this with EVERY choice of specialty, specialist batter, batting all-rounder, all-rounder, bowling all-rounder, bowler, with EVERY batting style. And still BA can't see it?)

It's unmistakable, present in every mode, match type, player, style, pitch, dynamic weather condition, & it can't possibly be missed.

Please raise ticket again and again then only will be addressed. Mentioning here it's of no use

 

[MattW]

Countless users have been constantly complaining about this glitch since it was introduced weeks ago & you're telling me nobody at BA can see this at all? (If they can't then honestly what hope is there?)

Yes - with the descriptions we had to go from, at least from what I could see/find, we couldn't work out exactly what people were referring to - batting has had some fairly significant changes, and I hope for the most parts improvements, since the game 6 or so weeks ago, which means isolating a thing that was good is more difficult. Maybe there was a really good post I missed, or a support ticket really early on that didn't get prioritised with the level of importance it would have needed, that would have meant getting on top of this particular case a lot sooner.

@Abcd9994's video above is excellent and has put us on the right track, we've found some things, and continuing to fine tune. That won't make it into today's update as that's already locked away, but hopefully there will be something in the next one.

I'm fine for everyone to just assume we're all idiots and have no clue if that will mean people will give the extra bit of info that helps us find what's being talked about. I want to find the problems you're raising, and sometimes yeah, that will mean I'll need to ask what to you might seem like a dumb question, or that we haven't seen something "obvious". Sometimes it takes a little nudge, or the right description, or there's one specific factor we hadn't considered.

 

[Gamefroggy]

Yes - with the descriptions we had to go from, at least from what I could see/find, we couldn't work out exactly what people were referring to - batting has had some fairly significant changes, and I hope for the most parts improvements, since the game 6 or so weeks ago, which means isolating a thing that was good is more difficult. Maybe there was a really good post I missed, or a support ticket really early on that didn't get prioritised with the level of importance it would have needed, that would have meant getting on top of this particular case a lot sooner.

@Abcd9994's video above is excellent and has put us on the right track, we've found some things, and continuing to fine tune. That won't make it into today's update as that's already locked away, but hopefully there will be something in the next one.

I'm fine for everyone to just assume we're all idiots and have no clue if that will mean people will give the extra bit of info that helps us find what's being talked about. I want to find the problems you're raising, and sometimes yeah, that will mean I'll need to ask what to you might seem like a dumb question, or that we haven't seen something "obvious". Sometimes it takes a little nudge, or the right description, or there's one specific factor we hadn't considered.

It could help if Big Ant get some of their own staff to watch people streaming Cricket 22. There you will also find a lot of info that can help with bugs and gameplay issues. I'm watching about four streamers and it is easy to pick up what is wrong with the game.

 

[GuyIncognito]

I may not be a mod or admin but can I just put it out there that this forum and discussion is not designed to be a pile on toward individuals. I'm disappointed with the game as well but stopping short of insulting people isn't on. Hate me all you want, but lets try and be civil about it. At the end of the day its a game, and the developers are doing the best they can, it may not be up to our standards but that doesn't mean they're not trying.