Ashes Cricket General Discussion

[Deleted member 185125]

Poor Watson . Hussey hit manage to hit a 4 in the last over but then good yorker bowling meant 3 dots in a row to end the match.

Yorkers and bouncers, always reliable.

 

[Nathaus]

Poor Watson . Hussey hit manage to hit a 4 in the last over but then good yorker bowling meant 3 dots in a row to end the match.

Interesting that the 3 top scores for each tam are 1 run apart?

 

[wasteyouryouth]

Interesting that the 3 top scores for each tam are 1 run apart?

I thought that about my scorecard, although pathetic scores they were very similar.

 

[wasteyouryouth]

I couldn't sleep so I thought I'd have another shot at bowling with South Africa and Pakistan in an ODI. This time, to make it fair on the AI after they failed so miserably against me on Legend, and because @Spoobir did, I put it on Pro.

After both results I'm going to go out on a limb here and say that one of three things is going on:

1. The AI cannot bat for shit in powerplays (in total, the last four I've bowled in, the AI has been 192 for 27).
2. I have broken the AI; mentally, physically, emotionally and every other which way.
3. The game evens things up, with the AI giving away wickets, when you bowl second to give you an exciting outcome.

I really hope it's 1 or 2.

That being said, defending a 'smallish' total was quite enjoyable this time. I thought there was no chance, well.. at least until the end of the first over when Pakistan were 2 wickets down and I had that feeling things might just go my way. And at least there were three or four edges.

Spoiler: Full Scorecard

 

[Nathaus]

I hope the crowd got a refund...

 

[trashpanda]

Hey, just wondering how do i play a series and once completed save the statistics of that series. i.e. add wickets to bowlers total wickets taken or hundereds scored?

 

[Spoobir]

I couldn't sleep so I thought I'd have another shot at bowling with South Africa and Pakistan in an ODI. This time, to make it fair on the AI after they failed so miserably against me on Legend, and because @Spoobir did, I put it on Pro.

After both results I'm going to go out on a limb here and say that one of three things is going on:

1. The AI cannot bat for shit in powerplays (in total, the last four I've bowled in, the AI has been 192 for 27).
2. I have broken the AI; mentally, physically, emotionally and every other which way.
3. The game evens things up, with the AI giving away wickets, when you bowl second to give you an exciting outcome.

I really hope it's 1 or 2.

That being said, defending a 'smallish' total was quite enjoyable this time. I thought there was no chance, well.. at least until the end of the first over when Pakistan were 2 wickets down and I had that feeling things might just go my way. And at least there were three or four edges.

Spoiler: Full Scorecard

Wow! It is insane how different an experience this is to what I'm getting.

I have a long-shot, quite absurd theory that I'm not going to voice yet but I will test it a some point today...

 

[Nathaus]

Just saw this on metacritic blurb for Ashes Cricket (I assume it comes from an official BA press release or seomthing):

"Ashes Cricket is the officially licensed video game of cricket's greatest rivalry. Bringing all the fast-paced action, big hits and skill that you see in the greatest cricket competition on earth, in both a more realistic and authentic way than ever before, you'll be able to bathe your team in glory in the men's and women's 2017/2018 Ashes tours. Courtesy of Big Ant's unique photogrammetry technology, Ashes Cricket presents official photorealistic likenesses for all of the Australian and English men's and women's teams -- it will make you feel like you're right there at the live game. Star Test players have been fully motion-captured and you can choose your own batting or bowling style to make your game your own. Big Ant's most detailed and refined cricket engine to date allows for true 360-degree batting. No two players will play the game the same way!"

There you have it - official confirmation that everyone's version has a random number generator in built and the reason some of us get loads of edges and some of us don't. The reason some are seeing scores of 300+ while others bowl out the AI for 50 in ODIs

Edit:

Also found this:
https://www.bigant.com/job/qa-manager/

Seems they've been advertising for 2 months now

 

[wasteyouryouth]

Just saw this on metacritic blurb for Ashes Cricket (I assume it comes from an official BA press release or seomthing):

"Ashes Cricket is the officially licensed video game of cricket's greatest rivalry. Bringing all the fast-paced action, big hits and skill that you see in the greatest cricket competition on earth, in both a more realistic and authentic way than ever before, you'll be able to bathe your team in glory in the men's and women's 2017/2018 Ashes tours. Courtesy of Big Ant's unique photogrammetry technology, Ashes Cricket presents official photorealistic likenesses for all of the Australian and English men's and women's teams -- it will make you feel like you're right there at the live game. Star Test players have been fully motion-captured and you can choose your own batting or bowling style to make your game your own. Big Ant's most detailed and refined cricket engine to date allows for true 360-degree batting. No two players will play the game the same way!"

There you have it - official confirmation that everyone's version has a random number generator in built and the reason some of us get loads of edges and some of us don't. The reason some are seeing scores of 300+ while others bowl out the AI for 50 in ODIs

Thing is we might not play the game the same way, but I'd disagree with @Spoobir when he says we had a different experience. When you look at the results, high scoring or low scoring they were all close finishes. So maybe the only real difference between his game and mine is that I've found a way to get wickets easily. Then the game responds by trying to make it a contest by giving away wickets, or not in his case, and you get a close finish.

The problem is 75% of the wickets look cheap and unrealistic so it just looks phony. I know I'm not alone in experiencing the AI just giving it away with a stupid dismissal at random times, or as someone said the other day (can't remember who) that even if you drop a chance, another will come along very soon.

In fact, the only time I can remember losing a match heavily is when I've batted second. Everything else seems to be a close finish - even when trying to defend 44. To me at least, that suggests the AI has no gauge for what I'm gonna do and if I bat second and, as is usual lose wickets because of errors on my part; bad shots, poor timing, trying a slog. Then it looks like a heavy defeat and a mismatch. Unlike batting, where the AI teams could easily give wickets away, it has no way to force me to get out - it's not like the AI ever bowls anything remotely challenging that leaves me thinking 'I could've done nothing to prevent that wicket.' But if you bowl second (having batted or bowled first like we did) it has something to target - a run chase or a collapse.

This isn't a unique experience for me on Ashes either, it was similar on DBC 17 and I can remember similar things happening way back on 14. I'm sure this will be an unpopular opinion with some but when a game is released with so many bugs and issues (the same happened to me before any patches on DBC 17), but I'm still seeing close finishes and tight contests, I start to wonder what's more likely: the game is good enough to still produce realistic results and close finishes despite all the other issues it has, or there's some element sitting there, working regardless of other problems, that creates 'good' matches?

Like I said when I posted those three theories with that scorecard, I really hope it's 1 or 2 cause they can be fixed. If it's three, it must be a fundamental part of how the game works and makes me question whether there is any 'game' in it at all or if it's just a sophistocated simulator and all we are getting is the output in response to whatever we do presented in the most exciting (if not convincing) fashion possible. I do hope I'm wrong, but the more I play the more this pattern persists regardless of difficulty, teams, skills levels, conditions.

 

[Spoobir]

Thing is we might not play the game the same way, but I'd disagree with @Spoobir when he says we had a different experience. When you look at the results, high scoring or low scoring they were all close finishes. So maybe the only real difference between his game and mine is that I've found a way to get wickets easily. Then the game responds by trying to make it a contest by giving away wickets, or not in his case, and you get a close finish.

I don't know, the other game I posted the team batting first won by 48 runs, which isn't exactly that close or exciting. You may be right that there is something to prevent total blow-outs however.

 

[Master Khan]

I couldn't sleep so I thought I'd have another shot at bowling with South Africa and Pakistan in an ODI. This time, to make it fair on the AI after they failed so miserably against me on Legend, and because @Spoobir did, I put it on Pro.

After both results I'm going to go out on a limb here and say that one of three things is going on:

1. The AI cannot bat for shit in powerplays (in total, the last four I've bowled in, the AI has been 192 for 27).
2. I have broken the AI; mentally, physically, emotionally and every other which way.
3. The game evens things up, with the AI giving away wickets, when you bowl second to give you an exciting outcome.

I really hope it's 1 or 2.

That being said, defending a 'smallish' total was quite enjoyable this time. I thought there was no chance, well.. at least until the end of the first over when Pakistan were 2 wickets down and I had that feeling things might just go my way. And at least there were three or four edges.

Spoiler: Full Scorecard

Won't be surprise if Pakistan does this in real life.

 

[Spoobir]

Alright, testing my stupid theory and it seems like a dud. Same conditions and now using the same teams as @wasteyouryouth. I was even bowling the cutters like you said and I just don't get these collapses in the PP.

 

[hammadahmed88]

Hello,
To all career mode pacers, are you picking up wickets in test matches and first class via edges to slips and keeper? I don't seem to get any. May be my bowler is not skilled enough? How do you get your wickets then?

 

[wasteyouryouth]

Alright, testing my stupid theory and it seems like a dud. Same conditions and now using the same teams as @wasteyouryouth. I was even bowling the cutters like you said and I just don't get these collapses in the PP.

I noticed you saying before that you had reduced revolutions for seam. I'm playing on default. That's partly how I discovered the cutter variation because I was trying to reduce the extreme movement of the default cutters.

 

[Spoobir]

Alright after Pakistan were 94-2 I took control and ran them all out for 105. Time to see if SA collapse in the chase.