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

[cricboi]

Played a few T20 games and noticed an overall improvement in fielding albeit with some new issues. On the whole fielders reacted a bit faster off the ball and it felt more fluid. I even got a few wickets that I never had before, with balls being nicked up in the air and the keeper running all the way to silly point to get the catch. On the other hand, with improvements come some stranger errors. For example, many times an outfielder dove to stop a boundary but only 50% of the time a second fielder was running to assist. In those cases the fielder who dives gets up and just stands there for 2-3 seconds before finally walking towards the ball and then cuing up the casual slow-mo retrieval. Another newer issue is that on a few high pop ups the catching game took a while to show up and once it did it disappeared in less than a second. This also happened to me with a catch at slip.
Other improvements were in the AI batting where they paced a few nice t20 innings and their running was increasingly more aggressive (this felt good). They finished 167-3 (I beat them by 18 runs) which should've been 167-6 without the glitches. All in all that's a compelling score in the circumstance and felt cool to be under pressure.

 

[SloppyMane]

I'd need more information - what platform you're on, specific teams you're referring to, etc. This is the only post I've seen with someone getting this.

Redownloading them fixed the issue.

 

[Wealey]

What he is referring to is the fact that they didn’t ‘fix’ the frame rate issue but rather changed the entire visual which some of us really liked.

Hopefully they can add it back as an option in the menu and allow us to choose whether we want the new visual (that improves the frame rates) or go back to the old one (and have low frame rates with it since apparently the issue cannot be fixed with the old visual)

Hope you don’t go back to praising everything since you are now on the beta testing team .

What you on about. I simply said they removed it due to it causing FPS drops. Whether it fixed it or not I don’t know.

I have never just praised everything. Ever.

 

[GuyIncognito]

Alright everyone, lets all take a step back and take a few deep breaths, lie-down and have a thought. Stop the subtle/not so subtle sniping of other users, sneer comments etc. The last ten pages or so on this discussion thread haven't been our best in terms of posting habits.

People over here starting to get petulant about a video game, when there are maternity hospitals getting bombed in broad daylight. Keep some perspective people.

Not saying you can't be disappointed or negative towards something you disagree with after an update, but whinging, moaning etc without a level of reason or suggesting constructive feedback etc is getting tiresome.

I may sound harsh, but lets keep it civil and constructive.

 

[shan111]

Quick question, apologies if this has been answered earlier. Last night I had AI batsmen stepping out to spinners and they were comprehensively beaten. However, the WK took his own sweet time to take the bails off and batsmen always managed to get back just in time. Is this something that everyone is facing? I am using full-auto fielding.

 

[Syed Bukhari87]

@MattW regarding the ball physics with day 0 patch , I think it was all due to ball being more heavier and coming off slowly off the pitch (i-e more friction off the surface) ,It felt some heavier ball has kissed the surface before it rises from the pitch again. Wish it can be replicated in the next patch , That feeling was awesome specially when bowling with Rabada's action. It does felt that bowler has put heavy muscle on the heavier ball and it the pitch surface really felt the impact.

Ball weight slider any one?

 

[Pinch hitter]

Quick question, apologies if this has been answered earlier. Last night I had AI batsmen stepping out to spinners and they were comprehensively beaten. However, the WK took his own sweet time to take the bails off and batsmen always managed to get back just in time. Is this something that everyone is facing? I am using full-auto fielding.

Yes keeper are slow in stumping and in runout too... In last patch bowler acted quickly in runout situation, which looks awesome... But keeper still act little or too slow all the time... (Not played latest patch yet)

 

[azkhan]

Quick question, apologies if this has been answered earlier. Last night I had AI batsmen stepping out to spinners and they were comprehensively beaten. However, the WK took his own sweet time to take the bails off and batsmen always managed to get back just in time. Is this something that everyone is facing? I am using full-auto fielding.

Sometimes they can take their time. It can sometimes feel like they are holding Thor's hammer when trying to hit the wickets lol but most of the time they are quick, I have had some good stumpings in the game. Using semi auto fielding.

 

[SloppyMane]

For all those who liked that day 1 'weight on the ball' feel, Personally I've found the 'Pace visual speed' slider helps in recreating that feeling.

For reference, I have it at 80-90 depending on where I'm playing like in Eng or Aus etc.

 

[GuyIncognito]

For all those who liked that day 1 'weight on the ball' feel, Personally I've found the 'Pace visual speed' slider helps in recreating that feeling.

For reference, I have it at 80-90 depending on where I'm playing like in Eng or Aus etc.

100% agree. That was the first thing I changed a few months back and changed the feeling of the game in a pretty big way.

 

[Nithin Antony]

100% agree. That was the first thing I changed a few months back and changed the feeling of the game in a pretty big way.

Very true. Even for spinners it gives a better feel when the values are increased.

 

[Syed Bukhari87]

