Steam update for DBC17 released

[wasteyouryouth]

Twitch I'm going to stream some bowling for a couple of hours. Hard/Hard, Legend. Grassy, soft, pristine, heavy cracks. Starting in five minutes. It should be archived too.

There were four bat pad chances, I dropped three. Caught one at short mid wicket.

 

[cricket_online]

Twitch I'm going to stream some bowling for a couple of hours. Hard/Hard, Legend. Grassy, soft, pristine, heavy cracks. Starting in five minutes. It should be archived too.

Watched the twitch live stream and saw SA bundled for 111 in 36 overs. This is the 4th match I've seen on your twitch stream and I've yet to see AI batsmen get to 160. At the moment I think I'll end up simulating the AI innings the way I do now coz based on what I've seen AI is too easy to roll over and expecting them to put up a decent total is asking too much.

 

[blockerdave]

There were four bat pad chances, I dropped three. Caught one at short mid wicket.

Any physics sliders?

What teams are you using? I've just never seen anything like this.

 

[wasteyouryouth]

Any physics sliders?

What teams are you using? I've just never seen anything like this.

I made sure everything was reset to default value before starting.

New Zealand and South Africa done by fissionmailed with Patel and De Bruyn added to NZ and SA, respectively. I'm pretty sure they are just from @Kiko_97 and @Llewelynf domestic teams.

 

[Wealey]

Agree with a lot you say, but run-outs are a part of cricket, a facet that isn't really the appealing essence of cricket for most people, but it's important that it's in there. Once in a blue moon means rare and that would indicate that you might get one every few tests or so, which is totally unrealistic. 2-3 a test (four innings) is quite realistic.

As for fake stupid cock-ups by the AI, I again respectfully disagree. Any wicket against the AI is nearly always going to have some element of a fake stupid cock up. The AI can be programmed to always play safe and always play the best possible shots, but it isn't from Legend on down. No game could be won against an AI that doesn't make a mistake.

Sure you want things to be earned and that's why there needs to be intelligent criteria for achieving a run-out and I hope BA have that as their objective, instead of just choosing to "live with no run outs".

Think you missed point of what I meant. I meant cock up as is programming bu

Any physics sliders?

What teams are you using? I've just never seen anything like this.

Same, I'm not really sure what to say, as my experience is nothing like this

 

[Langeveldt]

I made sure everything was reset to default value before starting.

New Zealand and South Africa done by fissionmailed with Patel and De Bruyn added to NZ and SA, respectively. I'm pretty sure they are just from @Kiko_97 and @Llewelynf domestic teams.

Sorry I left your stream at about 30/2 as we had visitors. Nice to see Bavuma getting clean bowled. As long as that is possible I don't really worry about the amount of it because at least it gives a reason to bowl at the stumps. But yes, a pretty feeble total again. Did you try @AnkitC 's advice of only having a short leg and not a silly mid on? I'll have a watch of the VOD later.

 

[Wealey]

Agree with a lot you say, but run-outs are a part of cricket, a facet that isn't really the appealing essence of cricket for most people, but it's important that it's in there. Once in a blue moon means rare and that would indicate that you might get one every few tests or so, which is totally unrealistic. 2-3 a test (four innings) is quite realistic.

As for fake stupid cock-ups by the AI, I again respectfully disagree. Any wicket against the AI is nearly always going to have some element of a fake stupid cock up. The AI can be programmed to always play safe and always play the best possible shots, but it isn't from Legend on down. No game could be won against an AI that doesn't make a mistake.

Sure you want things to be earned and that's why there needs to be intelligent criteria for achieving a run-out and I hope BA have that as their objective, instead of just choosing to "live with no run outs".

Think you missed my point a little bit, I mean I'm all for genuine looking run Outs where you have executed a throw perfectly and ran them out while trying to pinch a single etc.

But I don't want it to get to the case where like in the last game it's just not remotely realistic. I'd say 3 a test is quite high, I'd be interested to see what the stats actually are.

My point was is an awkward balance.
You don't want the AI to start getting run out 5-6 times.

 

[Moosc]

I actually have the opposite problem. I'm in career mode and have made the ODI's and the shield games as a opener.
When ever I'm batting the other team members fall around me like Autumn leaves. Often we are like 6 for 82 or so and they come into bat playing extravagant shots like we are 600 runs ahead. In one game I was on 42 after 80 balls whilst watching the "Keystone" cops bat at the other end. Despite being really struggling as a team these guys would come in and throw their bat at the first ball they faced hit them for 6 and then get out, caught as usual, the next ball. The AI has no idea of playing safely when you are in trouble.
So we get bundled out for 130 odd and then the AI bats and makes over 500. We are not much better in our second dig and once again we are bundled out around 135. Naturally we get thrashed. So how come they can bat that well on a pitch where the opposition has been bundled out twice in the 130's. Surely a 500 pitch is usually rather like a road and wouldn't have deteriated that quick straight after their innings.

