When recording a checkpoint, it is treated as an initial replication, as all the changed properties since the channel was opened need to be recorded. This normally results in any initial only proper ...
This is due to the same reason behind [Link Removed], as the stack object is passed to MARK_PROPERTY_DIRTY rather than the array property's owner. ...
When adding late joining clients, the engine checks the originally requested EPlaySessionWorldType, rather than checking whether or not the session is currently simulating or not. This means if the ...
Changing the global time dilation in a multiplayer game affects the rate at which actors are considered for replication, and setting it to 0 will even cause replication to stop entirely (unless the ...
In [Link Removed], it mentions that only the instance in the editor viewport supports switching to Simulate In Editor when running multiple instances in PIE. However, rather than showing that instan ...
AActor::AddReplicatedSubObject will ensure in this case if the actor doesn't set bReplicateUsingRegisteredSubObjectList, but there is no equivalent check in AActor::AddActorComponentReplicatedSubObj ...
When the actor goes out of dormancy, it will replicate its push model property, even if it hasn't been marked as dirty. In this case, it seems the value of the property is not written to the shadow ...
Because the component's subobjects are replicated before the component, the content block for the subobject is received before the component has been created on the client. Since this subobject is c ...
It looks like the "Server Only" emulation settings are being applied to the client after a travel. When doing a server travel with the TRAVEL_Relative travel type, the NextURL created in AGameModeBa ...
With net debug drawing enabled, an extra debug box is drawn around some actors to indicate if the actor is always relevant or if it is distance culled. However, the strange size of this box makes ne ...