Server time incorrect on client if the Tick Rates are different

[JohnConbere]

Describe the bug
If you have the NetworkManager.TickRate set to different values on the client and server the NetworkManager.ServerTime value is incorrect. For example, if you set the Server Tick rate to 30 and the Client Tick rate to 5, the servertime on the client will be reported to be 6x what is on the server.

To Reproduce
Steps to reproduce the behavior:

1. Create a server and client application
2. Set the server tick rate to 30
3. Set the client tick rate to 5
4. Run
5. Check the NetworkManager.ServerTime variable.

Actual outcome
The NetworkManager.ServerTime variable on the client reports 6x what the NetworkManager.ServerTime is on the server.

Expected outcome
The NetworkManager.ServerTime on the client and server are sync'd

Environment (please complete the following information):
Unity 2020.3.21
com.unity.netcode.gameobjects -> develop branch commit(c3ca7cb)
UnityTransport : Version 1.0.0-pre.10 - December 03, 2021

[LukeStampfli]

Different tickrates are not something we support. We should include the tickrate of the config in the checksum so that there is an exception when different tickrates are used.

[LukeStampfli]

I just checked and I'm not able to perform step 2 and 3 by changing the tick value of the NetworkConfig. If I do change the values to different ones I'm not able to connect due to a config mismatch. Could you provide more details for how you set those values?

[JohnConbere]

We have completely separated client and server projects and I just set it in the editor on each project in the NetworkManager component.

[LukeStampfli]

Okay thanks, I checked the source and we are indeed missing a check. I will create a PR to fix that so that using two different tick rates will result in an exception being thrown. Right now we only support cases where the client and the server are using the same tickrate.