smurfygray86
Associate Captain
- Joined
- Feb 9, 2022
Agree can go for ages without seeing a leaveYeah agree… it’s random.. and they can go a while without even playing a leave would you agree?
Agree can go for ages without seeing a leaveYeah agree… it’s random.. and they can go a while without even playing a leave would you agree?
yeah, like 15 overs, unless you bowl 15 ft outside off stumpAgree can go for ages without seeing a leave
I've had slo mo mode happen to me too, but it always stopped when I exited and reloaded. I only rarely get slo mo and, when it happens, it's generally after an automatic replayI experienced continues slow mo sweep shot for an entire over.
Played a test match on dry day 5 crack surface with heavy tear and spin revolutions at 55 against India
every single ideally timed sweep shot was played out in slow mo.
I see, I'll keep this in mind and check again! thanks mate!I've had slo mo mode happen to me too, but it always stopped when I exited and reloaded. I only rarely get slo mo and, when it happens, it's generally after an automatic replay
But but but little Timmy wants fireworks and blue dye for hair.I think we need to prioritize the list of issues and then put it in front of Big Ant.
Example - Who cares that AI is not leaving the ball in tests if
1) All the shots are not being played properly as a batsmen
2) Your game keeps crashing
3) Career data keeps getting corrupted
4) Shot power is not fixed
5) Fielders look at the opposite directions when gathering the ball (even this fix can wait)
6) Keeper/bowler reaction times and bouncers going through keeper
7) Post overthrow fix, the fielder now throws the ball directly to the bowler even if there’s a run out chance.
8) AI keeps setting the same field even after being hit in same direction
I feel that we need to pick what impacts an average user and then get into advanced details of the gameplay
Send this to big ant support nothing helps hereI think we need to prioritize the list of issues and then put it in front of Big Ant.
Example - Who cares that AI is not leaving the ball in tests if
1) All the shots are not being played properly as a batsmen
2) Your game keeps crashing
3) Career data keeps getting corrupted
4) Shot power is not fixed
5) Fielders look at the opposite directions when gathering the ball (even this fix can wait)
6) Keeper/bowler reaction times and bouncers going through keeper
7) Post overthrow fix, the fielder now throws the ball directly to the bowler even if there’s a run out chance.
8) AI keeps setting the same field even after being hit in same direction
I feel that we need to pick what impacts an average user and then get into advanced details of the gameplay
I think the whole game is built around Trash20.. sorry, T20. All the commentary is related to limited overs cricket, the way the AI swings the bat at everything, the crowd reactions from a slog or a boundary...it's just how it is I guess.I reckon I bowled 25 overs in a Test match on reduced run rate of 30 and I don't remember a single leave...
I posted a week or so ago that I'd been playing with the AI run rate at 0 and the AI would leave or block every ball. At run rate at 1 or 2, they try to hammer the F out of the ball every single time but it would generally go straight to a fielder. However, I think C19 had this problem too as I remember posting about it a year or so ago.
I think the whole game is built around Trash20.. sorry, T20. All the commentary is related to limited overs cricket, the way the AI swings the bat at everything, the crowd reactions from a slog or a boundary...it's just how it is I guess.
I get your frustration - I feel it too - but the team that does things for Timmy isn't the team that looks at gameplay. They are the art people at BA.But but but little Timmy wants fireworks and blue dye for hair.