Has anyone encountered this?
When the CPU bats first in a 4 or 5 day match and posts a big total (anything over 400 seems to be the cut off point), when it comes to your turn to bat, it sets an aggresive field until your batsmen have taken 70odd easy runs each (particularly cos there's no mid off or mid on). It does not attempt to change the field no matter how quickly you score or that you haven't lost any wickets.
This is totally ruining the game for me at the moment as its too easy to chase down big targets.
Is there anyway of preventing the CPU doing this (presumably its somewhere in the .exe but I haven't a clue where to start)?
The default field editor will help in that we will be able to make the aggresive fields less aggresive but that seems to be a way off yet.
Anyone?
When the CPU bats first in a 4 or 5 day match and posts a big total (anything over 400 seems to be the cut off point), when it comes to your turn to bat, it sets an aggresive field until your batsmen have taken 70odd easy runs each (particularly cos there's no mid off or mid on). It does not attempt to change the field no matter how quickly you score or that you haven't lost any wickets.
This is totally ruining the game for me at the moment as its too easy to chase down big targets.
Is there anyway of preventing the CPU doing this (presumably its somewhere in the .exe but I haven't a clue where to start)?
The default field editor will help in that we will be able to make the aggresive fields less aggresive but that seems to be a way off yet.
Anyone?