DBC 17 Batting post Patch 3

[Mr Snrub]

Had a few games tonight with a good mate, who hasn't played much (if any) of DBC'17 at all (except now around at my place), but is pretty good at DBC'14 and he was very surprised by a few things.

We played with both custom and normal settings (and with custom we used various settings from throughout this thread) and some of the things he noticed and asked about were:

"Why is it that the outfield almost doesn't slow the ball at all? I mean I can understand the inner-circle, but the ball almost doesn't ever stop in the outfield!" One ball beat the fielders and rolled on and on, it began slowing and slowing and crawling along and still crawling along almost stopped, but not, 2 metres from the boundary. Here came the fielders, two of them. It was still moving, so slowly, but not stopping, snail racing them to the line. It juuuuuuuuuuuuuuuuuuuuuuuuuuuuuuust got there. Then it all happened again 10mins later.

"Why is the timing so early no matter what we set it to?"

"Maybe it was custom difficulty, try the default on Pro (then Amateur). Okay it's the same, why do you need to play a shot before you have any idea where the ball is going?"

(On custom - gradually lowering foot placement difficulty to 45 and then below) - "This doesn't seem to make a lot of difference and sometimes the shots I'm playing are coming out as totally different, when I use footwork"?

We put bowl quality influence down to 40 and it still was hard to hit the ball around, but it's not down to those things, it's down to the criminally early timing that's needed. It's crazily different to DBC'14.


We went on to play DBC'14 and the difference was night and day. "Okay, the only thing that's rubbish about batting is that I can't read length until too late and I'm used to working around that with only two bouncers per over".

Final verdict from my friend "I'll stick with DBC'14" basically. In general, he seems to think there's a lot of good new stuff, new bowling, new nicks, more dangerous fast pace than medium, shots going to more places. He loves the more official looking teams, grounds and logos, but in short, what doesn't work in DBC'14 is less annoying than what doesn't work in DBC'17. I don't think I let him play until patch 3 and I don't try and influence friends I just try and see how they feel when they play.

 

[blockerdave]

i agree that the timing is too early on console, and much much earlier than on DBC or pre-patch. i've spent some time today playing the pc build. it's very different.

my observations from 1 session batting on PC:

it felt like a different game.

i was able to get ideal timing very consistently, which i struggle to do on console. however, even with all 3 "ideal" the ball was still not travelling great and often not getting off the square. on console i time it poorly and edge or it trickles off the bat but when the timing is ideal it generally travels as expected. here i was not edging it much at all, but it was as common to get all 3 green trickle to the infield as it was to race to the boundary. an odd one.

i was able to pull the ball at will rather than trigger the hook animation. yay! on console post-patch i seem to always trigger the hook.

NOT ONE incident of triggering the reverse cut when cutting a ball that was too straight. on console it's 100%.

NOT ONE incident of the ball travelling in a direction contrary to the input. no way i'd get through a session on console without multiple instances of that.

footwork seemed more stable / less likely to jump around the crease.

so i'd be very interested in hearing if anyone else has batted much on pre-patch console, pot-patch console, and PC, and what their take is?

 

[christy_lenin1]

i agree that the timing is too early on console, and much much earlier than on DBC or pre-patch. i've spent some time today playing the pc build. it's very different.

my observations from 1 session batting on PC:

it felt like a different game.

i was able to get ideal timing very consistently, which i struggle to do on console. however, even with all 3 "ideal" the ball was still not travelling great and often not getting off the square. on console i time it poorly and edge or it trickles off the bat but when the timing is ideal it generally travels as expected. here i was not edging it much at all, but it was as common to get all 3 green trickle to the infield as it was to race to the boundary. an odd one.

i was able to pull the ball at will rather than trigger the hook animation. yay! on console post-patch i seem to always trigger the hook.

NOT ONE incident of triggering the reverse cut when cutting a ball that was too straight. on console it's 100%.

NOT ONE incident of the ball travelling in a direction contrary to the input. no way i'd get through a session on console without multiple instances of that.

footwork seemed more stable / less likely to jump around the crease.

so i'd be very interested in hearing if anyone else has batted much on pre-patch console, pot-patch console, and PC, and what their take is?

I always had this doubt after seeing some PC videos, let's hear it from others as well

 

