This is it - Ashes Cricket (Beta Feedback)

[Gamer Pradosh]

Although I don't have any issues with either the spinner bowler going too wide or now it being restricted, I doubt the team at BA would blindly make changes just because a couple of guys "moaned" about it. Surely they would do it only if they find a tiny bit of merit to the issue?

This I agree..

 

[Wealey]

Have you guys ever had a bowled off AI leaving the ball, with the ball seaming in and clipping to top of the off stumps?

No, it's a fine balance with getting a robust competitive AI and every dismissed variant

 

[Gamer Pradosh]

No, it's a fine balance with getting a robust competitive AI and every dismissed variant

Yeah varied is always preferred over anything else anyday.. But in DBC there always felt like ah man if that had just seamed a slightly bit that would have been a stunning wicket...I feel we would ultimately get to a stage where we would be discussing the softness level of pitch could be set as other stuff would have been covered, as we go on this series and the travel along BA...Its one heck of an experience connected to a gaming series this well..

 

[blockerdave]

Wasn't just pointed out was then pointed out again once we explained he reasons etc.

Let's move on

yes lets...

to push away the negativity, i'd just say last night i got to to play the game on a new system, so not looking at my lowered settings small screen pc that i'm worried is going to overheat if i play too long.

it was amazing.

put in to bat on a grassy Gabba, under (beautiful) overcast skies, after a rain delay cost the first hour or so play, I battled through the short session, scoring slowly but not losing any wickets. Tough test cricket.

Aussies rotated their 3 seamers, only bringing on Lyon after 20 overs, to chants of "Gaaaary, Gaaaary, Gaaaary". Also a bit of "Niiiiice Gary" from the keeper.

Nice opening 50-partnership, Aussies turn to the part-time spin of Maxwell.

Really notice it getting easier as the batsmen get in / ball softens. Conversely, that feeling of needing to start again with a new batsman.

Bat nicely. Finish the shortened day honours even. Bairstow (well set), Ali (slow start) at the crease.

Lose Bairstow early on day 2 to a bad leave. Par score some way off.

Ali and Woakes push up the run rate a little, Ali particularly starts to get after the bowlers, using the extra hardness of the new ball. AI keeps seamers on because of the new ball, but stamina-wise probably should have gone to Lyon? Ali doesn't mind... Woakes goes and Overton plays defensively, supporting Ali.

Ali goes for a big shot too many - castled! Missed out on the hundred but a vital 82.

Broad swipes out, and Overton releashes the shackles, demolishing Hazlewood with some enormous biffs.

England past the 400. All out shortly before lunch.

105 brilliant overs of test match cricket. There may be video of some of this... on Monday

Can't wait to bowl tonight...

 

[Gamer Pradosh]

105 brilliant overs of test match cricket. There may be video of some of this... TODAY

Can't wait to bowl tonight...

Man that was great to read...

PS Correct text a bit for myself...

 

[Spoobir]

yes lets...

to push away the negativity, i'd just say last night i got to to play the game on a new system, so not looking at my lowered settings small screen pc that i'm worried is going to overheat if i play too long.

it was amazing.

put in to bat on a grassy Gabba, under (beautiful) overcast skies, after a rain delay cost the first hour or so play, I battled through the short session, scoring slowly but not losing any wickets. Tough test cricket.

Aussies rotated their 3 seamers, only bringing on Lyon after 20 overs, to chants of "Gaaaary, Gaaaary, Gaaaary". Also a bit of "Niiiiice Gary" from the keeper.

Nice opening 50-partnership, Aussies turn to the part-time spin of Maxwell.

Really notice it getting easier as the batsmen get in / ball softens. Conversely, that feeling of needing to start again with a new batsman.

Bat nicely. Finish the shortened day honours even. Bairstow (well set), Ali (slow start) at the crease.

Lose Bairstow early on day 2 to a bad leave. Par score some way off.

