Search Issue Tracker
Fixed
Votes
5
Found in
Issue ID
696932
Regression
No
ClientRPC isnt called for local client for networked scene objects
ClientRPC doesnt work for network objects placed in the scene.
Comments (8)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
nsmith1024
Jul 05, 2016 18:53
ClientRpc is not working, can someone fix it please, how can anybody make a network game without this? I cant do anything because this basic function dont work.
nsmith1024
Jul 05, 2016 12:59
Its happenning in 5.4.0.b24
i cant run my game because i cant do any clientRpc calls it gives error. Why does it show 2 Rpcs (RpcRpcSetLayerWeightClient) shouldnt it be RpcSetLayerWeightClient with 1 Rpc in the function name string?
Found no behaviour for incoming [ClientRpc:InvokeRpcRpcSetLayerWeightClient] on Player2@Owner(Clone) (UnityEngine.GameObject), the server and client should have the same NetworkBehaviour instances [netId=1].
UnityEngine.Networking.NetworkIdentity:UNetStaticUpdate()
[ClientRpc]
public void RpcSetLayerWeightClient(int layer, float weight)
{
animator.SetLayerWeight(layer, weight);
}
[Command]
public void CmdSetLayerWeightClients(int layer, float weight)
{
RpcSetLayerWeightClient(layer, weight);
}
shadiradio
May 26, 2016 23:20
This appears to be happening to me in the 5.4 beta.
Linetksy
Jan 29, 2016 16:30
Version 5.2.3f1 - Rpc not executed on local client
TomNCatz
Dec 19, 2015 07:28
5.3.1f1 issue still seems to be present.
TomNCatz
Dec 18, 2015 19:21
5.2.3f1 and I am still seeing this issue.
james69lemon
Sep 18, 2015 13:46
doesn't seem to be resolved for me either
quitebuttery
Sep 14, 2015 01:53
Is this resolved? It still happens to me on 5.2.