Game Version Number: v0.1.0.1.0887
Game Mode: Casual
Match Type: Five5
Teams used: England & Australia (Casper)
Ground: MCG (Downloaded with teams)
Over Count: 0.3
Issue (one line description): Ball seemed to hit itself for six
Bug description (detail): Bowling to Steve Smith with Jimmy Anderson, the ball pitched and headed straight towards the batsman. However, about half a metre in front of him it deviated sharply and flew up into the air towards fine leg. The ball had already travelled past the batsman before his shot animation kicked in, and even then, this was a full delivery that would have hit him on the ankles, and in the eventual shot animation (while the ball sailed through the air to the rope) - his bat never moved below his waist, and was always pointed up towards his shoulders. The point at which the ball started deviating was at about ankle height having not deviated at all off the pitch and heading straight for the pads. I assume this was just a graphical glitch, and if he was going to hit that ball for six then fine - he was certainly given the runs, haha! It was just a bit confusing when I watched it back to try and figure out what had happened. For a moment, I thought he'd somehow got six leg byes, haha! Hope that makes sense anyway and that it helps in some form.
It seems this glitch applies to wickets too...
Game Version Number: v0.1.0.1.0887
Game Mode: Casual
Match Type: Five5
Teams used: England & West Indies (Casper & Friedlele7)
Ground: Etihad Stadium (Downloaded with teams)
Over Count: 0.4
Issue (one line description): Stumps knocked out without ball reaching them, sometimes bouncing in the opposite direction
Bug description (detail): So, I just had this a second time, 0.4 overs into a different game (same details as before except - England vs West Indies, Five5, downloaded Etihad Stadium). Bowled a full length ball and middle stump was sent flying - EXCEPT, the ball actually hit the batsman on the pad and bounced away towards Short Leg, so middle stump seemed to fire itself out of the ground for no apparent reason, because the ball never even entered the crease. Again, I'm assuming this is just a visual issue, but I could see it happen in real time and I was able to verify with the replay - the stumps went flying while the ball was travelling in the opposite direction. Clearly not just a replay issue as I could see it happen before that, then checked after with the automated replay. Unfortunately, I couldn't get a screenshot because as soon as I entered the custom replay from the pause menu, the game crashed yet again. More problems there, I guess, as that's happened a few times for me now.
Edit - Now this is getting ridiculous, haha! I resumed the crashed save at 0.0 overs, and proceeded to take wickets exactly like this on 0.3, 0.4, 0.5 overs for my first DBC 17 hat-trick (I actually got another the next ball for 4 in 4, but that one did at least hit the stumps). All of them were full length Jimmy Anderson outswingers, smashing middle and/or leg stump out of the ground, even though the ball either hit the batsmen on the pads and bounced away or changed direction without even reaching the batsman. I managed to get screenshots of two of them, though the replay crashed AGAIN before I could get the third.
I've noticed both times, this was in a downloaded stadium, if that helps at all...
Edit - Well, it's not just Jimmy. I could repeat it with Jordan and Woakes. There seems to be a real problem with the batsmen not reacting for some reason. Ball pitched -> Stumps uprooted (with ball still in front of batsman) -> Ball changes direction away from the batsman (as if hitting his pad or possibly bat) -> Batsman starts to play his shot, but he's already out. Hope that helps in some way. This was on Medium / Medium / Pro, and I bowled them out for 30 - of which there was one legitimate bowled, one LBW, one caught behind, and all the others seemed to have this glitch.
Edit - Just a thought, I was having some frame rate issues before which may have been the cause of this in hindsight. Thankfully I've sorted it all out now, and have the game playing perfectly - so far I haven't had anything like this again, but it was still a bit weird. Will post if I have it again now that my game is running smoothly.
