krefsar
New member
The ThrowableItem component does a NetworkSpawn of the thrown object from the master client's side. That part is working fine.
However, there's some logic where the master client's scheduler changes the thrown object from the start layer to the thrown layer after a delay. That layer change works fine on the master client's side, but on the remote client the layer change never happens. Is there some sort of additional component needed so that the instantiated thrown object will sync its layer across the network?
As an example, if a thrown item starts in the IgnoreRaycast layer and is set to the Default layer after a delay of 0.1s, the remote client will see the thrown item be instantiated in the IgnoreRaycast layer, but it will remain there and never change to the default layer.
However, there's some logic where the master client's scheduler changes the thrown object from the start layer to the thrown layer after a delay. That layer change works fine on the master client's side, but on the remote client the layer change never happens. Is there some sort of additional component needed so that the instantiated thrown object will sync its layer across the network?
As an example, if a thrown item starts in the IgnoreRaycast layer and is set to the Default layer after a delay of 0.1s, the remote client will see the thrown item be instantiated in the IgnoreRaycast layer, but it will remain there and never change to the default layer.
