So I have some reports that people are kicked more often that I would expect, and I have experienced it a bit myself now with a couple of days with really choppy internet. At some random point I'll get the Send issue: NoConnection, then Connection to server was lost. ultimately stopping the connection completely, which is of course expected, however I feel like it happens a bit too quickly if that makes sense?
Like one small hickup and then suddenly you're out. Since my game does not have any reconnection logic this is quite critical, so I'm wondering if there's a good way to give a bit more leeway before kicking anyone?
#Clients kicked a little too aggressively with choppy internet - is this configurable?
vapid current
urban tusk
You can increase Timeout parameter, but default is already 15 seconds I believe.
http://jagt.github.io/clumsy/
maybe you can help debugging it yourself with this
and check how much data you are sending & try to optimize that, i.e, make structs smaller, make communication less frequent, and so on
vapid current
and check how much data you are sending & try to optimize that, i.e, make struct...
Ah thanks, I see timeout is 5 seconds default with FishyFacepunch! Doubled that to 10 and then let's see what happens 🙂
quick cedarBOT
KO₿I received thanks.
vapid current
Actually, I don't think it was that simple... It looks like the timeout might only be for establishing a connection?
Yeah when I dig a little bit deeper it seems like the timeout is essentially only used in ClientSocket.StartConnection...
@shut nebula is it unique to FishyFacepunch that connections are kicked by a single NoConnection (which is seemingly what happens, not sure)
shut nebula
Each transport handles timeouts differently, which I have often no control over. If you're getting kicked that's steam doing it.
There might be a hidden setting in facepunch. I don't use it personally so I'm not sure but if there is something that can be exposed I'd be happy to make it happen
urban tusk
It could be also corrupted networking/RPC, instance is if you use structs/classes that are not serializable inside RPC, it can cause desync and therefore disconnect (maybe, not sure if that could cause disconnect though)