Even though it says that UE4 comes with lag compensation, client prediction, server correction etc., that only seems to be the case for character-pawns, which is kind of a let-down 
I want to use
- vehicles that are physics-simulated and non-wheeled
- kinematically moving non-character pawns
My question is: what is the ideal way/place to deal with client prediction and smooth correction for their movement? Should I implement the “Prediction-Interface”? What else do I need?..
And then I’d like to know what other parts of a game typically need client prediction. I mean, every client action - like firing a rocket - suffers from input-lag, if I bind it to a server-function call. And I have absolutely no idea how I could make a client do a prediction here. I would have to spawn the rocket on the client immediately, then wait for the server to spawn it as well, and then somehow redirect the replicated movement to the client’s rocket, and also prevent the rocket from being spawned/replicated again on this particular client. At least I don’t see what else can be done here 