DBC 17 Batting post Patch 3

[riteshagl]

IMO after patch 3 the batting is more realistic and agree on the above points. Also along with the footwork, it seems the angle of the delivery also determines where the ball ends up.

Even I felt sometimes some shots doesn't go where we intend to play, there needs some tweaking but what I feel difficult or some tweaking required is the batting timer starts way too early. If I watch the line/length/speed/direction and place my foot then I always end up with late timed shot.

I went back to dbc14 to check how it works there, even with the highest difficulty I can time it perfectly by watching the line & length but I like the dbc17 batting much more after patch 3 but only thing is they need to delay the batting timer little bit.

Before patch 2, i think the timing meter was perfect

@funnyadit ,@grkrama , @cricket_online please share your opinion on this

Absolutely agree....spot on...there is hardly any time to try to see all aspects..it mostly results in late timing...patch 2 game speed/timing meter/whatever you call it, was perfect

 

[blockerdave]

You want to revert to old legglance that was unidirectional because of the pull animation it plays now when the ball is way outside off.

Im saying let BA get rid of the pull animation and let the glance remain as it is.

find one post from me, anywhere, about the leg glance and saying it is any different now to prior to the patch. it doesn't exist. my complaint about the pull animation is specifically about the on drive, which i have stated repeatedly. this was never triggered for an on drive pre-patch, and is now triggered regularly for the on drive.

you are actively disrupting / spamming my attempt to report that issue.

 

[grkrama]

again, i had acknowledged that too, and have already reported that the pull shot animation should be removed, even posted a video of how and why and when it occurs.


The difference being you say BA' i get pull shot when i play ondrive FIX '

I say ' BA it occurs when the ball is way outside off and when user attempts to play on drive or legglance it triggers, and mainly when RS is 10'o clock or below, otherwise it plays well.'

Essentially both are same one detailed a bit more on the experience.

Look you are trying to portray me as the villain standing between your issues with the game and BA. I'm NOT.


can we shake hands and move on

 

[blockerdave]

again, i had acknowledged that too, and have already reported that the pull shot animation should be removed, even posted a video of how and why and when it occurs.


The difference being you say BA' i get pull shot when i play ondrive FIX '

I say ' BA it occurs when the ball is way outside off and when user attempts to play on drive or legglance it triggers, and mainly when RS is 10'o clock or below, otherwise it plays well.'

Essentially both are same one detailed a bit more on the experience.

Look you are trying to portray me as the villain standing between your issues with the game and BA. I'm NOT.


can we shake hands and move on

Again with the leg glance. And again obfuscation...

I have acknowledged in my first post (diff thread) about the issue Re the on drive it comes from being outside off. But, and here is the thing, it didn't happen before the patch. Which you wouldn't know because you didn't play it.

Your video of the issue, explanation of the issue is irrelevant and incorrect because it happens to balls just oustide off too. All your "contribution" does is obscure the issue: a negative thing (wrong animation for on drive) has been introduced by the patch. I shouldn't have to repeat that endlessly, but I do because you keep jumping in "yeah leg glance..." and I want to make sure everyone is clear I am not talking about the leg glance, at all.

You don't know that the on drive issue was introduced only by the patch, because you didn't play it before the patch. Yet you keep again spamming and distorting my attempt to report the issue. I reported your previous post about the leg glance, and I will report that one too, because you are trolling my posts now with the leg glance shit.

 

[blockerdave]

I found when I'm trying to drive to mid on and the ball is slightly outside off it does a pull shot. This happens to good/full length balls. The ball always seems to go under the bat which is understandable as it's a pull shot but that shot shouldn't be there when you are trying to drive the ball

A drive slightly outside off... THANK YOU!

but listen to Jeremy Beadle with his home videos and you'd think it only happens to leg glances way outside off.

 

[ndschan]

@BigAntStudios First up great job with the Patch 3. Batting has improved greatly post patch 3 and is freakishly realistic. This is my personal assessment, so may vary depending on user experience. A few things I observed:
1) Batting Difficulty: has increased. Previously I could easily bat at the Hard Level (second from top). It's become quite difficult to time now, good for tests, but not so much for One Days and T20s.
2) Custom Difficulty: Somehow if the marker slider is increased, the camera pans out to Batsmen Far while playing the shot, which is extremely odd.
3) Variations: Batting 360 is now available, and its good. Pitches actually behave differently depending on their characteristics. There were some genuine edges, and its become extremely enjoyable. Although edges on spin bowling are few and mostly are edged to wicket keeper. The Forward Short Leg takes a catch only if its a miss timed pull or a glance.
4) Gameplay settings modifier: One thing that is sorely missed is changing game settings mid match. I used to change it a lot, in test matches, making the pitch worst as game progresses. Also if you select competition you can't customize wicket as per your liking. In essence you get a random wicket to bat on.
5) Skills/Attributes of bowlers and batsmen do matter and play differently depending on their confidence levels. Also the type of bowler changes the bowling strategy. If the fast bowler is brute, he will primarily try to bounce the batsmen out.
6) No-ball byes: Observed a lot of no-ball byes in tests. I mean one off is understandable, but becomes irritating. Another very strange observation: If Player 2 camera is chosen whilst running, the back up fielder just doesn't cover the over throws. The same throw on Player 1 camera is covered aptly.
7) Strange bowling allotment by the AI. Couple of examples: In tests the AI assumes there are just 4 frontline bowlers. The 5th bowler, even if he is a genuine bowler doesn't bowl a single over. In ODIs they are meant to bowl 40 overs and all four frontline bowlers complete their spells till 40. Playing t20 against India would mean, the first three bowlers finish 12, leaving rest 8 to be bowled by remaining 2. Now this wasn't present in Don Bradman 14, so it's surprising how the AI could be dumber than the previous games.

