Jump to content

Recommended Posts

@V2C While looking at how DirectWalking is implemented, it made me wonder if the "stutterstepping" you see from people experiencing lag with movement prediction on is due to the WASD movement vector being of length 1-- maybe in some cases the delay is too much for it to update. If the vector's length were increased to something like 4, that should help a lot, I think?

(To clarify on what I mean by stutterstepping-- I see them moving around but stopping every half second, which slows them down. It looks really weird, too, almost like they're trying to put an item down repeatedly while walking.)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...