Unless a property is set to REPNOTIFY_Always, we compare the property's received value to the current value on the client before calling the OnRep function. However, when determining if a fast array ...
In FReplayHelper::ReplicateActor, we check Connection->ClientHasInitializedLevel(Actor->GetLevel()) to see if the actor should create a channel or not. However, the DemoNetConnection does not have a ...
See linked UDN for more info. This issue was reported for Iris, but I believe package map errors occur in the current replication system as well. ...
Based on the licensee's report, the crash seems to be occurring due to the WorldDataLayers actor, and setting this actor to never be dormant seems to resolve the issue. ...
There seems to be an issue with replicated attachments ending up causing cyclical setups resulting in crash on clients. It was reported for 5.2 but even after patching up code it seems to occur. ...
When calculating an actor's NextUpdate time, a random delay is added: ActorInfo->NextUpdateTime = World->TimeSeconds + UpdateDelayRandomStream.FRand() * ServerTickTime + NextUpdateDelta; If this d ...
This issue seems to occur due to the client keeping the NetGUID for the class/object, while the server will clean up this NetGUID during travel. When the client sends the class and its NetGUID as pa ...
The issue seems to occur when a replicated child actor is received on the client before its parent. The child actor will first be spawned at its correct global position, with its root component's p ...
The buffer start time is calculated by subtracting the TimeBufferHintSeconds from the stream length: const uint32 BufferStartTimeMS = UE::LWC::FloatToIntCastChecked<uint32>(FoundReplay->StreamInfo.L ...
This seems to be the same issue as was reported in [Link Removed], as enabling net.ResetAckStatePostSeamlessTravel resolves the issue. However, it was recently reported that disabling net.FilterGuid ...