But overall a good patch, looking forward to the next, which I am sure will iron out other sissues.

 

[riteshagl]

I have a similar issue trying to hit a late cut to straight deliveries...the batsman plays a reverse cut...
Also, i feel the batsman tends to hit the ball towards cover more even when you try to hit to extra cover...Not to say that the ball never goes to extra cover, but chances are 70% of the times the ball goes to cover, when you try to hit it to extra cover...I have a similar problem in trying to hit the ball between mid on and midwicket (cow's corner), again chances are 70% of the times the ball goes to midwicket, when you try to hit it to cow's corner...I guess the tolerance range for the input of these shots need to be increased...Then of course the pull shot animation has been discussed so need not add anything...Also, the footwork is too sensitive i feel, so many times i get bowled round my legs trying to leg glace/flick...i love the idea of making footwork important, but its too sensitive at the moment..

 

[mattk]

If footwork is going to be so important (which I'm quite happy with) there needs to be a better way to give feedback. Maybe showing the direction you pressed the left stick and the ideal direction it should have gone for the shot you played.

Edit- More specifically about batting after the patch... it seems to me as having fixed lots of problems but has created lots of new ones. I'm very happy they opened the ground up to the batsman, but in doing so it feels like I've had some control taken away from me. Not really like batting in real life at all (yes I know its a video game).

 

[blockerdave]

i just want to quote the patch 3 release notes:

Update Notes:

GAMEPLAY
Improved shot range
Added detailed information to score HUD
Improve physics detection on stumpings
Corrected an instance of LBW not being called if hitting the batsmans shoe

That is it for gameplay. No mention of changes in footwork, timing etc. So i repeat my question from a few pages ago: is it intentional, or a bug? Is there any point learning this system or will it change again? Because discussion of whether it's better, what input creates or avoids issues etc. is moot.

It was in state A, now it's in state B, but the patch notes don't mention the changes that are obvious to anyone who has played both pre and post patch. So - do I learn state B, or wait for state C? Because when there is silence about the changes, and they go alongside obvious bugs (extension of the pull shot from leg glance to on drive, the introduction of the reverse cut, the introduction of shots going in contra direction to input: all of which are corroborated by multiple sources) my inclination is to assume they were not intentional: that is - footwork and timing weren't supposed to change, but have.

 

[asprin]

To be fair to blockerdave, the changelog states what was done but in this case, I think a more detailed description was the need of the hour. There seems to be a lot of confusion post patch 3 and perhaps BA could throw some light on this.

 

[cricket_online]

Have you thought that maybe its because it might be a hard pitch hence more bounce than a soft pitch?, or that the delivery was too short to play off of the frontfoot? Or that the ball was too wide of off stump?...Maybe it's the game mechanics telling you it wasn't the right ball to attempt playing that shot to!

No I don't think a pull animation when I intend to play an on drive or drive towards widish mid on should be something to do with the pitch or the bounce. If I intend to play a drive it should play like a drive and not a pull. IMO it has more to do with the narrow tolerance range for the on drive and you accidentally go over that range into the "pull shot" territory.

 

[whiteninness]

Yes I think the pull animation should only be triggered if the ball is sufficiently short. The user needs to be helped out a little here.

 

[cricket_online]

Please guys - I want to find out what's going wrong for people here and get things improved - it'd help a lot if you'd all try and stick to constructive discussion of this. In testing so far I've been able to get a few cases where it seemed to go in a different direction than the input - but the more specific examples people can highlight the better.

Matt the biggest issue I've seen so far is the batsman moving way across the off stump leaving stumps exposed behind him and getting bowled. No matter how hard I try I eventually end with this shot animation and it's impossible to build a long innings coz you know eventually you will be dismissed in this fashion. Alternative is to stop playing to the leg side altogether which is not practical. This is my biggest bugbear and I think it could be due to tolerance range level between 12'o clock and 1'o clock on LS (footwork) too narrow. Could be something else as well but this issue, especially against spinners is causing a lot of grief.

 

[christy_lenin1]

Matt the biggest issue I've seen so far is the batsman moving way across the off stump leaving stumps exposed behind him and getting bowled. No matter how hard I try I eventually end with this shot animation and it's impossible to build a long innings coz you know eventually you will be dismissed in this fashion. Alternative is to stop playing to the leg side altogether which is not practical. This is my biggest bugbear and I think it could be due to tolerance range level between 12'o clock and 1'o clock on LS (footwork) too narrow. Could be something else as well but this issue, especially against spinners is causing a lot of grief.

Do you mean something like this 0:47

 

[cricket_online]

here's a couple of overs of batting of that wagon wheel by KL rahul, you can see how i look at the field have an idea of it and go.

If I may what are your batting modifier slider settings? I'm referring to the the 5 main ones for batting starting with "Ball Marker Display Time".