Don Bradman Cricket 17 General Discussion

[cricket_online]

In terms of reaction time, we can't speed the animation up, it doesn't look good, we can't forecast the AI to the player as we calculate the trajectory in real time as it leaves the bowlers hands (we need this for two player games in any case).

Fair enough. I was hoping the AI delivery type/trajectory can be calculated beforehand (say when it's 3/4th of the way in his/her runup) and head-to-head games (any mode where AI doesn't bowl) can remain the way it is now.

 

[cricket_online]

rather than fiddling with controls how about freeze frame for fraction of a second before ball release with color indicator of length like in online match ups in dbc14????
that way las up or down would be taken care of while other input can be made on merit of ball

That's a decent option as well.

 

[blockerdave]

That's a decent option as well.

no it is a terrible idea. any freezing/slowdown is a huge no. i think a flash just prior to release giving the broad area is sufficient.

 

[toecrusher71]

When i play in nets i get this annoying message "Lost connection to the controller-7 press y"when i click it takes me to menu and it repeats every 4 minutes.I play with playmax controller that came with dbc14.Any possible reason or suggestion?

 

[cricket_online]

no it is a terrible idea. any freezing/slowdown is a huge no. i think a flash just prior to release giving the broad area is sufficient.

It's an option so only folks who enable it will see the "slow down". it's not the best option - I would still prefer the AI to calculate the delivery type earlier so there's enough time for it to be displayed based on the setting of a user's choice, but it's better than the current scenario where I have to pre-meditate nearly every shot on the front foot. I would take a slight "slowing down" just before the bowler delivers the ball as compared to not reading line & length in time and not using back foot at all.

 

[blockerdave]

It's an option so only folks who enable it will see the "slow down". it's not the best option - I would still prefer the AI to calculate the delivery type earlier so there's enough time for it to be displayed based on the setting of a user's choice, but it's better than the current scenario where I have to pre-meditate nearly every shot on the front foot. I would take a slight "slowing down" just before the bowler delivers the ball as compared to not reading line & length in time and not using back foot at all.

this optional "only there for people who enable it" is craven nonsense. the issue - picking up length early enough not to premeditate or feel they are premeditated/rushed - is an extremely common complaint and needs a good solution implemented. implementing a terrible solution and making it "optional" is not remotely helpful.

 

[cricket_online]

this optional "only there for people who enable it" is craven nonsense. the issue - picking up length early enough not to premeditate or feel they are premeditated/rushed - is an extremely common complaint and needs a good solution implemented. implementing a terrible solution and making it "optional" is not remotely helpful.

I would take it if there's no other option available, which looks to be the case. Playing almost everything on the front foot or being late takes too much fun out of batting.

 

[Deleted member 9102]

The lower difficulty levels choose front/back foot automatically don't they? How about having footwork assistance and shot timing difficulty be split into different options rather than bundled together into the difficulty levels?

This way, people who struggle to react don't have to worry so much about the length and camp on their front foot because the player will go on the back foot automatically when necessary, but they wouldn't have the easy six hitting that goes with playing on Rookie.

 

[Spitfires2007]

Do we know which teams are licenced? Such as the ones in Australia and England???

 

[FAZ007]

When i play in nets i get this annoying message "Lost connection to the controller-7 press y"when i click it takes me to menu and it repeats every 4 minutes.I play with playmax controller that came with dbc14.Any possible reason or suggestion?

Its a sign of defective or dying controller
Game works best with Xbox controller

 

[cricket_online]

The lower difficulty levels choose front/back foot automatically don't they? How about having footwork assistance and shot timing difficulty be split into different options rather than bundled together into the difficulty levels?

This way, people who struggle to react don't have to worry so much about the length and camp on their front foot because the player will go on the back foot automatically when necessary, but they wouldn't have the easy six hitting that goes with playing on Rookie.

