The visual bug only happens to my player when he's using a jumper.
I tried bowling in the first session of a match in a few games on a grassy/medium pitch and I observed that either of the two things will happen.
1. AI will start losing wickets from the first or second over the game
or
2. AI will wait for you to change bowlers and then start losing wickets (If I am not able to pick up wickets they will run themselves out).
Is there a way to make picking up wickets look more natural or random? Cause these things look hardcoded like AI loses wickets just after the powerplay?
Coming to the variety of dismissals. LBWs look the most natural.
Caught Behinds are fine but they would look better if there are more thin edges (that end up as catches) in the game. Usually, there are only thick edges and the keeper takes one-handed catches (sometimes in front of slips).
Catching at slips to be fine, just hope the first slip can do something more in the game other than just standing.
Bowleds don't look natural at all, a set batsman not playing in the line of the ball? It looks really ugly. Plus every time you take a wicket (bowled) the stumps go flying. Can't there be instances where the ball just clips the stumps and they don't go flying around?
Catches in the circle and out-field are good but there's a way for them to look more natural. Can AI play a few shots that just caries to the fielder in the circle or the outfield?
If a player is rewarded for bowling good line and length there's nothing better than this. Hope this hard-coded stuff gets removed and things happened a bit randomly (which looks natural) across formats.
What are your thoughts?
Also tagging
@JNT BA
View attachment 269360