Description

A user has reported an issue where Possession replication or Character Movement replication, unsure of which, is not working properly for some clients. It seems to work fine for the first client but does not for any past that. It requires the possession change to occur on one of the affected clients to occur.

Regression? No
This occurs in 4.19 and 4.20

Note: when attempting to reproduce this using the project in Main (4.22) this is blocked by a crash occurring, related to an access violation. That callstack can be found in the attached files.

A workaround is to set the cvar net.ShareShadowState to 0, though this will likely negatively impact server performance.

Steps to Reproduce
  1. Download the attached project
  2. Set the number of players in the Play settings to 2 and enabled Dedicated Server
  3. Press Play
  4. In the first client (the window still docked in the editor) Press K to Possess the character
  5. Press K again to unpossess the character
  6. Note that the character begins moving via the AI Controller again
  7. On the second client, repeat steps 4 and 5
    Result: After unpossessing the character on the second client, the AI controller's movements are no longer replicated to the second client
    Expected: The AI Controller's movement are replicated properly to the second client, as with the first.

Have Comments or More Details?

There's no existing public thread on this issue, so head over toAnswerHub just mention UE-66313 in the post.

1
Login to Vote

Unresolved
ComponentNetworking
Affects Versions4.194.204.21
Target Fix4.22
CreatedNov 8, 2018
UpdatedNov 12, 2018