Ali and Woakes push up the run rate a little, Ali particularly starts to get after the bowlers, using the extra hardness of the new ball. AI keeps seamers on because of the new ball, but stamina-wise probably should have gone to Lyon? Ali doesn't mind... Woakes goes and Overton plays defensively, supporting Ali.

Ali goes for a big shot too many - castled! Missed out on the hundred but a vital 82.

Broad swipes out, and Overton releashes the shackles, demolishing Hazlewood with some enormous biffs.

England past the 400. All out shortly before lunch.

105 brilliant overs of test match cricket. There may be video of some of this... on Monday

Can't wait to bowl tonight...

Sounds awesome mate, were you playing an missing a lot in the morning with the clouds and green wicket?

 

[blockerdave]

Sounds awesome mate, were you playing an missing a lot in the morning with the clouds and green wicket?

maybe not as much as it could have been, but pitch was even/no cracks. i think seam movement could be higher as it could have been in 14 and 17.

 

[Wealey]

Pitches as people have said I have banged on about a lot and I think once release is done and the team is a little more relaxed it may get looked at a little more.

I personally want to see a green top seaming visually, jogging back in and away.

It's a work in progress!![DOUBLEPOST=1510318897][/DOUBLEPOST]On that note, I have recorded an ODI innings for the AI! Chopped it up a little a recorded in HD.

I'll try get it out tonight if I can do guys can see how the AI go about their business!

What I wanted to do isn't possible at the moment until Monday.

 

[Spoobir]

maybe not as much as it could have been, but pitch was even/no cracks. i think seam movement could be higher as it could have been in 14 and 17.

Are we talking seam movement from the upright ball? Because at least in DBC17 the cutters used to move miles, I even turned the slider right down it was so exaggerated.

 

[AliKhan215]

Hey guys.

I have a question for you beta boys, not sure you guys will be able to nswer it, but that’s fine too.

In this picture it’s mentioned that there is online co-op (2-4 players)

Is that something that’s a new feature in the game? Can some of you just quickly check if there’s such option in online mode? thanks

@WealeyH @grkrama @Dutch @Llewelynf

 

[MattW]

Although I don't have any issues with either the spinner bowler going too wide or now it being restricted, I doubt the team at BA would blindly make changes just because a couple of guys "moaned" about it. Surely they would do it only if they find a tiny bit of merit to the issue?

The 'merit' is that yes indeed, they were bowling no-balls when the most wide crease approach was chosen.

However, contrary to the original suggestion that this was 'missed' - it was simply a 50/50 decision on whether the exact spot the back foot landed was more important than giving a wider range of crease approaches. Underneath the release point of the ball was not any further out - just that the angle of approach meant the foot landed outside the line. Given that it is mocapped animation, it would be unnatural to solve it by changing where the foot landed, so instead to stop the back foot no ball it meant moving in the widest release point (there are still 3 either side, and it is still wider than the middle point before the change)

And yes, the decision to make the change was very much down to the fact people did notice that they were no-balls and mentioned it - however that does come at the cost of a not insignificant amount of variation of positioning, hence not taking that approach earlier.

 

[wasteyouryouth]

yes lets...

to push away the negativity, i'd just say last night i got to to play the game on a new system, so not looking at my lowered settings small screen pc that i'm worried is going to overheat if i play too long.

it was amazing.

put in to bat on a grassy Gabba, under (beautiful) overcast skies, after a rain delay cost the first hour or so play, I battled through the short session, scoring slowly but not losing any wickets. Tough test cricket.

Aussies rotated their 3 seamers, only bringing on Lyon after 20 overs, to chants of "Gaaaary, Gaaaary, Gaaaary". Also a bit of "Niiiiice Gary" from the keeper.

Nice opening 50-partnership, Aussies turn to the part-time spin of Maxwell.

Really notice it getting easier as the batsmen get in / ball softens. Conversely, that feeling of needing to start again with a new batsman.

Bat nicely. Finish the shortened day honours even. Bairstow (well set), Ali (slow start) at the crease.

