Noel Stephens

@daalen Ahh, I am not sure if we had the type:feature label back then so perhaps feedback was the only option... but at that point we were handling other deeper...

@zachstronaut We are looking into this issue as a potential candidate for the next release after the up-and-coming v1.7.0.

For anyone still following this: #2874 imports the user submitted solution and this will be available in the next (v1.9.0) update (_we are currently working through the promotion steps for...

@zachstronaut 😸 You are great at finding obscure issues and in almost all cases they should be addressed. This one, I first need to get some form of confirmation on...

@zachstronaut So, you are saying that if you could spawn NetworkObjects on the client-side that your underlying issue would be resolved (_obviously the client instance doing the spawning would, by...

@rever96 Hello, I am looking at this issue and believe it has been fixed. If you wouldn't mind, could you use a development branch where I have made quite a...

@rever96 Thank you for including this zip. I will look at your implementation and see if I can replicate the issue on my side. From the sound of it, you...

@rever96 I understand. This is an issue that is deeper than change in ownership as it involves the change in ownership and synchronizing the transform during the change in ownership....

Are you making sure to change ownership when you exchange the ball from one client (or host) to another? The owner of the NeworkObject is the authority over the ClientNetworkTransform.

Hi @aidanhorton, Could you provide more details on the NetworkObject with the NetworkBehaviour containing the NetworkVariables not synchronizing properly? _(i.e. is it in-scene placed, when is is spawned, is it...