by abc010101 » 17 Mar 2024, 20:57
Manu, I've been doing some more testing and it seems that you're correct. I stand far behind the baseline to receive a strong serve, so when I try to get closer to the baseline to continue the point after I return the serve, the CPU thinks I'm rushing to the net and so he moves forward. It's too sensitive, all it takes is one step forward from me and the CPU thinks I'm trying to go to the net even though I'm so far behind the baseline. I think it would work better if I cross the baseline after I make a shot and actually approach the net, but it shouldn't trigger just because I move slightly forward after a safestrike.
There are also other instances where the CPU has this issue. Here is another DMO, take a look a the second point. Wide serve that almost gets me off the court, so the CPU wants to finish the point quickly and so moves forward, but ends up doing a safestrike. Again, this connects to what I was saying earlier, I tweaked the Elite controls to be a little bit more difficult and it seems the CPU has trouble understanding that its behavior needs to change appropiately. It tries to hit the ball even before it reaches its peak but at the last moment realizes that it can't, so it does a safestrike. It's like the CPU thinks it's playing on easier controls than it is. Although, I have also noticed this issue even on Arcade controls, just less frequently.
Is there anything I can do ? Can I somehow tell the CPU that since the controls are tweaked to being more difficult now, it needs to wait a bit more for the ball to come down to perform an acceleration, instead of rushing and trying to catch it so high ? Is there something in the custom strategy that affects this ?
You do not have the required permissions to view the files attached to this post.