I wouldn't prefer this option as it takes away from the batting experience. One of the integral part of batting is to read line & length, select footwork (back or front) and choose an appropriate shot. If you make footwork selection "automatic" it dumbs down batting. I would want to be in control of footwork selection and would want to make the choice how I play the shot - on front or back foot. The issue is that it takes insanely fast reaction time to read line & length to determine appropriate footwork and that's what needs to be solved, i.e. how users get enough time to get the information. Making footwork selection automatic doesn't do so.

 

[The_Pharoah]

It's an option so only folks who enable it will see the "slow down". it's not the best option - I would still prefer the AI to calculate the delivery type earlier so there's enough time for it to be displayed based on the setting of a user's choice, but it's better than the current scenario where I have to pre-meditate nearly every shot on the front foot. I would take a slight "slowing down" just before the bowler delivers the ball as compared to not reading line & length in time and not using back foot at all.

I think the only way to fix this (or change this) is to change the FOV ie. move the bowler back in your FOV maybe 1m or something. This allows for a slightly longer flight but allows the batsman that extra millisecond to judge the pitch/flight. Anyone knows playing against bowling machines is extremely difficult because you have only a split second to judge before performing a batting action. in DB14 it was similar ie. you only got a small window to judge. So I say, move the bowler back a bit. Remember, this is cricket and cricket is NOT an easy game to play (or we'd all be scoring hundreds) and being able to judge the length/pitch/etc of the ball doesn't guarantee you anything...you still need to choose the correct footing, shot, force, etc etc...and still get bowled middle stump.

 

[Deleted member 9102]

I wouldn't prefer this option as it takes away from the batting experience. One of the integral part of batting is to read line & length, select footwork (back or front) and choose an appropriate shot. If you make footwork selection "automatic" it dumbs down batting. I would want to be in control of footwork selection and would want to make the choice how I play the shot - on front or back foot. The issue is that it takes insanely fast reaction time to read line & length to determine appropriate footwork and that's what needs to be solved, i.e. how users get enough time to get the information. Making footwork selection automatic doesn't do so.

I thought you might say this... But surely the other solutions you've proposed also have this effect anyway?

If you have a marker or an indicator of some sort before the bowler releases the ball to tell you if the ball is short or full, you're only really going to choose back or front foot respectively anyway. Having manual input over footwork at this point is almost an illusion of depth/choice... You'll already know the best footwork and the subset of shots that are playable to most deliveries before the bowler even releases the ball. Good length balls may still cause some uncertainty, but the element of surprise of facing a nasty short ball or a yorker is gone if you know the length in advance.

I appreciate that it's difficult to react so quickly and see why people can get frustrated... I'm not great at it either, but I like that to be honest. Batting in most other games has been too easy and a bit of a slogathon - only losing wickets by getting impatient or mistiming one... In DBC I play on the highest difficulty and lose wickets in natural and realistic feeling ways - being beaten by pace, bad footwork, playing all around one, getting done by swing etc. It makes those innings where you manage to grind out a big score all the more satisfying because it's so challenging.

It's such a common complaint though and was throughout DBC14's lifecycle that I agree with you - it probably needs addressing in some way or another so these people aren't put off the game.

 

[Gayan]

I don't think picking length is a big issue , only if ur footwork is really off you will be in trouble. I think the big issue is picking up the line , there's just not enough time to really assess the trajectory to pick up the line. The current system for line determined by the fullness of the circle around the ball is too subtle.

One suggestion id have for the line indicator is to have three shapes around the ball rather then the fullness of the circle.

• For balls pitching between imaginary 4th and 5th stump display the circle around the ball (currently in game)
• For balls pitching outside imaginary 4th stump( off side) have a triangle around the ball instead of a circle
• For balls pitching down leg side 5th stump (leg side) have a square around the ball

Having 3 different shapes around the ball instead of just the circle and its fullness to determine line will be easier to pick up.


This would compliment the current color coding for length already in the game.

 

[Snowy]

How is an arbitrary shape any easier than a circle effectively 'pointing' you in the right direction?