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

Is it just me or anyone else's game crashing after playing the debut match in the BBL (career mode)?
yes its happened to me for Tasmania I'm the captain and suddenly matt wade is at the bat flip which is ridiculous and then it crashes again and again I've submitted the ticket and they actually emailed me and looking into this for us
 
Last edited:
If u want self headache plz go and purchase ps5 version. Atm game is extremely worst on almost sll platform after last patch. those who are still enjoying or praising either they adjust via lots of tweaks in settings, sliders, player skillsets to their level to minimise existing bugs or they know that game is extremely broken but cant accept.

By the time you tweak settings for sure new patch for breaking game more would by there in which awesome features will introduce like bowlers having gold chains around neck or fielders having sunglasses on top of cap etc etc.

I doubt if current BA team really play cricket then what type of cricket they bring in C22.

Dont forget to report bugs at BAS and get auto reply and if you dare to complain ross at twitter, you would be blocked.

Regarding ur query, C22 has nothing with dual sense so better to play C19 if u want good cricket
enjoyable time pass.
Thanks all for the responses on the PS5 version and DualSense.

I really wanted to buy this game, but seems like there is nothing special about the ps5 version either, with ongoing bugs, and BA using its customer base to test the product and report back, I think I will wait. I'm certainly not going to do any UAT for them at this retail price point.

Getting blocked or complaining about a poor product seems harsh. Shouldn't they blame themselves, credit customers, offer other free games in their library as compensation?

Can't imagine what the Switch version will be like :)
 
Problem with Unreal engine 5, or unreal in general, is that steam takes a 30% cut of a sale. After a certain amount of sales, Unreal takes a %10 cut of sales. All up that's 40% lost to third parties so I can see why they want their own engine but atm it just isn't cutting the mustard.

Your numbers are off. First 1 million USD, you don't pay Epic anything. 5% after that.
On Steam, you pay 30% until 10 million USD and then 25% until 25 million USD and finally 20% if above that. Instead if they choose to release on Epic Games, they will pay 12%.

So if BA chooses to go Epic all the way, it would be 17% instead of the 30% right now. Or a 35% (just 5% increase) that will save them from having to overwork their employees when the engine isn't responding as fast as they want it to. But then, the change would need new employees who are trained in Unreal (there is high demand now), so making a shift would need to be a fully committed one. It's BA's decision but if they don't make the right choice, they will only survive until a better developer turns up or until this becomes unprofitable.
 
I've finally had the time to have an extensive play (although 20 overs isn't that extensive but I want to go eat).
  • I'm at 15 no balls so far. The jump and release feels a little inconsistent between actions. Although it could just be that the difficulty has increased from Cricket 19. I have no problem with it being more difficult as it was far too easy to get Perfect/Perfect at least 3 times an over even without using the timing meters. Don't know if there needs to be a bit more balance with the jump and release across actions, or if I need to drop a level difficulty level.
  • Lovely number of plays and misses. Three wickets from edges (two inside - one was an ugly aggressive drive by Malan, the Crawley one I shared in the clips channel). Got Root in six balls, three he edged. One for four, one was dropped at second slip and then the last one was caught by the keeper. Fending one off.
  • Still not certain if and when R1 and L1 length adjustment works.
  • Keepers still do my head in.
  • Can live without the AI scoring at 6 runs per over in a test match. Even taking away the no balls it's well over 5 per over.
Genuinely enjoyable bowling apart from the AI scoring rate, which stinks - but that's no different to Cricket 19.
 
Last edited:
I noticed in 50 over game they usually go for big runs in the last 5 overs or so which I thought is a nice feature as it happens in reality like this. I also play on 20 RR and Timing 20 so it makes for exciting end
Have you noticed just 3 fielders outside the ring between 10 to 40 overs?
 
Thanks all for the responses on the PS5 version and DualSense.

I really wanted to buy this game, but seems like there is nothing special about the ps5 version either, with ongoing bugs, and BA using its customer base to test the product and report back, I think I will wait. I'm certainly not going to do any UAT for them at this retail price point.

