We’re noticing a server wide lag / stutter / hitch (whatever the technical term here should be) when players join in progress. Testing with friends we’ve found that all players in the game experience a brief lag at the same time that our friend begins to connect to the game from the lobby. From in game, there will be a lag spike, and then a few seconds later the elimination feed with say “{PlayerName} has joined the game!”
Steps to Reproduce
Play 7632-5434-5590 or another high activity game. Have another player load into the game, the joining player will go through the following stages when matchmaking:
Matchmaking: Joining server…
Preparing…
Preparing… Initiating travel to server…
Connecting…
A few seconds after the “Connecting” phase begins, the players in the lobby experience the lag spike.
Expected Result
Players joining a game in progress will not cause server wide lag.
Observed Result
Players experience a server wide lag spike, then a few seconds later a player has joins the game.
Platform(s)
All
Island Code
7632-5434-5590
Additional Notes
It may only happen as a result of players joining who already have save data and / or verse persistence data. All of the players we tested with have already built up some save data and verse persistence data.
We have the same problem, you’re not alone. We’ve spent FOREVER trying to figure it out and believe it may have something to do with some kind of persistence as well. Maybe mod bench etc kind of thing.
Hey Dilly, glad you brought this up! The PXCreative team has been experiencing the same issue with our “Ultra Red vs Blue” map (4470-6058-7690). However, we do not use any persistence devices on our map. We noticed these join in progress lag spikes start after the UEFN patch that introduced the analytics devices.
We’ve been trying to address this through various updates—such as enabling streaming, minimizing memory usage, and eliminating frequently triggered analytics devices—yet we haven’t been able to solve the problem. This issue has been a concern for us, as it negatively impacts the first impression of our map among players.
Thanks dilly, for highlighting this matter. We were under the impression that this was an isolated issue affecting only our map.
What info does Epic need? Are you going to ask questions or are you looking internally? This happens after a period of time has passed mostly, we think maybe when a lot of users come in and out kind of thing. Like there is some kind of table lookup that is happening and because it never gets purged or garbage collected on, it hitches the whole game just before the player is spawned.
