Nothing game stopping but a few issues.
{FIXED} Unable to start career mode on very high resolution displays
- If you auto play aspects of a game (like the fielding) the message that tells you that you might lose XP for auto playing does not clear from the screen once it has jumped through to your turn to act again. Something like " Using auto play you may not gain experience for your players actions" or something similar. It says Press "A" to clear - but pressing "A" does not clear the message for a ball or two.
- Certain resolutions (such as 2560 x1080) are shown as available in the game menu but do not work in game. Unselecting "letterbox" does fill a 2560 wide screen with a stretched 1080 resolution (therefore displaying the game with a blurry and incorrect aspect ratio)
- Playing a league game, batting second held out for a draw. Chasing 301 we got to 297 or for 2 at the end of play ion the 4th day. Another over and we would have won. However, rather than a draw (or in league cricket one of those horrible "winning draws") we were informed we had lost the game. The commentator actually said we had been bowled out "so close" the league table had us losing as well. This was a 4 day game so should have been either a draw or (if it's implemented) a "winning draw".
- Quite a few commentary errors. like "He's finally out for.. 265 for 5". Which might I suppose be right - but it feels like it should be telling us the batsmans final score. And "fielded by... "then nothing is said. Bowling a maiden and being told "He went for a few that over".
- Fielding changes. Choose a new field from presets "X" to set for all. Return to game. Nothing has happened. Do it again this time don't press X (so should be just for that bowler) but again no field changes. A ball later (one ball into the over) it lets me change fields fine. Seems to not let me on the first ball of an over.
- 26 over spell in my second game. Ok I'm a spinner - but from DB '17 where as a batting all-rounder I would have multiple 2 over spells which was a little annoying when the fields reset after each mini spell. In Ashes, in my second game, as the weakest of 5 bowlers in my team. I bowled 26 overs without a break. There was an interval in there, but straight back out to continue my spell afterwards. I was neither the most economical nor the most penetrative bowler in my team - actually being the 4th out of 5 for economy and the worst for wickets (nor the only spinner) so this seemed a little strange.
- Maidens not being counted towards achievement goals. About 1 in 5 maidens is registered by the game with the pop up. According to the achievement screen area my career spin bowler has not bowled 20 maidens in his career yet, according to his stats he bowled almost that many in the last test match he played in (but none got credited to the number of maidens required to bowl to reach the achievement) and literally hundreds in all FC games so far.
NONE BUGS - BALANCING QOL ISSUES and "Maybe this is meant to be but it doesn't feel right" type stuff.
- Keeper drops perhaps 75% of thin edges
- Field settings often forgotten or require to be reset often
- In T20 games the number of wickets that fall on both sides seems low. Typically only 2-3 wickets lost per innings. I have seen frequent games of 180+ for 0 wicket
- AI selects strange teams, often leaving out the best players. Is this to simulate injury or something?
- How many ponytails on male players? Teams with 7 ponytailed players?
- Women's voices being used in men's games
No big issues really. Gameplay itself was smooth and enjoyable. No crashes. Mechanics tightened up noticeable from DB '17. Menu's also sharper and more intuitive than DB '17. These issues feel like things that could be ironed out with a quick patch. Let's hope Big Ant support this game for a long time to come.
{FIXED} Unable to start career mode on very high resolution displays
- If you auto play aspects of a game (like the fielding) the message that tells you that you might lose XP for auto playing does not clear from the screen once it has jumped through to your turn to act again. Something like " Using auto play you may not gain experience for your players actions" or something similar. It says Press "A" to clear - but pressing "A" does not clear the message for a ball or two.
- Certain resolutions (such as 2560 x1080) are shown as available in the game menu but do not work in game. Unselecting "letterbox" does fill a 2560 wide screen with a stretched 1080 resolution (therefore displaying the game with a blurry and incorrect aspect ratio)
- Playing a league game, batting second held out for a draw. Chasing 301 we got to 297 or for 2 at the end of play ion the 4th day. Another over and we would have won. However, rather than a draw (or in league cricket one of those horrible "winning draws") we were informed we had lost the game. The commentator actually said we had been bowled out "so close" the league table had us losing as well. This was a 4 day game so should have been either a draw or (if it's implemented) a "winning draw".
- Quite a few commentary errors. like "He's finally out for.. 265 for 5". Which might I suppose be right - but it feels like it should be telling us the batsmans final score. And "fielded by... "then nothing is said. Bowling a maiden and being told "He went for a few that over".
- Fielding changes. Choose a new field from presets "X" to set for all. Return to game. Nothing has happened. Do it again this time don't press X (so should be just for that bowler) but again no field changes. A ball later (one ball into the over) it lets me change fields fine. Seems to not let me on the first ball of an over.
- 26 over spell in my second game. Ok I'm a spinner - but from DB '17 where as a batting all-rounder I would have multiple 2 over spells which was a little annoying when the fields reset after each mini spell. In Ashes, in my second game, as the weakest of 5 bowlers in my team. I bowled 26 overs without a break. There was an interval in there, but straight back out to continue my spell afterwards. I was neither the most economical nor the most penetrative bowler in my team - actually being the 4th out of 5 for economy and the worst for wickets (nor the only spinner) so this seemed a little strange.
- Maidens not being counted towards achievement goals. About 1 in 5 maidens is registered by the game with the pop up. According to the achievement screen area my career spin bowler has not bowled 20 maidens in his career yet, according to his stats he bowled almost that many in the last test match he played in (but none got credited to the number of maidens required to bowl to reach the achievement) and literally hundreds in all FC games so far.
NONE BUGS - BALANCING QOL ISSUES and "Maybe this is meant to be but it doesn't feel right" type stuff.
- Keeper drops perhaps 75% of thin edges
- Field settings often forgotten or require to be reset often
- In T20 games the number of wickets that fall on both sides seems low. Typically only 2-3 wickets lost per innings. I have seen frequent games of 180+ for 0 wicket
- AI selects strange teams, often leaving out the best players. Is this to simulate injury or something?
- How many ponytails on male players? Teams with 7 ponytailed players?
- Women's voices being used in men's games
No big issues really. Gameplay itself was smooth and enjoyable. No crashes. Mechanics tightened up noticeable from DB '17. Menu's also sharper and more intuitive than DB '17. These issues feel like things that could be ironed out with a quick patch. Let's hope Big Ant support this game for a long time to come.
Last edited:
