#ClientRPC not being called
1 messages · Page 1 of 1 (latest)
Yes other clients are getting it. I just removed virtual to test as well, same case
It seems like the only one not getting it is the host client
I can just call the implementation method on the host manually, but I don't want to do that in case this could somehow be a bug and it get fixed later, then my function gets called twice. I only suspect its a bug because on the docs it says that the host should receive the clientRpc call too, but maybe im doing something wrong
that is odd. can you try it with just a straight clientRPC call from the host? if it gets called the host should be getting it
sure ill set up a test script really quick
Huh, now im even more confused. So on the test script, it works as expected. I removed all my checks and just called the RPC on my actual script, and its still not being called
So yours is getting sent by the host but not received?
In both theses cases, the host is sending the RPC (no other clients connected) and then on my script, it does not receive the call, but on the test script, it does
I can confirm RPC sent gets logged too
weird. I dont see anything wrong with the code itself. both scripts are on the same object?
I just put them on the same object, it stopped working....
progress, lol
True haha
This is the component structure at the moment... ignore the component names, very similar i know lol
And I know the RPC is getting sent, because other clients receive it
Except my own (host)client
I don't suppose its parented to anything?
nope
start removing scripts until the RPC test starts working again
sigh
So, it was one of my fundamental script, which concerns me slightly.
Turns out, in my relevancy checks, I'm skipping the server, meaning the host client (which is a server) and any objects are never relevant to the host client
Thank you for the help, I never guessed it could of been one of my other classes, cause as far I knew, everything worked fine (the trickyness of the server being authorative and the host client being that too, makes the illusion that things are still relevant). I guess I have to be more careful!
Has anyone else noticed that setting the name value on a networked object doesn't work?