Wrathchild tw wrote:I think I have discovered what causes this, and if I'm right it's not character stats, stick movement, or lag.. I'm pretty sure it's a game programming issue.
The best way to see this is with the ball machine. Turn it on, but don't try to hit the balls back, just run around with and without the run button pressed. What you will see is that the run button doesn't have any affect if there isn't a ball coming from the other side of the net. Oddly it will always allow you to run towards the net, but not away from the net or right/left unless there is a ball coming from the other side. This means you cannot quickly position yourself after you hit a shot until your opponent makes his swing - which is a problem in itself at high levels of play.
Now the problem with the player not moving sometimes seems to happen if you're trying to change direction or start moving from a stand still while your opponent is hitting the ball or just after this. Hopefully this is something that can be addressed if 2K can find the issue, because I don't think it's an intentional programming choice.
I noticed this, but I noticed it differently. I was playing online, and I've kinda figured out why. Also, I think the pause will be affected by reflex stat.
Anyways, what basically happens, is everytime the opponent hits the ball, your player will pause and 'react' using the reflex stat. Basically, pausing you from moving for tiny period of time after the opponent hits the ball. The pause is not noticable in normal situations, because thats general run-of-the-mill reactions.
The problem here though, seems like Wrathchild says, is a programming issue.
If you begin to move your player before the opponent hits the shot, i.e anticipating a cross court shot and running cross court, you player will move where you want him to, but when the opponent begins his animation for a shot, your player will 'pause and react' to the shot your opponent is hitting, hence why the player stops for a short period even though he was moving before hand. This is when the 'pause and react' action is noticeable, as it should not be happening as your player is already moving.
This to me seems a glitch, and I think 2K could sort it by overriding the 'pause and react' moment when you have already began moving your player.