GameplayDebuggerCategoryReplicator seems to be not replicated.
Grid filtering may affect the GameplayDebuggerCategoryReplicator.
In our environment, we can avoid this by using DefaultEngine.ini:
```
[/Script/IrisCore.ObjectReplicationBridgeConfig]
+FilterConfigs=(ClassName=/Script/GameplayDebugger.GameplayDebuggerCategoryReplicator, DynamicFilterName=None)
```
[Attachment Removed]
再現手順
You may test this by:
- Enabling Iris replication.
- Creating a World Partition level.
- Running PIE in client mode.
- Moving the player character far away from (0, 0, 0).
[Attachment Removed]
Hi,
Thank you for the report! I can confirm this behavior is present in 5.7, but it should be fixed in later engine versions.
There was a recent fix made to AGameplayDebuggerCategoryReplicator for Iris at CL 47780546 in UE5/Main. This was mainly to ensure that the gameplay debugger’s traffic didn’t count towards the bandwidth limit, preventing it from saturating the connection and slowing down replication.
However, that change also set bOnlyRelevantToOwner=true for AGameplayDebuggerCategoryReplicator, which will prevent it from using spatial filtering.
You can try integrating this change, but if you’re only seeing issues with the debugger getting filtered out, then I do think your current workaround of manually disabling spatial filtering also makes sense.
Thanks,
Alex
[Attachment Removed]