Having just a single NetworkView over which RPCs can be sent means there are a few extra responsibilities we have to take on: A better option is to just use AllocateViewID() to get a unique object on the server even though our actual player object won't have their own unique network views. But if we did that, then we'd have to import at least another package - which isn't really worth it just for one function. NET's functions specifically designed for this task. Which would leave us with something like this:Īt the same time, we still want a way to guarantee a unique ID is assigned to each player. This will allow us to send RPCs back and forth between client and server without all the overhead and without all the unnecessary complexity. However, a single NetworkView component attached to an empty GameObject can be set to State Synchronization=OFF, and Observed=NONE. However, we're still going to need a single NetworkView because that's the only way Unity can communicate over the network (since we don't want to re-create the wheel and build our own Socket manager in. We're not going to take the standard route. Using this setup, EACH player will have its own chatty NetworkView sending out information to everyone else more or less continuously. If you start digging through LOTS of other Unity Networking tutorials, they'll follow the "standard route" of adding a NetworkView to your player prefab and then relying on Unity to decide when to send updates, and how much data will be sent. Unity Networking Sample Using One NetworkView So, what does that leave us with? It leaves us with.
Unity networkview code#
Update: I recently found a good way to do Server Discovery for the LAN, please post a comment if you'd like me to post that code as well :) I really wanted to do this as a true peer-to-peer, but Unity's built-in networking is geared strictly for client-server networking. And finally, RemoveRPCs (RPC = "Remote Procedure Call") only works when you are using Network.Instantiate, so it goes out the window as well. Network.Instantiate also generates so much network traffic that the game can pause and skip every time a new player joins. I picked these three because NetworkViews (even when set to "Unreliable") can create a lot of unnecessary network traffic if they are not managed very carefully.
The components I decided to avoid were NetworkViews, Network.Instantiate, and RemoveRPCs.
Unity is a great tool for Indie developers, but there are parts of it that can really make you spin around in circles. This Unity Package can be downloaded here (updated): fps_sample_2013_02_21.unitypackage
0 kommentar(er)
