Asset SyncVars

Is this cool or is it crazy?

SyncVars could be any Unity asset type, such as Texture, Material, Sprite, Shader, Light..

As long as they are registered at runtime on the client, they can be sent from the server to clients. This applies to parameters in ClientRpc calls as well.

Code (CSharp):

1. public class Player : NetworkBehaviour
2. {
3.     [SyncVar(hook="OnMat")]
4.     Material mat;
5.  
6.     void OnMat(Material m)
7.     {
8.         GetComponent<Renderer>().material = m;
9.         mat = m;
10.     }
11.  
12.     public Material otherMaterial;
13.  
14.     void Awake()
15.     {
16.         ClientScene.RegisterAsset(otherMaterial);
17.     }
18.  
19.     public override void OnStartClient()
20.     {
21.         if (mat != null)
22.             GetComponent<Renderer>().material = mat;
23.     }
24.  
25.         [ClientRpc]
26.         void RpcSetMaterial(Material mat)
27.         {
28.           GetComponent<Renderer>().material = mat;
29.         }
30. }
31.  

 

ah.. but that misconception is one reason not to do this. Passing a component such as a Transform would pass by reference, not by value. So the other end would get a reference to its local instance of the transform with the local values, not the values from the source object.

 

everything would by synced by reference, not by content