#Unity networkview bandwidth update#

If playerA and playerB are far from eachother but still able to see eachother you can reduce the rate at which you send playerAs transforms to playerB and vice versa.

#Unity networkview bandwidth update#

(if you have 200 players on your server each playing in groups of 4 in their own little instance your server will only need to send 3x200x36x15 bytes/second instead of the 199x200x36x15 it would have to send if all 200 players were in the same area and able to see eachother)Ģ) Adapt the update rate based on distance or relevance. (Do you see where this is going ?), 100 players in this scenario still only requires players to have a 400kbps connection (or one that never drops below that really) but the servers bandwidth requirements can start to making hosting difficult in some areas.Īt 200 players the server bandwidth can hit 199x200x36x15 ~= 163Mbps, this is now pretty much impossible to host on a consumer connection (Allthough some regions have 1Gbps consumer connections now it is still fairly rare) and hosting costs for a commercial grade connection will be very high.įor an action game you probably want to update transforms atleast 15 times per second and you will have to send quite alot of other data aswell (a single transform per player isn't really enough for most games) so in order to keep the bandwidth usage on the server at a reasonable level you need to be a bit smart about it.ġ) Keep the number of players in a given area low, the more players you got in a single area the more data your server has to send to each of them. Some tips for optimizing the performance and bandwidth usage of Actor. at 100 players you'd hit ~40Mbps on the server at that update rate with just a single transform per player being synced. The maximum transmission unit (MTU) setting determines the largest packet size. There is room for improving your bandwidth performance by reducing the int to a short. at 50 players you get 49x50x36x15 ~= 10Mbps worth of bandwidth for the server (Still acceptable). Note that the PhotonView is very similar to Unitys NetworkView. With 20 players at the same updaterate you get 19x20x36x15 ~= 1600kbps (80kbps per player) (now its no longer possible to host the game on a DSL connection with 1Mbps upload, players can still play just fine with even a really weak 256kbps connection). I'm aiming for a 1MB/sec connection speed.The problem is the server, if you have 10 players and sync their 36 byte transforms 15 times per second the server has to send 9x10x36x15 bytes of data each second (thats 47.46 kbyte/s or 379kbps (37.9kbps per player)

Often, these methods are triggered when network operations complete (example: when joining a room). Much like 'Update ()' in Unity, PUN will call methods in specific situations. Hmmm, if only 36 bytes are sent per update, it seems like a fair amount more than 100 could be supported for an action game with a moderate update rate. This enum defines the set of MonoMessages Photon Unity Networking is using as callbacks.