Iris - Initially dormant actors not replicated if dormancy is not enabled

With dormancy disabled, it seems that actors marked as dormant are not registered as expected with Iris. Even if the actor is woken up or flushed before making changes to its properties, the client won’t receive the changes.

This seems to occur due to Iris using FReplicationSystemUtil::FlushNetDormancy to start replication for any initially dormant actors, as UNetDriver::FlushActorDormancy returns early if dormancy is disabled.

This does not occur with the generic replication system, as UNetDriver::ServerReplicateActors_PrioritizeActors only skips dormant actors if GSetNetDormancyEnabled is true.

• Enable Iris but disable network dormancy
  • net.Iris.UseIrisReplication=1 and net.DormancyEnable=0
• Place a replicated actor in the map and set its default NetDormancy value to DORM_Initial
• On the server, change the value of a replicated property on this actor

Expected: the client will receive this new value

Actual: the client does not receive the property’s new value