WHAT
Join us for our weekly Unreal Engine livestream. This week we’ll be joined by Ryan Gerleve and Dave Ratti to discuss general server optimization in UE4, as well as techniques and solutions to improve your Actors’ performance in a networked environment. In addition to this, they’ll provide insight into the Replication Graph and answer any questions you may have.
Are there any plans to refactor GameplayCues to use some modern engine facilities ? (AssetManager).
Any particular reason why, replication of variables/dispatching of RPC is single threaded ?
If there is a lot, and I mean a lot of replicated properties, does all of them must be iterated at the end of tick to see if the changed, or is there way to tell engine, “look I’m sure it didn’t changed and I will tell you when it does”.
How can we force relevancy for actors in Replication Graph for specific connections, regardless of net cull distance - while still benefiting from the priority-based replication?
I’ve created nodes which add actors to relevancy, but they are still culled by Net Cull Distance regardless. Currently the only way around this is to force replication graph to set DistancePriorityScale to zero for the objects entire class. They are still culled by spatial nodes, but no longer benefit from priority-based replication.
Also, there are several legacy network relevancy conditions that exist in actors that replication graph still doesn’t support (such as objects the player ‘owns’ always being relevant to them regardless of culling) - will this stuff come back?
anyone have any idea where to find this timer value in the engine https://youtu.be/mT8VUVuk-CY?t=4328 ? to change from 32bit float to higher precision?
Did this video come out before the network PushModel? I’d be curious about tips/suggestions/etc regarding using the push model along side relevancy and dormancy. A lot of the internal engine classes use the pushmodel presumably to avoid the overhead of checking for replication changes.
Also, an unrelated question about dormancy and ForceNetUpdate();
How does dormancy interact with relevancy? Surely actors can’t be completely skipped by the network/replication logic when dormant if there are still moment to moment relevancy changes occuring, such as cull distance.
Does ForceNetUpdate(); circumvent the normal relevancy checks? (cull distance, etc)? Meaning when you ForceNetUpdate();, are you forcing replication to players potentially outside your relevancy bubble?
If not, and if the actor is then dormant, when a client comes into range of a dormant actor, how are they getting accurate state?
