Is this wides problem since the latest build as I am
Just not coming across it to this extent. Not saying it isnt there just trying to help narrow it down so we can help get it fixed....,[DOUBLEPOST=1565259499][/DOUBLEPOST]I get the pissed off bit but we need science not emotion to get things done.
Well, I assumed it was the build, since I hadn’t been experiencing it to this extent for some time.
BUT - I know before that the situation was worse with aggressive/brute bowlers and I had as far as possible avoided these types of bowlers.
Looking at the squad list, I realise actually I had 3 out of 4 as “aggressive” and 1 as balanced. Though they were all culprits, the aggressive were certainly worst. (Sigh, another competition restart in order.)
There are multiple parts to this problem however.
1) The AI is capable of bowling “ultra short” so short it doesn’t even hit the “short” area on the pitch map. These cause the vast majority of the wides.
2) The wicket keeper runs forward under the ball. This is just nonsensical.
3) There is obviously an issue with ball and pitch bounce, whereby even on a medium pitch with both reduced (35 currently) it’s still bouncing wildly
4) Even with “test match wides” the umpires are harsh on anything leg side.
5) If you have a big partnership, the AI has no other plan but to bounce. Case in point, I didn’t have this problem as I slumped to 46/4 off 29 overs at lunch. In the afternoon session I didn’t lose a wicket, and the problem arose and began to grow. The evening session I still didn’t lose a wicket, and it became borderline unplayable. Even when they weren’t ultra-short wides, roughly 4 balls in every over was a bouncer.
