Unreal Engine Issues

Include option to use ViewTarget's location when determining relevancy

When determining relevancy for an actor based on distance, the location of the player's view point is always used if it is available, rather than the location of the view target (see FNetViewer and ...

Multicast RPCs called from standalone instance are not recorded into replays

This seems to have regressed because of the fix to [Link Removed]. Because UWorld::InternalGetNetMode now only returns the DemoNetDriver's NetMode when it is recording and in its tick, the multicast ...

Duplicate child actor created on client in editor

This seems to be related to the fix for [Link Removed]. Part of that fix made sure that the child actor component recreates the child actor when GIsReconstructingBlueprintInstances is true, as previ ...

Check hit in FNetworkObjectList::MarkActiveInternal for dormant actor after seamless travel

When seamlessly traveling, FNetworkObjectList will have its data cleared. However, because FNetworkObjectList::Reset is called before FNetworkObjectList::ResetDormancyState, AllNetworkObjects will b ...

Unable to play replays with custom GameNetworkProtocolVersion set at runtime

It seems that when comparing the custom versions for a replay (in the "operator<<" defined in ReplayTypes.cpp), the value retrieved from the FCurrentCustomVersions is not the value set at runtime, b ...

Subobject of garbage actor may be reassigned to newly created actor on the client

When an actor channel is cleaned up, the actor and its subobjects in the CreateSubObjects array are destroyed/marked as garbage in DestroyActorAndComponents. However, default subobjects are not adde ...

Attachment changes on the client for non-replicated actor may be stomped by replication

For projects relying on attachment to be performed on the client before the server, such as to prevent latency, this can result in attachments being overridden when USceneComponent::OnRep_AttachChil ...

Blueprint actor component properties do not automatically flush dormancy when set

UK2Node_VariableSet::ShouldFlushDormancyOnSet only returns true for classes that derive from AActor. This leads to inconsistent behavior, as the owning actor will not have FlushNetDormancy called on ...

Push Model may prevent actors from going dormant

This seems to happen because FObjectReplicator::ReadyForDormancy will continually return false while FObjectReplicator::CanSkipUpdate returns true. In ReadyForDormancy, the actor's SendingRepState h ...

The RemoteRole will not be sync correctly when the push model is turned on