`PhotonNetwork.Time` doesn't change in every `FixedUpdate`
Options
develax
✭✭
I noticed that `PhotonNetwork.Time` can stay unchanged for several `FixedUpdate` calls. It seems to be odd. Isn't it supposed to be different in every `FixedUpdate` call?
In fact, the time can remain unchanged up to 10-15 `FixedUpdate` calls in a row and the intervals between time changes look to be very variable when not having very stable ping. Since sync algorithms use `PhotonNetwork.Time` to calculate interpolation time in every `FixedUpdate` call to move the object smoothly, it looks unreasonable to waste computer resources to calculate the same values and also makes smooth movement difficult to achieve. But all the interpolation algorithms I've seen seem to rely on the fact that time has to change every `FixedUpdate`. I'm curious, how to handle this situation, IOW is there a way to calculate interpolations correctly in every update method call?
In fact, the time can remain unchanged up to 10-15 `FixedUpdate` calls in a row and the intervals between time changes look to be very variable when not having very stable ping. Since sync algorithms use `PhotonNetwork.Time` to calculate interpolation time in every `FixedUpdate` call to move the object smoothly, it looks unreasonable to waste computer resources to calculate the same values and also makes smooth movement difficult to achieve. But all the interpolation algorithms I've seen seem to rely on the fact that time has to change every `FixedUpdate`. I'm curious, how to handle this situation, IOW is there a way to calculate interpolations correctly in every update method call?
0