Platform: Xbox One X
Game Version: v0.1.1349
Game Mode: Career
Match Type: First Class.
Teams used: Kent vs Hampshire, (in this instance).
Ground: Kent Oval
Over Count: Began in 9th over in this instance.
Issue: Batsman began taking giant steps across the stumps & down the pitch right at the moment the shot needed to be played from spin bowlers. (Fast bowlers remained unaffected.)
Bug description: Ordinarily the batsman stands still at the crease until the moment a shot is played, the delivery is actively left by the player, or there is sometimes a very subtle trigger movement/step to spin bowlers, (more so leg spin vs off spin). However, my batsman (RHB) suddenly started taking
giant steps forward & across the stumps even to deliveries coming in from the leg side, (advancing shots were not being inadvertently activated). (I can't recall ever experiencing this problem happening before the latest patch in literally thousands of matches played of all formats, & with multiple careers of differing specialties, but I've now seen this happening a couple of times since the latest patch. It continued on for several overs in this instance while spinners were operating at both ends & then cleared itself when a fast bowler came back on this time.)
Exiting/re-entering the match, restarting the game, or completely rebooting the Xbox had no effect until it eventually seemed to clear itself. Ultimately, it made batting nigh on impossible because - I could no longer gauge exactly where & how far the batsman would step forward/across to, where I'd actually end up in relation to the stumps & a moving ball after this "giant glitch step", & the batsman was still actually in motion exactly when the shot needed to be played which also caused serious timing issues as well. Even a simple front foot defense became almost impossible because the batsman was still in the middle of taking this huge step & almost all that I did actually manage to defend were still timed very late anyway. (I had more LBW appeals made against me or was very nearly bowled in those 12 glitched overs than I can ever recall having in any 12 matches!!)
(I currently use custom batting difficulties based upon the "hardest" preset but modified to be slightly easier than the actual hardest preset itself.)
Will edit this post if this becomes a chronically recurrent issue but it obviously shouldn't be happening in the first place.
EDIT:. OK, this has become a repeating issue but oddly it only seems to be happening with my genuine "
all rounder" career so far. I've been trying to recreate it with a "specialist batsman" & a "batting all rounder" career as well. (I've also tried testing to recreate this glitch in other game modes such as an Ashes series or ODI World Cup matches using the entire team to bat rather than one individual player.) So far, I haven't been able to recreate this glitch anywhere else & oddly it seems to be confined to the "all rounder career" alone.
A "
possible" cause/trigger that may be contributing towards this particular glitch is the pre-delivery use of both the
LEFT trigger to view current fielding positions,
plus the simultaneous use of the
RIGHT trigger to check the batsmans exact guard/position on the batting crease. (It's not 100% recreatable every time for me to be 100% certain. However, using both triggers certainly seems to be a very common pattern so far after now seeing this glitch
repeating in another 5 or 6 separate matches since the initial post. I'm using an
Xbox Elite Series 2 controller if that's also of any consequence.)
On a related note there's now another glitch with the latest patch that may have actually lead to the discovery of this one. Prior to the v0.1.1349 patch, if you moved the batsman from their default position on the crease for fast bowlers & a spin bowler then subsequently came into the attack for the first time in an innings, the game would always automatically return the batsman to the default crease positioning/guard for a spin bowler.
Since the latest patch, the batsman now isn't always automatically being placed back to the default crease position when there's an initial change from a fast bowler to a spin bowler at each end respectively for the first time in an innings. (Consequently, obviously I have to readjust my crease positioning manually when there is a change from a fast to a spin bowler & the automated repositioning fails. I then also need to use both triggers simultaneously to double check that I'm positioned & taking the correct guard specific to the type of spin bowler. Prior to this issue, because the game would always automatically move the batsman back to the default guard/position when a spin bowler first came into the attack I never needed to use both triggers to adjust/check guard as the vast majority of the time I just bat from the default position when facing spinners. (I constantly adjust my position on (or just outside) the crease when facing fast bowlers, however, based on their height or actual pace, or the type of pitch itself, & especially in the shorter formats of the game.)
(
Additionally - I use the "
BATTING CLOSE" view almost exclusively as I like the additional degree of difficulty the batting close view adds & personally I find it slightly more immersive than the alternatives too, which is possibly compounding this issue. (I occasionally use the "
BATTING PRO" view but I haven't noticed it happening while in the pro view either.)
It may even be an issue specific to the batting close view itself, as I can't help but notice the distinct lack of anyone else reporting this same glitch & I know I'm in a distinct minority of those that use this particular view for batting. (It's not as straightforward to immediately gauge the batsman's exact positioning on the crease using the
batting close (or pro) view as it is with the
batting mid/batting far views because of the significant difference in the actual view angles from behind/above, or first person respectively. Batting close has a far shallower rear angle of view so both triggers are often required to check the exact positioning of the Batman's feet. Batting Pro pretty much speaks for itself.)
I apologise for the lengthy details but it's not exactly an easy issue to properly explain in 50 words or less, & obviously I'm potentially using settings/views that the vast majority quite possibly aren't
!!
Regards.