[cricket_online]

i agree that the timing is too early on console, and much much earlier than on DBC or pre-patch. i've spent some time today playing the pc build. it's very different.

my observations from 1 session batting on PC:

it felt like a different game.

i was able to get ideal timing very consistently, which i struggle to do on console. however, even with all 3 "ideal" the ball was still not travelling great and often not getting off the square. on console i time it poorly and edge or it trickles off the bat but when the timing is ideal it generally travels as expected. here i was not edging it much at all, but it was as common to get all 3 green trickle to the infield as it was to race to the boundary. an odd one.

i was able to pull the ball at will rather than trigger the hook animation. yay! on console post-patch i seem to always trigger the hook.

NOT ONE incident of triggering the reverse cut when cutting a ball that was too straight. on console it's 100%.

NOT ONE incident of the ball travelling in a direction contrary to the input. no way i'd get through a session on console without multiple instances of that.

footwork seemed more stable / less likely to jump around the crease.

so i'd be very interested in hearing if anyone else has batted much on pre-patch console, pot-patch console, and PC, and what their take is?

There goes all of @grkramas theory about our crappy batting on consoles. Looks like there are different versions of the game post patch 3 on consoles and PC.

 

[grkrama]

There goes all of @grkramas theory about our crappy batting on consoles

ok first i want to be clear i didnt call anybody's batting as crap, apart from blockerdave's that was cause more because of our heated arguments and he deserved it.

Second Everything else i provided were tips to see if they work for you, and i thought it worked a bit for quite a few here. There is no grkrama's theory, plus anythign i proveded were batting tips for all i never targeted a platform, if there is not a parity between platforms its not my problem but BA's.

third its sill a theory, in all probability if its right hope BA fixes it soon.


[HASHTAG]#nottheEnemy[/HASHTAG]

 

[blockerdave]

There goes all of @grkramas theory about our crappy batting on consoles. Looks like there are different versions of the game post patch 3 on consoles and PC.

well my point regarding getting all 3 greens but the ball travelling as if mistimed was reported by nobody else on PC, so I may be off. what i would say is on PC you can definitely wait on watch line, as you could on console prior to the patch. post patch that's gonna be late timing.

 

[riteshagl]

i agree that the timing is too early on console, and much much earlier than on DBC or pre-patch. i've spent some time today playing the pc build. it's very different.

my observations from 1 session batting on PC:

it felt like a different game.

i was able to get ideal timing very consistently, which i struggle to do on console. however, even with all 3 "ideal" the ball was still not travelling great and often not getting off the square. on console i time it poorly and edge or it trickles off the bat but when the timing is ideal it generally travels as expected. here i was not edging it much at all, but it was as common to get all 3 green trickle to the infield as it was to race to the boundary. an odd one.

i was able to pull the ball at will rather than trigger the hook animation. yay! on console post-patch i seem to always trigger the hook.

NOT ONE incident of triggering the reverse cut when cutting a ball that was too straight. on console it's 100%.

NOT ONE incident of the ball travelling in a direction contrary to the input. no way i'd get through a session on console without multiple instances of that.

footwork seemed more stable / less likely to jump around the crease.

so i'd be very interested in hearing if anyone else has batted much on pre-patch console, pot-patch console, and PC, and what their take is?

Well well well that is interesting. No wonder grkrama was finding batting much easier then we console guys (though i think he has given some good inputs and advice). However, i believe eventually we will get these things on console as well, so two important positives out of this are timing meter is a bit delayed in pc and we are generally able to hit shots where we intend to.

 

[Dutch]

remember everyone.....lets make DBC great again......argh cant believe I just did that: I am off to build a wall around myself and invoke my visum......

 

[blockerdave]

remember everyone.....lets make DBC great again......argh cant believe I just did that: I am off to build a wall around myself and invoke my visum......

Difficult when someone who has never played on console is publicly and privately (i.e. directly to BA) attempting to delegitimise the complaints of console players and calls them morons, or keeps going on about shots that the people haven't mentioned.

whether i'm right or wrong about the differences, that is not helpful.

 

[grkrama]

The most pathetic post i have ever seen, implying absolute bullshite

 

[Mr Snrub]

