PDA

View Full Version : Lag in Chat and Notes with 8 players - not seen previously



Reg
December 23rd, 2020, 02:32
Hi

Our group that has recently upgraded to Unity has now also expanded to 8 players.

This week we all noticed that the chat window is extremely laggy - to the extent of 50-70 seconds from time of type to time of echo and visibility to others

The PC notes are also laggy, though not to the same extent.

Dice rolls are also slower to appear than when clicked.

Is this something we have done with content loaded, or is it a network speed issue or possibly some other thing?

Not sure if it warrants a bug report at this stage.
?

Trenloe
December 23rd, 2020, 09:46
Things that appear in chat generally have to go from the player initiating it, to the GM, then back out to all the players. Even for the player doing the action. So if Network speed isn't great, the GM instance is overloaded (doing other things, a player joining, sharing maps, loading a module, opening a massive data list, etc., etc.), a player instance is lagging and taking time to display messages, etc. then you could experience lag in data appearing in chat. When it happens let the GM know and ask them what as happening at that time to see if there is something specific that is causing it.

Moon Wizard
December 23rd, 2020, 16:13
If you can grab GM and player logs for both sides when the issue is happening to that specific player, we can check to see if there is some sort of network issue going on. (i.e. /console, and click Compile Logs button.)

Alternately, it might be some sort of over the network infinite loop scenario that gets exacerbated by having lots of players.
* Are you running any extensions?
* If so, can you try running without the extensions to see if you get same issue?
* Either way, can you keep an eye on what action might be triggering? (sharing a specific image, combat tracker interactions, voting, anything...)

Basically, if we can narrow down the places to look, we can see if there is something happening that shouldn't be.

Thanks,
JPG