Ashes Cricket General Discussion

Okay like a major gliche (understatement of the century).
Yeah, having toiled through 167 overs with three centurions and Australia scoring 602 it was a good chance to notice quite a few. Lbws, or very reasonable reviewed lbws chances, that don't match the ball tracking. I had a catch that was celebrated but Tim Paine stayed in. There's a lot of times where fielders just don't seem to react to balls in going near them, it'd be nice to at least see an attempt to stop a ball near them or going over their head. Caught and bowled opportunities not even attempted. This is all on fully assisted fielding. The keeper standing further back for medium pacers than fast medium bowlers and not being able to move them up to the stumps is really frustrating.

It could be factors such as difficulty settings, my bowling, the field settings, the conditions or the just the agony of a side batting on a flat pitch but the top skilled players just seem to never appear troubled, ironically, until the ball gets old and it starts to move less. I don't know what other people are experiencing but second innings batting has always been too strong in the previous games for my liking and this was painful. I know cricket can be like that, particularly for England. I can only hope this is a one off otherwise I'll be giving test matches a swerve.
 
Yeah, having toiled through 167 overs with three centurions and Australia scoring 602 it was a good chance to notice quite a few. Lbws, or very reasonable reviewed lbws chances, that don't match the ball tracking. I had a catch that was celebrated but Tim Paine stayed in. There's a lot of times where fielders just don't seem to react to balls in going near them, it'd be nice to at least see an attempt to stop a ball near them or going over their head. Caught and bowled opportunities not even attempted. This is all on fully assisted fielding. The keeper standing further back for medium pacers than fast medium bowlers and not being able to move them up to the stumps is really frustrating.

It could be factors such as difficulty settings, my bowling, the field settings, the conditions or the just the agony of a side batting on a flat pitch but the top skilled players just seem to never appear troubled, ironically, until the ball gets old and it starts to move less. I don't know what other people are experiencing but second innings batting has always been too strong in the previous games for my liking and this was painful. I know cricket can be like that, particularly for England. I can only hope this is a one off otherwise I'll be giving test matches a swerve.


I also got Steve Smith caught behind when he was on 107 and he stayed in. Very depressing to get someone out who is well set and then have them get a second chance
 
After bowling 148 overs I'll take wickets any way I can get 'em, although I think this one would be reviewed.


Dismissals like this just simply didn't exist in the beta, or in the release build. i've had a couple myself in the latest build.

Everything that has happened to this game post-release has been a travesty.
 
Dismissals like this just simply didn't exist in the beta, or in the release build. i've had a couple myself in the latest build.

Everything that has happened to this game post-release has been a travesty.

So disappointing to read this ......
 
Dismissals like this just simply didn't exist in the beta, or in the release build. i've had a couple myself in the latest build.

Everything that has happened to this game post-release has been a travesty.

It's so close to being a great game though. I really hope that the build you were playing on comes back in the next patch.

One thing that has irritated me, that the Bairstow "catch" reminds me of, is the number of one-handed catches that are taken and the ridiculousness of the fielder running after the ball when in flight, catching up with it and then taking it.

These were issues in DBC17 and don't seem to have been dealt with.

What is nice is that the bat-pad smash, which made DBC17 unplayable (or very frustrating) is gone.
 
**Long post warning**

Dismissals like this just simply didn't exist in the beta, or in the release build. I've had a couple myself in the latest build.

Everything that has happened to this game post-release has been a travesty.

It's a shame to hear that but equally not that surprising, these things happen with games. I get the impression the shorter forms of the game were not as rigourously tested during beta as test match and maybe trying to make improvements to them has had a knock on effect? There's bound to be things that pop up that just simply didn't happen or got missed until a larger player base started playing. I just bowled 167 overs, how that experience be unique for everyone without there being the odd bug or eye brow raising moment? I really thinkg anyone that expects otherwise needs to lower their expectations. What I look for is not a perfect recreation of cricket but one that at least provides excitement and competitiveness.

That video is weird for several reasons - the fact that it isn't out only being a small one to me. That there's no review and Bairstow's hurried movements are worse to me. I can accept some of the more weird looking catches, like @Mondy mentioned, because I think they must be a case of animations not quite being able to recreate the situation that is happening. I always go from the position of: does that feel like a genuine dismissal even if it looks a bit off? That was why the bat pad smash was so problematic. It looked bad and felt cheap. Although I did one get one bat pad smash in ths match, btw, it too completely ruined DBC 17 test matches for me.

It's weird having the AI score 602 against you, I think on '17 they scored 250-300 once, every other time I got a collapse from 20 overs onwards usually accompained by half a dozen bat pad smashes. So, I appreciate the fact they are stronger and grinding out in the field is realistic, if horrible. The issues are that there was barely a mistake. Thinking about Cook's 200 the other day he was dropped twice, ignoring the fact I've seen one drop in the game since I started playing, it would be good to at least feel like chances are there. Playing with fully assisted fielding I'd get so pissed off if there was a drop but that's cricket.

And I think confidence is set too high. It seems like if player faces 30-50 balls, not matter how well they did they come out batting with little problem in a second innings. The balance with bowlers seems off as well. I had Cummins take a wicket with first ball against me and his confidence didn't go to green until he got a second wicket with his fourth ball. Starc and Hazlewood both finished their first spell before they were 'green' confident (which could be fine) and Mitch Marsh was fully confident (going off the colours) after about two overs. A consitent progression is good but I think it should be far more erratic at the start of an innings or spell. I don't know if it's changed, other than you get the colours instead of a number, but going off that colour coded system I'd prefer to see:

Red - Not confident/completely vulnerable
Orange - Little confidence/unsettled
Amber - Start of an innings or bowling spell/getting settled
Light Green - Quite confident and almost settled
Full Green - Confident and Settled

Maybe throw in a system to that means for a couple of balls a batsman/bowler can be completely unsettled or completely confident, after an edge or getting by a bouncer. They can go from full green to a 'pulsing red' (a subtle flash or something) to indicate they are vulnerable and temporarily at risk so you can better target them or a 'pulsing green' to show they are on high and you might want to be more cautious. Depending on the mentality you might get different reactions, a player going into their shell or getting out from trying another big shot. The same could apply to bowlers after they get a wicket, bowl a couple of beauties or get smashed for a couple of boundaries. They could potentially help with bowling changes or selections from the AI - less likely to bowl a player in the red or take off a player who is 'pulsing red'. As it is, even if you completely hammer a player they'll come back on at some point in the rotation. The AI should bring on a Smith or a Malan if it reaches that point where a fourth/ffith bowler having a bad game is perhaps too much of a risk not just keep rotating the main bowlers regardless of how they've done.
 
BTW that dismissal was there in DBC 17 as well..Same thing happens..Only pad and AI plays cut and get out as caught...Few issues like this have carried over from 17...Though like Blocker said the release version seemed the best version of the game so far..Atleast in regards to varied dismissals...
 

Users who are viewing this thread

Top