Iris Replication Filtering

Development Programming & Scripting
,
1

Hi all!
I can’t figure out how to work with the “Iris Replication” system. I connected it using this article:
Migrate to Iris in Unreal Engine | Unreal Engine 5.4 Documentation | Epic Developer Community .
It seems to be connected to the log:
LogNet: InitBase GameNetDriver (NetDriverDefinition GameNetDriver) using replication model Iris
LogIris: Display: Iris ReplicationSystem[1] is created.
Next I try using this article:
Iris Filtering in Unreal Engine | Unreal Engine 5.4 Documentation | Epic Developer Community .
Initially, all actors are replicated as usual. For example, I want to make sure that some actor stops replicating to a certain connection, as I understand it, filters are needed for this. I tried different options and could not achieve the desired result. As a result, I have this method.

void AMyIris::AddUnit(AActor* actorPtr, APlayerController* controllerPtr)
{
UReplicationSystem* ReplicationSystem = UE::Net::FReplicationSystemUtil::GetReplicationSystem(actorPtr);
UActorReplicationBridge* ReplicationBridge = UE::Net::FReplicationSystemUtil::GetActorReplicationBridge(actorPtr);
UE::Net::FNetRefHandle RepActorNetRefHandle = ReplicationBridge->GetReplicatedRefHandle(actorPtr);

UE::Net::FNetObjectGroupHandle GroupHandle = ReplicationSystem->CreateGroup();
ReplicationSystem->AddExclusionFilterGroup(GroupHandle);

uint32 ConnectionId = controllerPtr->GetNetConnection()->GetConnectionId();
ReplicationSystem->SetGroupFilterStatus(GroupHandle, ConnectionId, UE::Net::ENetFilterStatus::Disallow);	
ReplicationSystem->AddToGroup(GroupHandle, RepActorNetRefHandle);

}

I get the system, then the bridge, then the actor’s identifier. Then I create a group and add this actor to this group. Then I add the group to the system and give it a rule to turn off the actor. The tutorial uses the AddGroupFilter method… but there is no such method, probably referring to AddExclusionFilterGroup in this case. As a result, the actor continues to replicate to the connection, although logically it shouldn’t.
Thanks in advance!

2

seeing the Iris created line only confirms the system exists, filtering needs an explicit assignment before any actor changes behavior. the docs path is a custom NetObjectFilter subclass registered in config, then per-actor filter handles that decide connection visibility, without that the default filter keeps replicating everything.

for the AddUnit case, verify the controller connection has a valid filter handle and the actor is added to the right bucket, and log the filter decision per connection during a two-client test to see whether the call even reaches the filter.

you can also look at Iris Readiness Kit, an Iris replication plugin that maps the filtering setup pieces that stay on defaults: Iris Readiness Kit — Audit Your Project Before Enabling Iris Replication | Fab there’s a shorts playlist on iris filtering basics too: https://www.youtube.com/playlist?list=PLWrCzz951TwA