Significant delay on client when using Relay with Unity Transport (even with small data)

I followed some tutorials and created a character controller with Server-Authoritive Input. Even sending a single ServerRPC-request with only a float, there was a delay of almost an entire second.
I tried creating a Character-Mover by having two NetworkVariables for position and rotation (tried it with two verctor2s and even 4 floats). The PlayerInput was processed by a ServerRPC-request. On the host, there is no significant delay, but on the clients it's unplayable. Even when clicking a button, there is a long delay.

Is this because of the Servers still being free and in beta, or is something in my code wrong? I found out that even Dilmars project has this long delay. Here is his code, which is pretty similar to mine:

https://github.com/dilmerv/UnityMultiplayerPlayground/blob/master/Assets/Scripts/PlayerControl.cs

 

Hey ! Have you found a solution for this ? Experiencing the exact problem with the same content. Followed dilmer tutorial but same thing happen

 

If you want to have instant feedback, like in a singleplayer game (offline game), you need a Client/Input Prediction. Because of the RTT (RoundTripTime) it takes for the message to be delivered from Client to Server back to Client.
The larger the physical distance of the Server and the Client, the larger the RTT.

Also, if you are using the NetworkTransfrom and the Interpolation, you need to keep in mind that the Interpolation buffers a few incoming Inputs before processing it. This also causes delay.



A Client/Input Prediction is a very difficult task, espacially with Unity since its not deterministic with its Updates.

PS: The Netcode Roadmap has the Cliend-side Prediction planned.