Actor deleted/respawned on client with no reason.

Hey,

I get a very strange behavior on my networked game.

When moving my main actors on the server, they get deleted on the client (only) and respawned when moving back toward the origin.

On the server everything is going well, the pb occurs only on the clients.

The deletion seems to happen a few seconds after the actor is moved at a bad place, so i makes me think of some garbage collection gone mad.

It happens not to far away from the origin (all coordinates less than 20 000), so not a big numbers problem here.

The problem shows in PIE as well as in the packaged game (tested with server and client being on two different computers).

I made a short video showing the problem:

https://www.youtube.com/watch?v=jhBW1cWV1TU

I posted this in the bugs section because i can’t see any reason why the client would take the decision to remove an actor by itself.

Any idea of the reason of this behavior ?

Thanks

Cedric

Hi, this is still happening and is very penalizing as it limits the playable area with clients.

Any idea ?

Thanks

Cedric

I’ve seen this as well with a replicated actor. When I have the actor stop moving after about 3 seconds the client’s actor gets deleted. This appears to happen when the actor is no longer relevant. Try setting bAlwaysRelevant=true in c++ or checking the always relevant checkbox on the actor in blueprint.

Hey,

Thanks, it seems that since 4.20 this is no longer enough.

I also had to max NetCullDistanceSquared.

Cheers

Cedric