Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualTelanor

Posted 10 December 2012 - 10:46 PM

Yep, that's exactly what's happening. The server seems to apply the input for exactly 1 less tick than the client. I don't understand why it's happening though...

Edit: Found the issue. The client was doing "if action.isTriggered, send triggered, else if action.isHeld, send held". Problem is, when you pressed a key, on the very first frame, it counted as both triggered and held. Client side, it was receiving both on the same tick, but the server had to wait an extra tick before getting the isHeld message.

#1Telanor

Posted 10 December 2012 - 10:06 PM

Yep, that's exactly what's happening. The server seems to apply the input for exactly 1 less tick than the client. I don't understand why it's happening though...

PARTNERS