Ashes Cricket General Discussion

Nice to see so much work being done in balancing the game. Hopefully they will get to AI feild placements and AI batting approach at some point
 
Didn’t no AI field placements was as issue??
Hi Wealey,

Do you see the bowl reversing once its old? If so, do you do it with seam positioning or just the default in-swing/out-swing selection? And does in-swing means in-swing even when its reversing?
 
Anyone batted 4th in FC or 2nd in ODI to see if they've fixed the logic Mikey said wasn't there but obviously is?
 
Really looking forward to an improved version of the current game - from what I have read and seen in this thread recently, it's looking promising. Not played Ashes in months so going back to it will feel like a 'new' game.
 
Bowling: Hard Veteran

India in deep doggy doo doo at lunch. Edges galore, plays and misses, rapping the pad constantly. Some of the best drives I have ever seen in a cricket game, a few lofted drives straight down the ground. One from Kohli, the set batsmen, one from Pandya, set to aggressive, and an earlier one, cant remember who. If not for the 2 boundaries from Saha just before lunch, one a whip through square leg, and the other a edge through the gully region, they would have been 100/6.

Oh and there was an inside edge that went for 4 just wide of the keeper on the leg side. BEAUTY!

3 to gully, 2 to slip and a zinger from Steyn to Ashwin to remove his off stump. This might be it.



upload_2018-2-26_1-1-20.png

upload_2018-2-26_1-1-31.png

upload_2018-2-26_1-1-42.png
 
Bowling: Hard Veteran

India in deep doggy doo doo at lunch. Edges galore, plays and misses, rapping the pad constantly. Some of the best drives I have ever seen in a cricket game, a few lofted drives straight down the ground. One from Kohli, the set batsmen, one from Pandya, set to aggressive, and an earlier one, cant remember who. If not for the 2 boundaries from Saha just before lunch, one a whip through square leg, and the other a edge through the gully region, they would have been 100/6.

Oh and there was an inside edge that went for 4 just wide of the keeper on the leg side. BEAUTY!

3 to gully, 2 to slip and a zinger from Steyn to Ashwin to remove his off stump. This might be it.



View attachment 206022

View attachment 206023

View attachment 206024

I don't want to piss on your chips but I'd reserve judgement until you've played the full match. A lot of my frustrations with the live version come from the 2nd AI innings. No idea if it's to do with pitch conditions or what but that's how it is.
 
I don't want to piss on your chips but I'd reserve judgement until you've played the full match. A lot of my frustrations with the live version come from the 2nd AI innings. No idea if it's to do with pitch conditions or what but that's how it is.
I have every intention to finish this match. I know many have said ai 2nd innings have been bollocks. One thing I can say is this just feels better.
 
Good to know a patch is coming after all and that would bring me to play Ashes Cricket once again. A few questions to beta testers:

-Do the gameplay modifier sliders, "especially physics" have a real effect ingame? I mean can i create a pitch condition similar to "Bangladesh vs Srilanka 2nd test", where spinners dominated from day1 or "Bangladesh vs Srilanka on tri-nation series final", where both seamers and spinners were equally dangerous. I would like to play in those tough conditions and you know scoring a 50 in those condition is more satisfying than scoring a 200 in batting paradise imo.

-Does the AI send an offspinners to left hand batsmen more often?

If possible, I have a few requests as well:

- Can we have a field without lawn stripes.

- An ingame editor to edit generated players name and appearence in career mode.
 
The only thing I would have said is that a particular fix couldn't fix already incorrect stats on a player.

In case I haven't explained previously, the reason for the difficulty here is that the stats get recorded as the match goes on - so if something is wrong like the count of 50s or whether a high score is correctly recorded as not out, comes down to the specific circumstances of the end of the innings or dismissal. To fix the remaining stats issues it comes down to finding those exact circumstances where it goes wrong, they all can be fixed, but it's a matter of tracking the remaining cases down.

Perhaps BigAnt can ship off the code to a company with the competency and decency to fix it.

Nah. They're only paying customers, right?
 

Users who are viewing this thread

Top