Getting blocked or complaining about a poor product seems harsh. Shouldn't they blame themselves, credit customers, offer other free games in their library as compensation?

Can't imagine what the Switch version will be like :)
Nintendo won't approve these huge patches as happened with cricket 19, there will be handful of ppl who will still buy it.
 
NO Appeal on RUN OUT & It went NOT OUT only...

This is called fixing in real means! :p
 
I've finally had the time to have an extensive play (although 20 overs isn't that extensive but I want to go eat).
  • I'm at 15 no balls so far. The jump and release feels a little inconsistent between actions. Although it could just be that the difficulty has increased from Cricket 19. I have no problem with it being more difficult as it was far too easy to get Perfect/Perfect at least 3 times an over even without using the timing meters. Don't know if there needs to be a bit more balance with the jump and release across actions, or if I need to drop a level difficulty level.
  • Lovely number of plays and misses. Three wickets from edges (two inside - one was an ugly aggressive drive by Malan, the Crawley one I shared in the clips channel). Got Root in six balls, three he edged. One for four, one was dropped at second slip and then the last one was caught by the keeper. Fending one off.
  • Still not certain if and when R1 and L1 length adjustment works.
  • Keepers still do my head in.
  • Can live without the AI scoring at 6 runs per over in a test match. Even taking away the no balls it's well over 5 per over.
Genuinely enjoyable bowling apart from the AI scoring rate, which stinks - but that's no different to Cricket 19.
Every action is so inconsistent with the timing on broadcast cam as its so janky following the bowler.

Takes me 2/3 balls with each change of bowler to get the timing of jumps good
 
Do you lose a lot of wickets? On Cricket 19 the AI may set fields that are more offensive to newer batsman.

It's okay to have an offensive field set to a newer batsman. But if a wicket falls during the later stages of the innings, it should not be happening.
 
Every action is so inconsistent with the timing on broadcast cam as its so janky following the bowler.

Takes me 2/3 balls with each change of bowler to get the timing of jumps good
I actually like the fact that timings are different for each action. I bowl in ProCam mode and like the fact that I need to make adjustments depending on the action of the bowler...it makes it more interesting and gives another element to the gameplay. If the timing is exactly the same for all actions, then the use of different actions is just an animation gloss that is not influenced at all by what you, as a player, do.
 
After long time on steam,Played a long session of saved career, no run out bug occurred in 3 hours, almost 15 matches, and 40-50 overs, only thing was left handed fast bowler was bowling on leg line(old problem)
Enjoyed a lot although making runs was easier, but i will increase difficulty again & check.


Then started bbl and played 2 full matches. Both batsmen running same side occurred once only. But problem is that whenever i change field and apply all game crashed, i had to do it one by one.
Also AI didn't hit last ball boundary everytime. It was there but not so often. Although they charged 198 runs in 2nd match but will check now matched for conclusion. I will tinker with sliders to see if it does make major differences as in last two overs i tried to lower down AI timing form 35 to 30 but he still managed to hot 2 consecutive sixes.
Fielder sliding four bug occurred on bbl matches, in career everything went fine.
Straight sixes were too high, but got 4 5 boundaries with straight drive.
Cut shot was changed in to late cut but only when close to body, i managed to play some cut shots when ball was away from body.
Still i enjoyed the play. That should first on fixing minor things 3 basic aspects, i.e. batting, bowling, fielding. That should suffice for long time. Other cosmetic things can be adjusted later.
I felt game is playable on steam of ignore some minor bugs( i never faced headless players).
Also i verified integrity after latest patch on steam after reading here.


And yes... now, when trying to start next bbl game on new competition game's crashing but old saved bbl saves are fine.
 
Last edited:
Just had to simulate a career red-ball game because every time I loaded up it kicked me back to the dashboard (tried 10+ times)

of course I got two golden ducks and my average has taken a dive.

can’t complain though. Just have to get on our knees and be grateful we have a cricket game
 

Users who are viewing this thread

Top