Search results

I see. Thanks for the reply. Will wait for a few more patches then.

Hello everyone. Now that Cricket 22 has been out for months and has had multiple patches, I would sincerely appreciate it if anyone here could answer the following questions. I’m yet to buy the game, but will decide based on the answers to these questions. 1. In tests, can you get the AI...

On a dry hard wicket, SA were very much cruising towards their target of 297 despite a few middle-over hiccups. Pollock came to the crease when 80 were required with 4 wickets remaining, so he simply kept rotating the strike. However, with Rhodes getting run out, he was left with the likes of...

Chasing 275 on a dusty Indian wicket, SA were left reeling at 87/6--until Klusener and Boucher happened. This was my highest ODI partnership batting between hard and hardest against legend AI with 100 bowl quality.

Yes, the edges seem to go up during death overs just like real life when the batsmen are having a go at almost anything. Putting fielders behind the slips could help.

Been playing only ODIs for the last few weeks. Would be grateful if anyone could answer the following two questions. 1. In ODIs or T20s against human opponents, does the AI EVER get caught at point, cover, mid-off, or deep third-man? I saw those happening only in AI vs AI matches on YouTube. As...

Not always the case if you play the full game without simulating, at least in ODIs. If you get a huge score, the AI would sometimes crumble. In my last ODI, I restricted my opponent to 209/9 and won by 8 runs. Some matches before that, I bowled Aus 90s out for something around 227-230 and won by...

First time I saw the AI (Dravid in this case) play in this manner after I had some early success with the ball. Note: This is from a pre-patch game.

Thanks for clarifying about the return catches. The only times I saw and took those were off pacers. It bothered me a lot to see spinners not even attempting return catches. Post patch, I gave catches twice in the very first match. Not sure about the problem with playing in the V. I have not...

Played one ODI after the latest patch where I batted for both sides. Here are a few observations at legend AI, bowl quality 100, and custom batting between hard and hardest. 1. Shot power towards fine leg has markedly been lowered. Now it is very hard to dispatch the bowlers around that...

I play with standard controls but did give classic a go for a limited amount of time. Yes, the L stick should point towards the ball, but if your footwork difficulty setting is high, then the movement is usually more sensitive, so have a look at that. Also, IMHO, it is much easier in batting...

I've recently re-started playing the limited-overs game after completing 24-25 tests. Last night, I witnessed this cracker in legend AI, custom batting between hard and hardest, and bowl quality at 90. This probably is my best innings in an ODI not only because Saifuddin won the match from 49/5...

I think bowling too close to the off stump might be the reason why your edges are going exclusively to the keeper. Remember that it's not always the corridor of uncertainty that the AI struggles with--some would slash at wider deliveries, while some would simply block, and even then, you can get...

Finally had a test match go to the last session, and boy, what a tense match this turned out to be! It was a dry and medium wicket, so the batsmen from both teams had fun. Drama unfolded in the 2nd innings where I was left to get 429 in about 95-96 overs. I reduced the requirement to 399 on the...

Took another outfield catch in my latest test. This time, the well-set Steve Waugh was caught at deep mid-wicket.

I feel your pain, man. This happened with me one test back at short mid-wicket--the cursor simply won't move towards the circle no matter how much I moved the D-pad despite having the best fielder in that position. I felt robbed of a 3rd short mid-wicket catch in a single test.

Happens a lot, especially on soft wickets where the ball will not carry. I think such edges are the AI's way of sending the message that the batsman is 'ready' to get out if you bowl the right ball. Eventually, as you have also seen, they will get dismissed. But before that, it can be frustrating.

I hope we get such a realistic cricket game soon.

For me, variations of full and yorker lengths triggered the AI batsmen coming down the wicket. I think they have a tendency to misjudge the speed and bounce of the extra loopy deliveries. Don't remember the particular length I bowled for the long-on catch, but it probably was L1+triangle or L2+x.

Reverse sweep works best, sweep only goes towards square leg or around midwicket and not behind the batsman (even though the AI can do a strange sweep towards fine leg), but these two are pretty easy to get the timing right on. Switch hit could also be mastered, but I personally find it too...