Yeah.. Something happens when youre shooting a ball.mojoicus wrote:Certainly seems to be an in game problem if its happening to com opps but very weird its not there on replays ???
You pull the cue back, and then strike forward to shoot: right before contact (or right at the same moment as the cue touches the cueball, cant say for sure which one is true) you will ge the lag. Right after the lag the cue dissapears and the cueball starts to move (remember this moment as point 1 for example).
In the replay case, if you really think of it, there is no "real" cue back n forth swing. There is only this animation which shows the back and forth animation of the cue. The animation does not show you how hard you really shot at the time when that replay was taken: its allways the same animation no matter what force you used in the actual shot. Anyways, as the animation goes on the cue moves towards the cueball and right at the same moment as the cue hits the cueball, ( !! this is the same moment as I described in the earlier paragraph !! ): Its the moment when the actual replay starts. This might be why the lag is not visible in the replay; The moment when you got the lag was during your cue action; the "record replay" haven't started yet.
But the thing that the CO also has it.. weird. When the CO shoots, to me it's like you see exactly the same animation as you see every time when you are replaying a shot (cue stick swing).
And so it all comes into this (maybe): This is something that makes me think that the shot lag is happening on the moment when you are hitting the cueball with your cue at the first time; maybe at the moment when the cue hits the cueball the game engine does some heavy duty burst calculation of how the balls are going to move and behave in the upcoming shot and causes some CPU process peak and the lag? In replay we cant see it because the ball routes have already been calculated and easily be replayed from a X and Y coordinates dug from your RAM memory?
I might also be very badly off tracks with this one, I dont know.