Also To add insult to injury both the number 9 and 10 batsman make centuries. In the next game I made 7 and the 'heroes' make heaps of runs. So my questions are:-
(1) Why do the AI players bat so badly when in a partnership with the human player yet play like Sir Donald when the human is out?
(2) Why do BA continue to allow tailenders who are usually MUGS with the bat to bat like specialist batsmen as it completely destroys the immersion and is simply unfair. In one game we had the AI 5 for 76 and yet they made well over 400 with the number 8, 9 & 10 batsman making 80% of the teams score. This happens often I'm sorry to say.

BYW the statistics in career mode is still messed up as it gives the player's average after dividing the total by completed innings less not outs plus the current innings that you are about to start????? What's that about.

Rant over.

 

[wasteyouryouth]

Sorry I left your stream at about 30/2 as we had visitors. Nice to see Bavuma getting clean bowled. As long as that is possible I don't really worry about the amount of it because at least it gives a reason to bowl at the stumps. But yes, a pretty feeble total again. Did you try @AnkitC 's advice of only having a short leg and not a silly mid on? I'll have a watch of the VOD later.

The collapse starts about 47:30 in.

I think @AnkitC suggested having a forward square leg instead of a mid wicket, which I did (actually is was a backward square leg) for one field with Patel. To my knowledge the field basically sticks for the next batsman when the the other gets out. These are the fields I set when Patel first came on. Bat pads occured with both in the 21st over.

Sorry about the image spam.

Amla field

Duminy field

Fast bowling field to Du Plessis (bat pad to short mid wicket first ball). The pitch was soft, even short balls were only going over at about chest height so I was looking to get them driving.

 

[Langeveldt]

Maybe the short leg at 90 degrees to the batsman is the right way to go here, but I have a feeling we are clutching at straws a bit.

 

[AnkitC]

@wasteyouryouth Both the fields have a Silly Mid On. The problem is bound to happen.

I had clearly mentioned to use a Forward Short instead of a Silly Mid On. And also to use a Backward Mid Wicket instead of a Mid Wicket.

 

[gang_s]

Think you missed my point a little bit, I mean I'm all for genuine looking run Outs where you have executed a throw perfectly and ran them out while trying to pinch a single etc.

But I don't want it to get to the case where like in the last game it's just not remotely realistic. I'd say 3 a test is quite high, I'd be interested to see what the stats actually are.

My point was is an awkward balance.
You don't want the AI to start getting run out 5-6 times.

I agree, the point here is that they should try to pinch a single, or push for a second occasionally depending on the situation. So far I haven't seen one such occurrence. If you tell me the AI runs slightly aggressively on the difficulty levels beyond Veteran, I'll believe you. But Rookie to Veteran, no such luck.

3 in a Test does feel quite high. It should at at least feel like it is possible. For instance, I suck at Free Kicks in FIFA, but I do score about 1 in 8, so I know it can be done.

If I remember correctly, DBC14 also had this timid running initially and a later patch made it more aggressive. After that I would get maybe 1 run-out in 2-3 matches. Now I understand, with the unpredictability of the sport itself, your experience may vary. But I felt dismissal wise, it was much more balanced.

 

[wasteyouryouth]

@wasteyouryouth Both the fields have a Silly Mid On. The problem is bound to happen.

I had clearly mentioned to use a Forward Short instead of a Silly Mid On. And also to use a Backward Mid Wicket instead of a Mid Wicket.

If that's the only solution then all of the field settings with Silly Mid Ons will have to be altered. That second field (Duminy) is one of the defaults.

Also, 9 of those wickets were taken by other methods. So unless it's just coincidentally another low score there's still the issue of the AI capitulating after 15-20 overs.

 

[Wealey]

If that's the only solution then all of the field settings with Silly Mid Ons will have to be altered. That second field (Duminy) is one of the defaults.

Also, 9 of those wickets were taken by other methods. So unless it's just coincidentally another low score there's still the issue of the AI capitulating after 15-20 overs.

Ok heres my theory. The AI will attack gaps in the field. Hence why I always have a pretty attacking field, but one that is realistic to test cricket.

The main region in your field to attack is through midwicket as you pretty much have the offside closed off. Hence your proportion of mid wicked hacks/on drives are going to be quite high!

 

[AnkitC]

If that's the only solution then all of the field settings with Silly Mid Ons will have to be altered. That second field (Duminy) is one of the defaults.

Also, 9 of those wickets were taken by other methods. So unless it's just coincidentally another low score there's still the issue of the AI capitulating after 15-20 overs.

I have not watched the stream so I cannot comment about the other wickets.

But as far as bat pads are concerned, for now we can avoid those by the method I have mentioned a few times already.

And this is not a solution by any means. I have provided enough info for the devs to find the true solution.

Until the issue is solved, it's a workaround which we can use to achieve realistic results.