Luckily you have been giving us the most feedback lately in this thread...
PC Public Preview Update Now Available
- Thread starter MattW
- Start date
Luckily you have been giving us the most feedback lately in this thread...
Increasing the slider will result in actual increase in pace however the speedometer will still show the old speeds , can't put it more simple than that.
I don't want to see the meter as 200Kph. The problem is I can't even feel the difference. Because I can hit sixes easily even after changing the slider to 80 in Legend mode. Almost every ball goes for six. How can I feel the difference ??
Spoobir
Thread of the Month March 2018
- Joined
- Feb 18, 2007
D
Dutch
Guest
Ball go faster. Numbers not.
yep you managed to make it more simple.....now the cat is really scared of me!
Do me a favour send us a video of you hitting sixes all round the ground, at legend hardest
sahil1087
Associate Cricketer
- Joined
- Jul 12, 2008
- Location
- Toronto, Canada
- Online Cricket Games Owned
- Don Bradman Cricket 14 - Xbox 360
Latest build tested for few hours again (T20) @MattW. Please don't hate me for repeating myself again lol.
Sorry guys, I might repeat the same points from last time but it's just for everyone to stay updated. I just want to make sure that everyone who is only on PS4 knows what is happening as I can understand their curiosity but since I play Ashes on both PC and PS4, I can relate to it much better.
First of all, great job again as usual.
Fixes
1) The edges were improved in previous update and I am definitely enjoying it even more now.
2) Those dropped catches are amazing as mentioned before.
3) The line and length bowled by Human bowlers is now making AI think which is what I wanted to see from a long time. It doesn't seem pre meditate now,
Example - If I bowl slow, they do get confused (specially if they loose quick wickets) and are under pressure. This is simply amazing
4) The lines bowled by AI bowlers are better
5) We do see Replays after every boundary which is back
6) Edges do carry to the keeper/slips which is amazing. I see that wickets are playing a big part in the gameplay.
7) Now if AI hits a ball in the air, it won't necessarily go for a six or a boundary. The odds of AI getting caught outside the circlet are a lot more which is
great to see as well
8) Variety of dismissals in a single game
Issues
1) Commentary issue
a) Every time if a ball bounces just in front of the fielder and if fielder misfields, commentator goes "Oh, he has dropped it" and they show a replay even if it's clearly not a catch.
b) On many occasions, the commentator goes "Did not time the ball in middle of the bat". Please fix that
c) Every time the commentator talks about field restrictions ending prior to the actual over. Ex- If restrictions end after 6 overs, commentator will announce that after 5 overs. This issue is there from a long time.
2) The animation for straight drive is still the same. (Looks like a cover drive but ball goes straight)
3) Scoop shot animation/power issues
4) Upper square cut animation looks weird. Can we add the late upper cut or something please?
5) Can we have top edges from a pull/hook/cut go for six. Haven't seen that happen yet.
6) The flick shot is going for bat pad (even on Ideal/Good timing) on many occasions. Please fix that.
7) The on side drive is a bit low on power. I personally felt that. Would like to see more people comment on that.
8) On many occasions, if there was a run out opportunity created at bowlers end, AI would throw the ball to the bowler rather than attempting a direct hit.
9) Not sure if we are getting replays for LBW's. Please take a look
Major Pending items (No updates from Big ant on that)
1) Batsmen turning back issue (going on from a long long time). Batsman is still taking time when a run is canceled on many occasions.
2) Batsmen still walks out of his crease when a ball is left
3) Commentary issues
a) When I hit a back foot pull, on few occasions the commentator goes "A back foot square cut"
b) When a new commentator is introduced, all they say is "hello, good morning" and go quiet. (They should talk a bit about the game)
This one could be an enhancement
c) Commentators must have some sort of discussions (game analysis, previous games, generic chat, cricket/non cricket related conversations) etc.
Sorry guys, I might repeat the same points from last time but it's just for everyone to stay updated. I just want to make sure that everyone who is only on PS4 knows what is happening as I can understand their curiosity but since I play Ashes on both PC and PS4, I can relate to it much better.
First of all, great job again as usual.
Fixes
1) The edges were improved in previous update and I am definitely enjoying it even more now.
2) Those dropped catches are amazing as mentioned before.
3) The line and length bowled by Human bowlers is now making AI think which is what I wanted to see from a long time. It doesn't seem pre meditate now,
Example - If I bowl slow, they do get confused (specially if they loose quick wickets) and are under pressure. This is simply amazing
4) The lines bowled by AI bowlers are better
5) We do see Replays after every boundary which is back
6) Edges do carry to the keeper/slips which is amazing. I see that wickets are playing a big part in the gameplay.
7) Now if AI hits a ball in the air, it won't necessarily go for a six or a boundary. The odds of AI getting caught outside the circlet are a lot more which is
great to see as well
8) Variety of dismissals in a single game
Issues
1) Commentary issue
a) Every time if a ball bounces just in front of the fielder and if fielder misfields, commentator goes "Oh, he has dropped it" and they show a replay even if it's clearly not a catch.
b) On many occasions, the commentator goes "Did not time the ball in middle of the bat". Please fix that
c) Every time the commentator talks about field restrictions ending prior to the actual over. Ex- If restrictions end after 6 overs, commentator will announce that after 5 overs. This issue is there from a long time.
2) The animation for straight drive is still the same. (Looks like a cover drive but ball goes straight)
3) Scoop shot animation/power issues
4) Upper square cut animation looks weird. Can we add the late upper cut or something please?
5) Can we have top edges from a pull/hook/cut go for six. Haven't seen that happen yet.
6) The flick shot is going for bat pad (even on Ideal/Good timing) on many occasions. Please fix that.
7) The on side drive is a bit low on power. I personally felt that. Would like to see more people comment on that.
8) On many occasions, if there was a run out opportunity created at bowlers end, AI would throw the ball to the bowler rather than attempting a direct hit.
9) Not sure if we are getting replays for LBW's. Please take a look
Major Pending items (No updates from Big ant on that)
1) Batsmen turning back issue (going on from a long long time). Batsman is still taking time when a run is canceled on many occasions.
2) Batsmen still walks out of his crease when a ball is left
3) Commentary issues
a) When I hit a back foot pull, on few occasions the commentator goes "A back foot square cut"
b) When a new commentator is introduced, all they say is "hello, good morning" and go quiet. (They should talk a bit about the game)
This one could be an enhancement
c) Commentators must have some sort of discussions (game analysis, previous games, generic chat, cricket/non cricket related conversations) etc.
Last edited:
CaptainOZ
Panel of Selectors
- Joined
- Jun 2, 2004
Lol
gkvarma18
International Cricketer
- Joined
- Jun 29, 2016
- Location
- Hyderabad , India
- Profile Flag
- India
- Online Cricket Games Owned
- Don Bradman Cricket 14 - Steam PC
First of all thanks to Ross and MattW for this kind of rapid support to the game.I played 2 odis with Veteran hard difficultly on latest preview build and my short feedback is
1)Human edges are excellent now as mistimed hits leading to edges .Great work done.
2) Frequently flick shots hitting the pads first
3) Front foot pull shots and leg glances are needs to be improved further.
4) Battings seems to have taken nice step now as any mistimed hits getting nicks .
5) Important thing needs improvement is Weather as i played in overcast and showers conditions but sun is shining and shadows are bright.
6) So my opinion few things like ondrives , flicks , front and backfoot pull shots needs to have look please .
Anyhow game is way better now with this support by BAS.
1)Human edges are excellent now as mistimed hits leading to edges .Great work done.
2) Frequently flick shots hitting the pads first
3) Front foot pull shots and leg glances are needs to be improved further.
4) Battings seems to have taken nice step now as any mistimed hits getting nicks .
5) Important thing needs improvement is Weather as i played in overcast and showers conditions but sun is shining and shadows are bright.
6) So my opinion few things like ondrives , flicks , front and backfoot pull shots needs to have look please .
Anyhow game is way better now with this support by BAS.
Last edited:
wasteyouryouth
Verified
I'm playing for the first time in a couple of weeks, first time ODI for even longer and it's been a fascinating innings of bowling so far.
5th one is really needed. It was not implemented even in DBC 14 and DBC 17.
It is badly needed.
And another is DLS system is also need to be improved. they just reduce 20% of the over if there is a shower. It is also not realistic.
@MattW please have a look at these. please. gameplay is looking far better now. But please improve these things.
wasteyouryouth
Verified
Took a break from gorging on chicken dinners on PUBG and I bowled an innings, just one, I'm hoping to do more. But here's some feedback.
Background: set up a tour (3 ODI, 2 Tests) in Bangladesh against Afghanistan - these are teams I have skilled myself. Fielding skills all set to 50, Judgement set to a batting rating I give them, Agility 50, Cardio & Aerobic 70, Pace 50, Strength between 55-65 (depending on mentality). Veteran - Hard for everything else. Swing set to 100 (there was a nice amount in the match).
I made some notes so excuse anything a little vague and cluttered.
Overall - it was very interesting to see an ODI innings play out this way. It seemed like a struggle for the batting side, to get runs. A lot of shots straight to the infielder, although there did seem to be more quick singles. A LOT of dot balls though. Granted a lot of this could be down to the attributes I have these players at but it was at least different to what I've had before on the game in ODI (bowling the AI out within 40 overs and taking 4-5 wickets in a powerplay.
Video of the full innings
Background: set up a tour (3 ODI, 2 Tests) in Bangladesh against Afghanistan - these are teams I have skilled myself. Fielding skills all set to 50, Judgement set to a batting rating I give them, Agility 50, Cardio & Aerobic 70, Pace 50, Strength between 55-65 (depending on mentality). Veteran - Hard for everything else. Swing set to 100 (there was a nice amount in the match).
I made some notes so excuse anything a little vague and cluttered.
Afghanistan elected to bat.
First boundary didn't come until the third over.
5 overs: 22/1
There was notably not a single shot in anger (supermen slog shots). Naib still got some boundaries but it was a cautious pace. There were a lot of drives to infielders (something that occured throughout the innings).
10 overs: 46/1
Rahmat Shah did not get to green until his 42nd ball (13 not out), sadly the next ball he was out caught off his pad (bug).
The first really aggressive looking shot didn't come until the 20th over, this was off a weak/late delivery.
20 overs: 71/3
First six in the 22nd over - Nabi on a ideal/perfect ball (I say this not to point anything out really just as a point of reference)
23rd over - aggressive - over the infield shot
24th over - Nabi trying this again - down the ground - was caught by mid on running backwards.
30 overs: 99/4
Shenwari took 39 balls to get to green and played fairly consistently. I would like to have seen what he'd have done in the last 5 overs, set the only serious batsman left - more on that later.
30th over - Najibullah Zadran came in - there was a lot of shouting 'yes' for singles but not taking them (not sure if this could be something to do with his mentality - aggressive). He started hitting a few boundaries, including reverse sweep slogs. Felt like a lower/middle order batsman coming in and looking to move things forward. He scored at a run a ball before getting out. He got to green after 17 balls.
Shenwari's first boundary came after 56 deliveries - he was still playing defensive shots in the 39th over (good/bad I don't know).
40 overs: 141/6
Shenwari got his 50 from 82 balls a strike rate of 60.98, not bad considering his real life ODI strike rate is 64.6 and setting him as Precise is based on real life strike rates. Like I said it'd have been interesting to see where he'd have finished but he got run out. A new and interesting calamitious one. Where both batsman took a run, were safely in their crease and then Shenwari (non-strikers end) decided to set off just as the bowler had the ball in hand from the fielder's throw - 174 was the score if you want to see from the video below.
Afghanistan were all out for 182 from 48.2 overs.
First boundary didn't come until the third over.
5 overs: 22/1
There was notably not a single shot in anger (supermen slog shots). Naib still got some boundaries but it was a cautious pace. There were a lot of drives to infielders (something that occured throughout the innings).
10 overs: 46/1
Rahmat Shah did not get to green until his 42nd ball (13 not out), sadly the next ball he was out caught off his pad (bug).
The first really aggressive looking shot didn't come until the 20th over, this was off a weak/late delivery.
20 overs: 71/3
First six in the 22nd over - Nabi on a ideal/perfect ball (I say this not to point anything out really just as a point of reference)
23rd over - aggressive - over the infield shot
24th over - Nabi trying this again - down the ground - was caught by mid on running backwards.
30 overs: 99/4
Shenwari took 39 balls to get to green and played fairly consistently. I would like to have seen what he'd have done in the last 5 overs, set the only serious batsman left - more on that later.
30th over - Najibullah Zadran came in - there was a lot of shouting 'yes' for singles but not taking them (not sure if this could be something to do with his mentality - aggressive). He started hitting a few boundaries, including reverse sweep slogs. Felt like a lower/middle order batsman coming in and looking to move things forward. He scored at a run a ball before getting out. He got to green after 17 balls.
Shenwari's first boundary came after 56 deliveries - he was still playing defensive shots in the 39th over (good/bad I don't know).
40 overs: 141/6
Shenwari got his 50 from 82 balls a strike rate of 60.98, not bad considering his real life ODI strike rate is 64.6 and setting him as Precise is based on real life strike rates. Like I said it'd have been interesting to see where he'd have finished but he got run out. A new and interesting calamitious one. Where both batsman took a run, were safely in their crease and then Shenwari (non-strikers end) decided to set off just as the bowler had the ball in hand from the fielder's throw - 174 was the score if you want to see from the video below.
Afghanistan were all out for 182 from 48.2 overs.
I could move fielders on a free hit (I don't know if that's still a rule).
Edges were there, had a couple of catches from them and some that went safe. It felt like a decent amount.
For almost all of the innings after the powerplay I had three men out, occasionally four. Granted I was on top and taking wickets but it would be interesting to see if other players/teams would take advantage of the opportunity to hit over the top more often.
Edges were there, had a couple of catches from them and some that went safe. It felt like a decent amount.
For almost all of the innings after the powerplay I had three men out, occasionally four. Granted I was on top and taking wickets but it would be interesting to see if other players/teams would take advantage of the opportunity to hit over the top more often.
Overall - it was very interesting to see an ODI innings play out this way. It seemed like a struggle for the batting side, to get runs. A lot of shots straight to the infielder, although there did seem to be more quick singles. A LOT of dot balls though. Granted a lot of this could be down to the attributes I have these players at but it was at least different to what I've had before on the game in ODI (bowling the AI out within 40 overs and taking 4-5 wickets in a powerplay.
Video of the full innings
Are you going to Bat or Bowl for Bangladesh?Took a break from gorging on chicken dinners on PUBG and I bowled an innings, just one, I'm hoping to do more. But here's some feedback.
Background: set up a tour (3 ODI, 2 Tests) in Bangladesh against Afghanistan - these are teams I have skilled myself. Fielding skills all set to 50, Judgement set to a batting rating I give them, Agility 50, Cardio & Aerobic 70, Pace 50, Strength between 55-65 (depending on mentality). Veteran - Hard for everything else. Swing set to 100 (there was a nice amount in the match).
I made some notes so excuse anything a little vague and cluttered.
Afghanistan elected to bat.
First boundary didn't come until the third over.
5 overs: 22/1
There was notably not a single shot in anger (supermen slog shots). Naib still got some boundaries but it was a cautious pace. There were a lot of drives to infielders (something that occured throughout the innings).
10 overs: 46/1
Rahmat Shah did not get to green until his 42nd ball (13 not out), sadly the next ball he was out caught off his pad (bug).
The first really aggressive looking shot didn't come until the 20th over, this was off a weak/late delivery.
20 overs: 71/3
First six in the 22nd over - Nabi on a ideal/perfect ball (I say this not to point anything out really just as a point of reference)
23rd over - aggressive - over the infield shot
24th over - Nabi trying this again - down the ground - was caught by mid on running backwards.
30 overs: 99/4
Shenwari took 39 balls to get to green and played fairly consistently. I would like to have seen what he'd have done in the last 5 overs, set the only serious batsman left - more on that later.
30th over - Najibullah Zadran came in - there was a lot of shouting 'yes' for singles but not taking them (not sure if this could be something to do with his mentality - aggressive). He started hitting a few boundaries, including reverse sweep slogs. Felt like a lower/middle order batsman coming in and looking to move things forward. He scored at a run a ball before getting out. He got to green after 17 balls.
Shenwari's first boundary came after 56 deliveries - he was still playing defensive shots in the 39th over (good/bad I don't know).
40 overs: 141/6
Shenwari got his 50 from 82 balls a strike rate of 60.98, not bad considering his real life ODI strike rate is 64.6 and setting him as Precise is based on real life strike rates. Like I said it'd have been interesting to see where he'd have finished but he got run out. A new and interesting calamitious one. Where both batsman took a run, were safely in their crease and then Shenwari (non-strikers end) decided to set off just as the bowler had the ball in hand from the fielder's throw - 174 was the score if you want to see from the video below.
Afghanistan were all out for 182 from 48.2 overs.
I could move fielders on a free hit (I don't know if that's still a rule).
Edges were there, had a couple of catches from them and some that went safe. It felt like a decent amount.
For almost all of the innings after the powerplay I had three men out, occasionally four. Granted I was on top and taking wickets but it would be interesting to see if other players/teams would take advantage of the opportunity to hit over the top more often.
Overall - it was very interesting to see an ODI innings play out this way. It seemed like a struggle for the batting side, to get runs. A lot of shots straight to the infielder, although there did seem to be more quick singles. A LOT of dot balls though. Granted a lot of this could be down to the attributes I have these players at but it was at least different to what I've had before on the game in ODI (bowling the AI out within 40 overs and taking 4-5 wickets in a powerplay.
Video of the full innings
wasteyouryouth
Verified
I started to have a bat but it was annoying and I was crap, so I rage quit.
Similar threads
