Steam update for DBC17 released

[Mr Snrub]

I've had a lot of run outs, particularly in T20, in comparison to '14 where I probably had five in my entire time playing it. There are some crazy instances where they end up dancing around the middle of the pitch not knowing which way to go but that at least feels realistic, even though it can look a little silly.

More chances would be nice, particularly towards the end of innings when chasing or pushing for extra runs. There are a lot of occasions where two is possible and they settle for one. I think I had one match where they needed 3 off the last ball and settled for one. In that instance there was at least a 50/50 chance of 2 which would have meant a super over.

I'm not sure how you do it without throwing the balance off entirely. I know the throwing can be a little irritating (the loopy throws) but I'm not sure if that is a gameplay quirk, down to skills or quality/timing of user input when throwing.

That three off the last ball situation is something where clearly the programming needs to include last ball scenarios and the batsmen should run. I agree that the factor of an icreasing run rate and the approaching end of innings should also be factors in making batsmen decide to have a crack, along with how many wickets are still in hand.

Ok so re the bat pads- anyone think a slider for bounce off pads might help with the issue? This gives one the option to turn it down and tweak it a bit so hopefully there isnt a surfeit of bat pads?

I don't think that's really possible, as the bounce of the pads is a product of the game's physics and (according to some) a certain shot the batsmen go to under pressure. Decreasing the frequency of them might be a bit hard to do when you're dealing with physics that need to be present, you can't just say "it randomly doesn't apply to this ball".

My suggestion wouldn't be the frequency of it as that's a little hard to stop as it depends on what the delivery has done. If possible, I'd suggest changing the gravity and velocity of the ball post a bat-pad slightly so that it dips a little faster (it appears to balloon up at times) and I'd stop the close-in fielders from being able to move more than a step towards the ball for that situation. Once again, that's all dependant on whats possible with the engine.

 

[DeadShot]

Yes. It may raise as an issue/concern post release of patch. Because not everyone are part of this forum and they will not be aware of amount of discussion happened around this. We cannot add disclaimer not to use silly mid-on to enjoy the game. This post is purely keeping in mind of the users outside this forum.

 

[Acid Burn]

Ok so re the bat pads- anyone think a slider for bounce off pads might help with the issue? This gives one the option to turn it down and tweak it a bit so hopefully there isnt a surfeit of bat pads?

This would also not work for the Online Side , where no tinkering of Sliders are possible .

 

[gkvarma18]

Can we expect an update today to address bat pads and other minor things.

 

[wasteyouryouth]

I've had none, and it never even seemed likely. I use semi-assisted fielding and while there were some loopy throws, there was never a scenario where a direct hit would have caused trouble.

Is this affected by difficulty?

With the drop and run scenarios - where the loopy throw usually became most frustrating - after the patches started coming out I did get a run out with the bowler grabbing the ball.

It's possible difficulty has an impact. A lot of my earlier games were on Pro. I've personally found very little difference in match results having played across Pro, Veteran and Legend. What I have noticed is that the higher I go the variety in types of dismissal decreases. This just a thought, I've no evidence, unless someone wants to go through all my scorecard posts on here and try and match it up with what difficulty I've said it was on.

 

[Mr Snrub]

With the drop and run scenarios - where the loopy throw usually became most frustrating

The loopy throws are ridiculous, there's no logic at all behind them. How on earth does the game decide to do a lobbed return like that? Why's it in there at all? There must be some reason escaping me?

 

[Xboxer]

The loopy throws are ridiculous, there's no logic at all behind them. How on earth does the game decide to do a lobbed return like that? Why's it in there at all? There must be some reason escaping me?

They're there for when you don't try to steal a run ?

 

[Mr Snrub]

They're there for when you don't try to steal a run ?

I guess when playing cricket we've all lobbed the ball back to the bowler from 10-20m away, but these things arc too high and trigger when players are actually running, allowing them an easy one when they would be run out.

 

[Langeveldt]

@AnkitC thanks for your findings. I no longer have access to a pc but will only be able to use the PS4, so by then it will be too late to test your theory. Good luck with the fine tuning guys.

 

[Spoobir]

I have had what I consider to be a realistic number of run-outs recently across tests/odi/career mode matches, there is even one at the start of my latest video (below). They can look a little funny and sure the AI running could be a bit smarter but in general it's much better than it was.

 

[Wealey]

Run Outs for me are a bit of a dodgy area. Personally I can live with no Run Outs as I always feel it's quite cheap.

I can 100 % why others would want them. But it seems to be a tough balance between genuine tight run outs caused by brilliant fielding and just fake stupid cock ups by the AI.

In a test for example, they should really be once in a blue moon.

 

[wasteyouryouth]

Run Outs for me are a bit of a dodgy area. Personally I can live with no Run Outs as I always feel it's quite cheap.

I can 100 % why others would want them. But it seems to be a tough balance between genuine tight run outs caused by brilliant fielding and just fake stupid cock ups by the AI.

In a test for example, they should really be once in a blue moon.

I'd worry a tweak would wind up with five or six an innings. I reckon I was seeing 1 every 3 matches on T20. That's compared with 1 every 30+ on '14. A couple of matches I had two in an innings. I've had them in long form games as well.

 

[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.

 

[wasteyouryouth]

That's three bat pad chances (I dropped two) in two overs with one off pace and caught at short mid wicket.

 

[Mr Snrub]

Run Outs for me are a bit of a dodgy area. Personally I can live with no Run Outs as I always feel it's quite cheap.

I can 100 % why others would want them. But it seems to be a tough balance between genuine tight run outs caused by brilliant fielding and just fake stupid cock ups by the AI.

In a test for example, they should really be once in a blue moon.

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".