Cricket 19 General Discussion

That's what gets me. Theres no obvious reasoning behind it and I refuse to accept the bollocks reasons provided by third parties on here. From the horses mouth please.

Its hard to bowl dots when the single is always on. Surely its simple enough to program the fielder to collect the ball and throw at normal speed? Then select from a list of possible outcomes i.e. runout, otherthrows, close call 3rd umpire review etc each with a different % chance of occurring based on time available, speed of the ball, distance from stumps, fielder ability etc.

You would then see pressure build up if we choose not to risk these currently guaranteed singles.

Also, why is the bowler/keeper so slow to break the stumps? The batsman can cover half the track while the balls in the keepers hands. Why cant this be sped up so we can run human players out when they take runs on a fielders throw?

Also worries me how many people on here support this argument of "these issues cant be fixed without causing several more bugs, fielding is the foundation of the game so cant be changed". You couldnt pitch a tent on these foundations.

It's just lazy programming. No Im not a game developer. But I know when things like batsmen not being able to run after the stumps are broken has been purposefully coded into the game, in an attempt to hide the fact theres no pull out stump animation. Please, let us run and just let the crappy bail breaking animation play out again. Yes it looks bad but at least it means the game plays to the rules of cricket. Plus we still see the ugly animation if you do set off for a run just as the bails were breaking first time. So what's the logic lads?

I hope they're working on a mega patch to sort the game breaking issues.
It feels like forever since they've released a patch. Game is very playable and looks great but there's a few elements that make you put it down after a while and wait for a patch. Also praying this will be a large patch. I was hoping for a release to coincide with Australia's Ashes retention but I guess not. Maybe at the conclusion of the 5th test they'll release it? *fingerscrossed*
 
That's what gets me. Theres no obvious reasoning behind it and I refuse to accept the bollocks reasons provided by third parties on here. From the horses mouth please.

Its hard to bowl dots when the single is always on. Surely its simple enough to program the fielder to collect the ball and throw at normal speed? Then select from a list of possible outcomes i.e. runout, otherthrows, close call 3rd umpire review etc each with a different % chance of occurring based on time available, speed of the ball, distance from stumps, fielder ability etc.

You would then see pressure build up if we choose not to risk these currently guaranteed singles.

Also, why is the bowler/keeper so slow to break the stumps? The batsman can cover half the track while the balls in the keepers hands. Why cant this be sped up so we can run human players out when they take runs on a fielders throw?

Also worries me how many people on here support this argument of "these issues cant be fixed without causing several more bugs, fielding is the foundation of the game so cant be changed". You couldnt pitch a tent on these foundations.

It's just lazy programming. No Im not a game developer. But I know when things like batsmen not being able to run after the stumps are broken has been purposefully coded into the game, in an attempt to hide the fact theres no pull out stump animation. Please, let us run and just let the crappy bail breaking animation play out again. Yes it looks bad but at least it means the game plays to the rules of cricket. Plus we still see the ugly animation if you do set off for a run just as the bails were breaking first time. So what's the logic lads?

I hope they're working on a mega patch to sort the game breaking issues.
I do hope for a patch as well. The game is quite good in the sense that, it's the only cricket game that's actually fun playing and mostly well made. However, the points you make are also true, and I hope we get something. Though as you know with patches, sometimes one thing gets fixed another worse one gets issues.[DOUBLEPOST=1568092510][/DOUBLEPOST]
One can only hope ,since they don't believe in letting customers know what they're or are not doing
To be honest, if it's about talking to fans here at PC Forums, I understand why they would be hesitant, given their experience in the past.
 
Is just me who thinks that the ball bounces way to low for spinners on a soft pitch
 
Does anybody know if you're able to switch counties? I'm still playing at club level but I'm wondering whether you can change counties when you get called up
 
Is just me who thinks that the ball bounces way to low for spinners on a soft pitch
It’s not only on soft pitches. Some grounds it doesn’t even matter if you change the bounce sliders. Big Ant really messed up on a lot of key features in this game. Their support system is the worst off all. Unfortunately they are the only cricket game developer at the moment. The game is perfect for players that just want to have some weekend fun, but for the serious guys it’s not on par.
 
Has the following bug related to catching been reported yet:
The catching mini-game comes up, the camera goes into first person, I move the left stick to bring the pointer within the circle, the circle glows green, press the button(A on Xbox One) and the catch is still dropped. No idea why.
This hurts even more when the fielder is on the boundary and he lets it go for a 6.


Also, with the first person view, how do you guys make out if the boundary fielder should tap the ball in or go for the catch. In instances, where the above bug doesn't hit, I take the catch and the fielder then calmly walks over the boundary line to gift a 6. So annoying.
 
Last edited:
Has the following bug related to catching been reported yet:
The catching mini-game comes up, the camera goes into first person, I move the left stick to bring the pointer within the circle, the circle glows green, and the catch is still dropped. No idea why.
This hurts even more when the fielder is on the boundary and he lets it go for a 6.


Also, with the first person view, how do you guys make out if the boundary fielder should tap the ball in or go for the catch. In instances, where the above bug doesn't hit, I take the catch and the fielder then calmly walks over the boundary line to gift a 6. So annoying.
Dont you have to press a button as well at the right time?
 
Dont you have to press a button as well at the right time?
Yes, I do press the button too. A on Xbox One. Sometimes the fielder takes the catch and other times he doesn't. And times he doesn't, its not like a dropped catch where he gets hands to it but can't hold on, instead he can't even get his hands into the position.
Please tell me it's not just me.
 

Users who are viewing this thread

Top