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

[sonimrajk]

Correct. The current behaviour is intentional.

I dont understand why is it intentional. No proper real batsman plays the shot that slow. There is a time gap between user input and the time animation plays. It looks really bad and very unrealstic.

If its going to continue like this please atleast reduce the time gap as possible as it can.

Also this gap looks very bad when the pace bowling speed is increased. So decreasing the time gap in accordance with the pace bowling speed should also be considered.

 

[The Fridge's Leg-Spin]

View attachment 265794
A pitch as green as this that too in England, still Ashwin taking all the five wickets on day 1. This really needs a fix as it is very easy to get AI out. @MattW

To be fair, this is actually realistic because this is classic England.

 

[Ed Smith]

Aye you can consider me fully on board the "spinners are OP" train now. I'm definitely not just gash at the game... Honest

 

[SloppyMane]

• Sporadically Batsman replaying that initial trigger load-up animation just as ball is approaching on styles 2,5,6 which has been there for more than a month now, still somehow hasn't been patched out
• DRS sometimes isn't shown post-dismissals to interact, really frustrating when its clearly the wrong decision by ump
• Not sure whether its supposed to be intentional or not, but pitch marker seems to readjust itself on some deliveries, if its intentional I assume its either making up for swing/lateral movement or the AI using after touch either way I'm liking the last fraction second change up

• Variety of balls(slowers/cutters etc) bowled in the 'death overs' period of limited overs is still sparse, when they do bowl we end up getting, bamboozled so would like more of them.
• AI bowling strategies like bowling to the field a.k.a setting up a field and bowling accordingly still feels lackluster and predictable(yes the f-word) i.e. If field is set on all leg side then AI bowls in off side lines and field is all off side he'll drift down the pads which we can easily milk runs to the point I'm ready with my left stick and waiting to time the ball.

• While edges off pull/hook shots should happen, it happens far too often to convince oneself right now
• Far too many leading edges when playing leg-side shots especially between the mid-on & mid-wicket region (In-game it says ok footwork in feedback but I've tried all possible footwork placements still happens, yes classic controls)

• WK animations (when user bowls) still is irregular at times, sometimes he manages super human like ones and then he leaves the simplest of lob up catches.
• Batting shot angle animations on areas like mid-off is not as it should be, so when you do edge playing those shots, you can visually see the ball is going through-the-bat rather than a proper outside/inside edge in replay.
  
  
• Proficiencies bug for specialist bowlers & WK, which I've repeatedly raised tickets/posts over months now and even posted a video displaying still exists.
• Ability to change the 'mentality' for licensed players is still locked, a fundamental pivot through which all others like reskilling,slider values come into play.

• Player sweaters seems to be some issue popping up like a tail with batsman who have styles 2,5,6.
• Kits & player model glitches like skin & flood lights shown through kits etc., are there for everyone to see.

Lastly, a game dev can only improve when there is communication/feedback from end users,if we settle down saying its already a decent game then we may never let it reach the levels we all know it is capable of.

I can see even the builds activity that used to update daily for the game in steamDB has been getting stale for some time now.

This will be my last post unless any significant change is made in the game and I'm gonna take the piece of advice that few have concernedly given away to all of us who have bought the game with their money, I'm gonna 'let go' and 'get a life'

 

[Plotinus]

Three of them were caught at leg slip and short leg. Two of them were bat/pad and one was a sweep shot. Other two dismissals were bowled and caught behind.

Would you say that the catches at leg slip and short leg were the result of good bowling or bad shots? A lot of bat-pad dismissals, I have seen, seem to come from bad shots...or at least poorly executed attempts...to balls that could have been left because they were going down legside or could have been played straighter rather than pusing across the line and against the spin into the legside. All close fielders are in catching positions, so you would expect them to take catches that come their way (though I wouldn't object to them spilling some of the harder ones more often than they do). However, with leg slip and short leg (I also have silly mid off and 2nd slip most times) in place, the batter should be trying to play straight more often and defending balls that are bringing risk to those close catchers....and occassionally playing aggressively to try to get the close fielders push to more run-saving positions. I still think, it's not the spinners that are the problem...it's the batters.

 

[tarrantino]

I get the same flashing too, with the controller it came with.

Ok well that’s one theory gone. Maybe the quick resume is the problem?

 

[sonimrajk]

So you do have them then.

Very very rare... not recently though. Maybe Crashes are in some game area which i am not trying.

 

[midhun333]

Would you say that the catches at leg slip and short leg were the result of good bowling or bad shots? A lot of bat-pad dismissals, I have seen, seem to come from bad shots...or at least poorly executed attempts...to balls that could have been left because they were going down legside or could have been played straighter rather than pusing across the line and against the spin into the legside. All close fielders are in catching positions, so you would expect them to take catches that come their way (though I wouldn't object to them spilling some of the harder ones more often than they do). However, with leg slip and short leg (I also have silly mid off and 2nd slip most times) in place, the batter should be trying to play straight more often and defending balls that are bringing risk to those close catchers....and occassionally playing aggressively to try to get the close fielders push to more run-saving positions. I still think, it's not the spinners that are the problem...it's the batters.

Could be something to do with their engine. If I recall correctly this issue was there in Cricket 19 too. I further adjusted a few sliders, seems like the silly bat/pad is gone but need to play more to make a conclusion

 

[Pinch hitter]

Easiest way to make Pitch & Weather condition is important part of Cricket 22

• Bowlers gets rating boost and reduction based on pitch type and weather conditions, before and in-between the match...
• Add variation in Batsman batting timings... Like the time of ideal shot play in Standard pitch will be different in green pitch or in dry pitch etc...
• Add variation in batting timing window... Like you get smaller, good and ideal timing window against fast bowlers in green pitch and bigger timing window against spinners in same green pitch... And it changes in different pitches against different bowler types...
• Remove Ideal timing completely from the Hardest settings...

 

[Hester]

Ok well that’s one theory gone. Maybe the quick resume is the problem?

I've never used quick resume with the game.

 

[Wealey]

The first thing that people need to do with the spinners is stop using the HUD which allows perfect input over and over and over

 

[midhun333]

The first thing that people need to do with the spinners is stop using the HUD which allows perfect input over and over and over

Not something for everyone I believe. I think it is something BA should fix it in the upcoming patches

 

[Wealey]

Not something for everyone I believe. I think it is something BA should fix it in the upcoming patches

Yeah.. but if your getting the perfect input every time and the game uses that for wickets etc. Your going to generate multiple chances.

I have HUD off and vary between good and ideal and in my last test bowled 40 overs for 2 wickets in a dusty pitch.

Anyone can look at a meter and stop it where they want fairly frequently.

 

[smurfygray86]

Yeah.. but if your getting the perfect input every time and the game uses that for wickets etc. Your going to generate multiple chances.

I have HUD off and vary between good and ideal and in my last test bowled 40 overs for 2 wickets in a dusty pitch.

Anyone can look at a meter and stop it where they want fairly frequently.

I tried this and struggled so scrapped it straight away but went back and stuck with it and it’s much more enjoyable watching the bowler and thinking of timing and shot selection rather than just staring at the hud. Looks better aswell on screen

 

[Wealey]

I tried this and struggled so scrapped it straight away but went back and stuck with it and it’s much more enjoyable watching the bowler and thinking of timing and shot selection rather than just staring at the hud. Looks better aswell on screen

Exactly.. also gives you a variety of outputs and gives you far more scope to work with with ideal input sliders if needed.

You don’t have to look at a meter like you say and are focused fully on the bowler