For all those who liked that day 1 'weight on the ball' feel, Personally I've found the 'Pace visual speed' slider helps in recreating that feeling.

For reference, I have it at 80-90 depending on where I'm playing like in Eng or Aus etc.

I have it on 100 and the usual ball pace ball at 60 for min and max , I am not having that feeling. Shall I increase the pitch fraction and lower the visual speed to 80 or 90 and increase the pace to 70?

 

[Crassus]

Right I played a session of a test match last night with the latest patch. Some positives and some areas of concern. I was England against India

I was playing with some pretty extreme sliders and reskilled players. I've tried to make a slider set that I've named 'Seamer Paradise Days 1,2,3' where there is loads of swing (slider on 90), AI run rate at 18, striker timing at 35 and wicket chance at 70. We do see these types of wickets in real life, particularly if India are coming to town. I've basically taken all the spin sliders right down too to try and nerf the usually unstoppable spinners.

The idea being that its an absolute nightmare to bat on. After 40 overs I have India 72/5 which seems quite realistic, Archer has taken 4, 3 bowled and one caught by Vince at 3rd slip. Jimmy had Sharma caught behind to Bairstow (WK). I'd probably say that IRL on this green wicket with these conditions 90% of the wkts would be caught behind off the seamer but we can't have everything.

Another positive is that there have been plenty of play and misses, Jadeja wafted at 3 Stokes deliveries in a row and I really thought this was the AIs way of saying he was about to get out but no he just knocked the next ball for a single.

Thanks to the reskilling Pant is in now taking the attack back to us and when I've bowled poorly I've been put away but by and large India have left mostly and are going at less than 2 an over so perhaps I need to slightly adjust the run rate slider. I have obviously made the batting sliders so that it will be a nightmare for me to bat on too (AI bowling well up, OK and poor input being massively punished etc).

OK negatives now, the fielding (shock). Several times the ball was played fairly nonchalantly through mid on which looked easy as pie to field yet the fielder dived over the ball. I understand the need of having fielders making errors and misjudgements but this looked terrible, a few weeks ago they seemed to have the balance right on this so who knows what has happened.

Another small thing really is the insistence o of the fielder to throw it into the keeper at the speed of light even when no run is taken, and then sometomea a fielder diving across to take the catch on the keepers behalf. Again a small thing but looks terrible

 

[SloppyMane]

I have it on 100 and the usual ball pace ball at 60 for min and max , I am not having that feeling. Shall I increase the pitch fraction and lower the visual speed to 80 or 90 and increase the pace to 70?

I guess it also depends on your overall batting difficulty values, yes I have max pace at 75 and visual is on 80 if that helps.

 

[smurfygray86]

Right I played a session of a test match last night with the latest patch. Some positives and some areas of concern. I was England against India

I was playing with some pretty extreme sliders and reskilled players. I've tried to make a slider set that I've named 'Seamer Paradise Days 1,2,3' where there is loads of swing (slider on 90), AI run rate at 18, striker timing at 35 and wicket chance at 70. We do see these types of wickets in real life, particularly if India are coming to town. I've basically taken all the spin sliders right down too to try and nerf the usually unstoppable spinners.

The idea being that its an absolute nightmare to bat on. After 40 overs I have India 72/5 which seems quite realistic, Archer has taken 4, 3 bowled and one caught by Vince at 3rd slip. Jimmy had Sharma caught behind to Bairstow (WK). I'd probably say that IRL on this green wicket with these conditions 90% of the wkts would be caught behind off the seamer but we can't have everything.

Another positive is that there have been plenty of play and misses, Jadeja wafted at 3 Stokes deliveries in a row and I really thought this was the AIs way of saying he was about to get out but no he just knocked the next ball for a single.

Thanks to the reskilling Pant is in now taking the attack back to us and when I've bowled poorly I've been put away but by and large India have left mostly and are going at less than 2 an over so perhaps I need to slightly adjust the run rate slider. I have obviously made the batting sliders so that it will be a nightmare for me to bat on too (AI bowling well up, OK and poor input being massively punished etc).

OK negatives now, the fielding (shock). Several times the ball was played fairly nonchalantly through mid on which looked easy as pie to field yet the fielder dived over the ball. I understand the need of having fielders making errors and misjudgements but this looked terrible, a few weeks ago they seemed to have the balance right on this so who knows what has happened.

Another small thing really is the insistence o of the fielder to throw it into the keeper at the speed of light even when no run is taken, and then sometomea a fielder diving across to take the catch on the keepers behalf. Again a small thing but looks terrible

Positives outweigh the negatives there sounds good still the silly fielding looks like it needs sorting but hopefully that will come

Post automatically merged: Mar 18, 2022

I

I guess it also depends on your overall batting difficulty values, yes I have max pace at 75 and visual is on 80 if that helps.

I used your batting settings last night mate and wow it felt real instead of arcade like I had to concentrate so much after losing 3 early wickets I’m having to learn to leave and block rather than just swinging away at everything