Some latency questions RPC, OnSerialize
Options
I've done some researching about the latency issues but I have some questions. Here is some info about our game.
1. Ideally the game logic needs to run at 60FPS. The game rendering can be less
2. The game can't make use of common tricks like prediction, etc.
Will using onserialize get the info from source to target faster than using RPC's which we are currently using?
In my test the client to server ping time is consistently 100ms +/-5ms. But it is taking longer than 50ms +50ms for an RPC to get from the source to the target. I tried using SendOutgoingCommands() which helped some but it still seems like there is an extra 30 to 50ms of delay on average.
When or how often is PUN checking for an incoming RPC on the client side. At the end of every update frame? This would be a problem since the update loop (graphics rendering is only running at 30-35FPS)
1. Ideally the game logic needs to run at 60FPS. The game rendering can be less
2. The game can't make use of common tricks like prediction, etc.
Will using onserialize get the info from source to target faster than using RPC's which we are currently using?
In my test the client to server ping time is consistently 100ms +/-5ms. But it is taking longer than 50ms +50ms for an RPC to get from the source to the target. I tried using SendOutgoingCommands() which helped some but it still seems like there is an extra 30 to 50ms of delay on average.
When or how often is PUN checking for an incoming RPC on the client side. At the end of every update frame? This would be a problem since the update loop (graphics rendering is only running at 30-35FPS)
0
Comments
-
I also forgot to mention the rpcs are just sending the state of the controller input and the turn the input is to be executed on.0