In ReadyForDormancy, we check if the replicator has any change lists or property updates that haven't been acked. However, these checks are not made in CanSkipUpdate, which can result in the object skipping its updates while it has unacked changes, preventing the actor from going dormant.

Steps to Reproduce

Enable push model replication and net.PushModelSkipUndirtiedReplication for a project. Create an actor with some replicated property. Set this actor to DORM_Initial and statically place it in the map.
With bad network emulation settings, flush net dormancy on the actor and update its replicated property on the server.
Expected: the property will replicate, and the object will go dormant again
Actual: the property will replicate, but the object will go dormant only after a noticeable delay

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-188947 in the post.

Login to Vote

ComponentUE - Networking
Affects Versions5.3
Target Fix5.4
Fix Commit23781868
CreatedJun 16, 2023
ResolvedSep 1, 2023
UpdatedOct 2, 2023
View Jira Issue