net.Iris.ReplicationWriterMaxAllowedPacketsIfNotHugeObject
net.Iris.ReplicationWriterMaxAllowedPacketsIfNotHugeObject
#Overview
name: net.Iris.ReplicationWriterMaxAllowedPacketsIfNotHugeObject
This variable is created as a Console Variable (cvar).
- type:
Var
- help:
Allow ReplicationWriter to overcommit data if we have more data to write.
It is referenced in 1
C++ source file.
#Summary
#References in C++ code
#Callsites
This variable is referenced in the following C++ source code:
#Loc: <Workspace>/Engine/Source/Runtime/Experimental/Iris/Core/Private/Iris/ReplicationSystem/ReplicationWriter.cpp:52
Scope (from outer to inner):
file
namespace UE::Net::Private
Source code excerpt:
static int32 GReplicationWriterMaxAllowedPacketsIfNotHugeObject = 3;
static FAutoConsoleVariableRef CVarReplicationWriterMaxAllowedPacketsIfNotHugeObject(TEXT("net.Iris.ReplicationWriterMaxAllowedPacketsIfNotHugeObject"), GReplicationWriterMaxAllowedPacketsIfNotHugeObject,
TEXT("Allow ReplicationWriter to overcommit data if we have more data to write."));
/*
* net.Iris.ReplicationWriterMaxHugeObjectsInTransit
* There's a tradeoff mainly between the connection characteristics to support and normal object replication scheduling when tweaking this value.
* On one hand you don't want to end up stalling object replication because the top priority objects are huge. So you want to be able to keep replicating huge objects during the maximum latency, including latency variation, and packet loss scenarios