Lose Bairstow early on day 2 to a bad leave. Par score some way off.

Ali and Woakes push up the run rate a little, Ali particularly starts to get after the bowlers, using the extra hardness of the new ball. AI keeps seamers on because of the new ball, but stamina-wise probably should have gone to Lyon? Ali doesn't mind... Woakes goes and Overton plays defensively, supporting Ali.

Ali goes for a big shot too many - castled! Missed out on the hundred but a vital 82.

Broad swipes out, and Overton releashes the shackles, demolishing Hazlewood with some enormous biffs.

England past the 400. All out shortly before lunch.

105 brilliant overs of test match cricket. There may be video of some of this... on Monday

Can't wait to bowl tonight...

I'm really interested by the bowler selections and glad you mentioned them. I'm sure I'd seen someone mention before that Lyon had come on first change. So, as far as you can tell does the AI appear to pick it's bowlers based more on the conditions or situation of the game? If circumstances are suited would we see them going to spin earlier and them having lengthy spells rather than just four or five overs then back to the next bowler for four or five overs. I know a lot it would be dependent upon who is set as the opening bowlers but say in the subcontinent would you see the AI go to spin very quickly.

One thing I always felt with DBC 17 was it was far too much of a pattern, e.g. bowlers would be chosen based on skill not based on the situation in the game. So you'd get someone who'd be smashed for 10 an over coming back to finish their spell. Or you'd have top bowlers in a T20 bowling out and then 5th or 6th bowlers bowling at the death.

 

[blockerdave]

I'm really interested by the bowler selections and glad you mentioned them. I'm sure I'd seen someone mention before that Lyon had come on first change. So, as far as you can tell does the AI appear to pick it's bowlers based more on the conditions or situation of the game? If circumstances are suited would we see them going to spin earlier and them having lengthy spells rather than just four or five overs then back to the next bowler for four or five overs. I know a lot it would be dependent upon who is set as the opening bowlers but say in the subcontinent would you see the AI go to spin very quickly.

One thing I always felt with DBC 17 was it was far too much of a pattern, e.g. bowlers would be chosen based on skill not based on the situation in the game. So you'd get someone who'd be smashed for 10 an over coming back to finish their spell. Or you'd have top bowlers in a T20 bowling out and then 5th or 6th bowlers bowling at the death.

yep, this is particularly something i gave feedback on and it was fixed: in a 3 seam 1 spin attack they will rotate seamers early if it's not spin friendly[DOUBLEPOST=1510320511][/DOUBLEPOST]

Are we talking seam movement from the upright ball? Because at least in DBC17 the cutters used to move miles, I even turned the slider right down it was so exaggerated.

yeah

 

[Rhone]

The 'merit' is that yes indeed, they were bowling no-balls when the most wide crease approach was chosen.

However, contrary to the original suggestion that this was 'missed' - it was simply a 50/50 decision on whether the exact spot the back foot landed was more important than giving a wider range of crease approaches. Underneath the release point of the ball was not any further out - just that the angle of approach meant the foot landed outside the line. Given that it is mocapped animation, it would be unnatural to solve it by changing where the foot landed, so instead to stop the back foot no ball it meant moving in the widest release point (there are still 3 either side, and it is still wider than the middle point before the change)

And yes, the decision to make the change was very much down to the fact people did notice that they were no-balls and mentioned it - however that does come at the cost of a not insignificant amount of variation of positioning, hence not taking that approach earlier.

Everyone's happy then. Great that it's been tweaked so soon. I wasn't even sure what a backfoot no ball was until yesterday so at least i've learned a new cricket law from this controversy!

 

[wasteyouryouth]

yep, this is particularly something i gave feedback on and it was fixed: in a 3 seam 1 spin attack they will rotate seamers early if it's not spin friendly[DOUBLEPOST=1510320511][/DOUBLEPOST]

yeah

That's great. But, stop making me want to buy the PS4 version and not wait for Steam.