The solution to that was to have the server change the IDs on its own NetworkViews, and then send another RPC to all the clients telling them to change their IDs. Secondly, if you send the RPCs to change IDs from a client, the server can sometimes send an additional state change from the old ID and clients receive that after they've changed to the new one, and that also gives an error on the clients when they can't find the NetworkView. I worked around that by having an extra NetworkView on my objects which I just use for RPCs, and that NetworkView is forever owned by the server and never gets its ID changed.
They still get sent, but a newly connecting client can't find the NetworkView and gives an error. It brought up a couple of issues that I hadn't anticipated, though:įirstly, changing the view ID messes up any buffered RPCs that were sent via the old ID. You can learn and discover the fundamental concepts in the. For this reason, it is recommended that you understand the fundamental concepts behind networking before you start experimenting with Network Views. They are simple to use, but they are extremely powerful. I've just tried this out this week and I can confirm that it does indeed work as expected. Network Views are the gateway to creating networked multiplayer games in Unity. Hopefully this helps, I haven't actually tried doing this myself but if it is possible to do want you want to do, this is probably the most likely way of doing it. This way you don't break the viewid relationship across all computers running the game. If you want to transfer ownership of an object it should be possible to do by allocating a new view id for the object on whoever you want to own the object and then assign the new id to the existing networkview, and the owner should now be changed.īut you would want to allocate the id first then send an rpc to all the other versions of the object on remote computers to change the id and then set the id.
#Networkview owne software#
Then the client will be the networkView.owner, if you were to do that on the server, the server would be the owner. NetworkView is a professional software application whose purpose is to help you generate a graphical map of your network using DNS, MAC addresses, SNMP, WMI, NetBIOS and TCP port information. From my understanding of Unity networking so far where ever you allocate the networkview.viedID is who the owner is.įor example is you instantiate an object that has a networkview on a client and then on that client says, Kinda, but not in a very nice and direct way.
0 kommentar(er)
