@WealeyH Played ODI after setting every player's strength down by 50, so most were in teens, I think Afridi and Inzi were around 30. Pro difficulty, dusty/soft/wearing pitch, bowling as both teams. Note: I also have my "05 ODI" match type with longer, test length boundaries.
Now if you'd asked me before the match based on pitch/conditions I would have said around 270-280 was a very good and most likely winning score, so in that respect the game was very realistic and I had a lot of fun playing it. Really thought Akmal and Pakistan were going to make it until I just ripped through the tail. I thought Murali would do better on such a pitch but seemed like it was a day for pacers.
All I can in the negative say is that some things just still "feel" a bit off. For one thing despite the lowered strength batsmen were still pinging 100m+ sixes, there were a lot of mishits and skiers but every one of them apart from 2 landed perfectly safe (which were both caught by the mid-off fielder running back). Not that this is bad if it just happened in one game but it's a consistent pattern I've noticed from a lot of limited overs bowling, the AI really does feel blessed when they hit the ball in the air. I know it sounds really stupid after all the years of us complaining about the stupid AI holing out all the time, but at least in LO cricket I feel it should still be a pretty common occurrence (if we can somehow keep the AI competitiveness as well). I would quite like my boundary fielders to be more than just run-savers if possible.
Still I'm kind of in the same camp as
@Langeveldt. If the game was never patched again I could play it forever quite happily, but if it could somehow be improved even more that would be crazy.
And there were no prod shots of course!