Difficult when someone who has never played on console is publicly and privately (i.e. directly to BA) attempting to delegitimise the complaints of console players and calls them morons, or keeps going on about shots that the people haven't mentioned.

whether i'm right or wrong about the differences, that is not helpful.

I do think there has been a bit of an on-going situation of people reporting what they believe (fair enough), whilst attempting to defeat any reports that have a different point of view.

I'm sure their intention is to help BA receive a more uniform impression of what's wrong/needed, but really this is an example where people are playing on different platforms and there can potentially also be different setup/modifier issues.

Questioning players abilities isn't the way to go with people either, some people may only have played up to Pro or Veteran on DBC'14, but still know what good timing, foot movement and shot selection should produce and it's definitely a good shot! I myself got to the stage of being able to score centuries on Legend difficulty with DBC'14, but find a 50 (on just Pro) a flat out impossibility on DBC'17, due to having to swing for the ball pretty much the moment it leaves the bowlers hand. This is having tried various modifier improvements.

 

[blockerdave]

The most pathetic post i have ever seen

You think i have a personal agenda against you because I'm jealous you're good and I'm shit and you could not be more wrong.

I accept your batting tutorials are helpful, and you've given advice I've used and benefitted from myself.

But you have a massive blind spot here because you have not played on the platform and you simply do not have any idea about the scale of difference between pre and post patch batting and the number of issues that the patch introduced. That it appears (from my very limited sample) that these issues aren't on your platform has blinded you further into the route of thinking everyone on console must be much worse than you.

As far as I can tell the shot directional issue is not on pc, or is greatly reduced. There is no way you can bat a session on console without it happening several times, but I got through one on PC without it happening once. When you initially post "oh your thumbs need to be at x & y" for that shot, i get you're trying to be helpful. But when the problem is reported by multiple people all saying their hands were in the right place and MattW even posts that he has replicated the issue on at least some of the shots, and you're still "x & y" you're not being helpful you are disrupting the reporting of and conversation around an issue and I'm going to call you on that whoever you are.

When multiple people are reporting a new issue (pull animation for on drive) after the patch, and you're all "thumbs at x & y for leg glance" I'm going to point out we're not talking about the leg glance, and this is a new post patch problem. When you keep referring to the leg glance after every mention of the on drive, I'm going to point out that you didn't play pre patch and you don't know this is a new issue. Yes I know it only happens when it's outside off and yes I know an on drive isn't the textbook answer in that situation but it can be (and was pre patch) effective. If you keep going on about the leg glance again after discussion of the on drive it's obvious you're no longer even attempting to be helpful and are actively disrupting discussion/reporting of an issue and again I am gonna call you on it.

I told you to STFU the other day because you were so far off the mark it was embarrassing and infuriating. I can appreciate why, as it seems most or all of these issues aren't in the PC build, but that was why I was saying - initially politely privately- and more forcefully publicly that you were disconnected from the console experience. If you'd have allowed for even one second the possibility that people weren't just shit and in need of your advice, it would never have got that far. (And I accept I am the last person in the world who should guve advice on humility.)

The current console patch - or certainly the ps4 one anyway, I don't know what the xboxers are experiencing - really does have some serious issues. All any of us want is that sorted, but that cannot be helped by people with no experience of the issues insisting all can be fixed with a bit more attention to thumb position. It's WAY more than that.

 

[First.Last]

"Why is the timing so early no matter what we set it to?"

"Maybe it was custom difficulty, try the default on Pro (then Amateur). Okay it's the same, why do you need to play a shot before you have any idea where the ball is going?"

We put bowl quality influence down to 40 and it still was hard to hit the ball around, but it's not down to those things, it's down to the criminally early timing that's needed. It's crazily different to DBC'14.

This, so much this! I play on legend, settings like footwork, bowling influence etc on 100, but timing on 25-33 ish, and its pretty much like cricket IRL as far as i can tell... no balls flying off in weird directions, i can play based on reading the line and length without mis-hitting everything...

I wonder if the crazy timing issue we seem to be experiencing was bigant forgetting that not everyone plays with those length indicators...

 

[grkrama]

That is appears (from my very limited sample) that these issues aren't on your platform has blinded you further into the route of thinking everyone on console must be much worse than you.

