Lobby still has the bug, showing too many players in a game

[Kryo]

yeah,

i dunno how I should report as this is not in a log or replay. But zep should know what I mean.

What I can say:

Happens more often in game lobbies with many players (>6).

Happens more often if the FAF lobby seems to be laggy at the moment. (also will raise the chances of 0 ping (Nil))

Happens not if host kicks someone. Rather if someone loses connection by timeout or sth.

[Ze_PilOt]

There is this in the lua code :

Code: Select all

quietTimeout = 10000.0 # milliseconds to wait before booting people
maxPlayerSlots = 12
maxConnections = 15 # count doesn't include ourself.


Probably, FA fails to clean old connections, goes to more than 15 and crashes. I will try to increase the maxConnections and decrease the quietTimeout.

The server is sending "DisconnectFromPeer" command to each players, but maybe it's not enough for FA to kill them.

But at some point, it's up to the host to be very careful and kick observers and nil player as soon as possible.

[Kryo]

There is this in the lua code :

Code: Select all

quietTimeout = 10000.0 # milliseconds to wait before booting people
maxPlayerSlots = 12
maxConnections = 15 # count doesn't include ourself.


Probably, FA fails to clean old connections, goes to more than 15 and crashes. I will try to increase the maxConnections and decrease the quietTimeout.

The server is sending "DisconnectFromPeer" command to each players, but maybe it's not enough for FA to kill them.

But at some point, it's up to the host to be very careful and kick observers and nil player as soon as possible.

what does fa do if maxconnections is reached? is there a command:
if connections > maxConnections
crash game
end if;

?

[Ze_PilOt]

No idea but the crash message is clearly a memory allocation/interrogation problem.