Component Collision isn't Replicating | Net Dormancy on Component?

Development Programming & Scripting Multiplayer & Networking
1

After moving a component of with the “SetRelativeLocation” node (running on the server), the collision space is not replicating. It does replicate the location of the component, but not the collision.

The image below shows both the server and client. The server has moved the component, and the client is able to still click into the old location and “hit” a collision on the component that has been moved.

3

Then is the collision on the origin instead of the relative location?

4

All components have replication.

As I investigate further, I noticed that sometimes the collision space is being updated to the client. I am going to try that networking “dormant” technique. Does anyone know how to enable net dormancy to a specific component? It doesn’t seem the option is available for the component of an actor :frowning: . I’m very clueless, but here is the goal now :slight_smile:

  1. Client Requests to Move Object
  2. The server allows it
  3. Client moves object
  4. Client ends Movement
  5. Client requests replication dormancy force check
  6. The server validates the Client has moved the object within permissions
  7. The server replicates/broadcasts the replication to all clients.

https://i.imgur.com/Q18MQLT.png

5

Make sure it’s reliable, make sure it’s called as a multicast on the clients… did you ?

6

That fixed it! Thank you Neongho!

7

Awesome dude!