Hello,
I have a 2 player networked game using listen-server and now it seems like to get rid of judder on replicated movement on the client side I will have to make my own movement replication system, as suggested by Zak in this post.
I’m guessing the judder is coming from replicated movement data fighting with local movement data.
I am surprised that I would have to do this as I thought the whole point with the CharacterMovement component was that it provided automatic remote-local merging, smoothing and prediction.
So my question is, can/should I now chuck out the movement component if I’m making my own replication anyway?
I can’t think about anything else in my blueprint that I’m using it for.
Does it do anything important ‘behind the scenes’ that I have to be aware of?
Cheers