this whole train of thought is just bigoted thinking from you and more way to try to insinuate me as villain here.

When multiple people are reporting a new issue (pull animation for on drive) after the patch, and you're all "thumbs at x & y for leg glance" I'm going to point out we're not talking about the leg glance, and this is a new post patch problem. When you keep referring to the leg glance after every mention of the on drive, I'm going to point out that you didn't play pre patch and you don't know this is a new issue. Yes I know it only happens when it's outside off and yes I know an on drive isn't the textbook answer in that situation but it can be (and was pre patch) effective.

dude i made the whole video of ON Drive for you after you cleared it in pm were i also clearly show how and when pull animation was happening. so another bullshite from you to attack.

but that was why I was saying - initially politely privately- and more forcefully publicly that you were disconnected from the console experience. If you'd have allowed for even one second the possibility that people weren't just shit and in need of your advice, it would never have got that far. (And I accept I am the last person in the world who should guve advice on humility.)

Again all i ever did was put in tuts on request of people here first cricket online, then people here in thread kept asking and i provided details of how shots worked for me.


If it works for you ok, if it does not it doesnot. How the hell is that anyway going to be a problem for you communicating with BA. Also all this was given when all thought the versions were in parity with each other. If you had spent more time testing that pc beta patch instead of trying to flame here may you would have arrived at the conclusion earlier.


If all you needed was getting the batting fixed based ion your experience there was no need to ever tag me or dutch. you just needed to report or discuss here, we weren't standing in you way, when you say things like a game were one guy can bat I had to disagree on bullshit like that.




And for all that talk of me having direct communication with BA, seriously you to have that, and may be you should make better use of it.

 

[grkrama]

Just to clear my name of all the dubious stuff blocker just said this is the feedback given by me on the issue to BA, im not telling BA to not look into this or discouraging nay discussion on it, i give my views and feedback both here on forum and in beta.

and this is before this theory of console not being in parity with PC.

Here are the problems i see with batting in the current main build. while its very enjoyable and playable from my view, these are things that can definietly be looked at and improved to make it better.

1. All the animation oddities :

• pull animation triggering for on drive
• pull animation triggering for legglance
• The reverse switch shot triggering for cut that blocker mentioned

2.All the shot direction oddities:

• Here the main standouts for me would be the cut shot going straightish beyond cover.
• On drive some times goes too square like squarelegish.
• I havnt had this happen but reported by others, straight drive going like a leg glance.

3. people having frustration over shot control:

• This mainly applies to shots like fine glance, hook, late cut and cut.
• people trying to go for hook end up with a BF fine glance, or late cut from my observation you need to get 6 clock on RS to play the hook.
• I would suggest moving the BF fine glance alone to precision control. front foot can stay normal. This will give Hook more area in RS and ocne people get that it shouldnt coincide with Late cut.

4. Frustration in getting out :

• edging ball in corridor while going for cover drive and they fly to point , or flyslip even of very slow medium bowlers. its not the edge itself but the way it results to wkt by ogin in a direction to poitn or flyign to fly slip of pies.
• Inside edge occurs a bit too often when going for cover drive when there is a inswinger.
• Also close in fielders act like block and take too many unbelievable catches of cuts. A short cover is more effective in stopping me from playing cuts than point. Getting out like that is frustrating after playing a long innings. They catch things that should have ripped their arms off.
• Same goes for late cut catching by WK of spinners which is well known.

5. Things needing tweaks to feel better:

• Think foot work for BF drives could be tightened a bit more, often the player moves a lot to leg side even when connecting well. this causes ball to go to midon than mid off were you aim for.
• Think shot force in general needs a bit of tweak to say 53 -55 something.
• Timing window can be a bit later and slightly wider at hardest diff for pace.

Also people who are finding it difficult to time etc a few seem to find a good play at these settings, apart from shot power which i and they too find OP at 60, 53 seems sweet at this setting, people do seem to get ok with this level of difficulty settings. I believe one of these parameters is were you guys need to tweak to more ease with batting.


I believe fixing these issues will resolve things with batting and these are the things affecting people with batting. Also all the variation we got now needs to be preserved while doing this and no other extra difficulty should be added.

As any other difficultly here on should come from better field sets and AI field decisions with bowling plan.