[Steam latest patch, batting on arcade controls, feedback applicable while playing against pace bowlers only, not sure what happens when facing spinners]
Yes I am also confirmed now that this is an issue. Here's what I found:
There is a backfoot cut shot animation in the game, and you can play it. But it will only execute if the ball is far, far wide outside off stump. As it gets closer, e.g. 6th stump line, computer simply executes guide to third man shot.
As a result, when playing off the back foot, it gets really difficult to find the gap between cover and point.
In my opinion, it is not the cut shot that's missing, it's the backfoot drive/punch. This is just my personal perhaps less educated opinion, I might be wrong as well. It could well be that the "not able to find gap between cover and point against pace bowlers" issue was fixed for front foot play, the back foot play remained broken.
Indeed, normal grounded or even lofted back foot drives & cuts are working fine against spinners. Except, however, a lofted back foot cut against a spinner towards the third man region is definitely broken too as they never get above head height in the same manner the lofted cover drives were broken for 5 weeks.
It's definitely the back foot square drive/punch that's broken against pace bowlers as the shot
was previously working perfectly well on release & up until approx 3 weeks ago. It was also one of the most commonly used shots in C19 etc. (A lofted back foot drive seems to work through cover point, although it has the same issue as the cover drive also had where it rarely gets above head height so it's often caught if attempted. The back foot drive/punch also works straight, through mid off & sometimes as far round as extra cover. Played squarer the game is just broken, period ).
Yes, I'm seeing the exact same symptoms where a back foot drive through cover point to backwards point is attempted but the game glitches & incorrectly shows the animation for an incredibly weak back foot square cut that always pings off the bat directly to the backwards point/gully region which is almost always manned in every format.
Yes, if a delivery is also quite wide of the stumps (nearing the wide markers) it then plays a forward square back foot cut through the cover point region which while risky isn't an entirely impossible or uncommon shot of itself. (The same issues were present when the cover drive was completely broken in that a very wide delivery could still be squarely driven through the backward point region but the main mechanics remained broken.)
Same problem as the broken cover drives & lofted cover drives, just a different fundamental shot affected in this instance & a different field quadrant instead this time around too.
Like others I'm actually not far from the point of just giving up now. The fact that this has cost £50, it's still busted & they're pushing "niche aesthetics" just adds further insult to an already significant injury. It's become a seriously annoying & somewhat costly bad bloody joke.
I'm spending as much time down, resetting & starting over, looking for workarounds to ridiculous issues, or entering lists of bloody bug reports for critical issues & for what? Yet they plain ignore important issues again to add in rope sponsors which is incredibly low priority in the grand scheme whichever way you slice it. What does a rope sponsor or a bowling action fix when
everyone is waiting for fixes to broken shots/mechanics & have been since release?
Those with an absolute passion & the outright talent to create some amazing stadiums, equipment & faces etc. are undoubtedly a very rare commodity.
(I'm not for one moment intimating that they should be marginalized or left out as their work on stadiums or kits etc. literally changes the face of the game for the better .) Yet again, it's simply a matter of priorities & bloody rope sponsors or another bowling action were hardly critical issues that required such immediate attention. Vs what's clearly broken with mechanics, shots & physics,
a swiss cheese career mode, they certainly could have waited.