I'm having trouble connecting a room on
I'm having trouble connecting a room on poor cellular connections. It has enough bandwidth for UDP traffic (youtube streams), but fails to connect to a room. Is there any failsafe?
5 Replies
there's also another wrinkle to this: the room marks itself as connected (or connects), but it doesn't receive TCP traffic (when a lot of models/clients are connected). Then, after about 5 mins, it disconnects and throws the 'failed to connect' error. Failing gracefully would be appreciated.
room servers don’t use TCP at all. it’s all UDP and the connection has a 5 second heartbeat timeout
is it possible the issue could be something else? can you show me the logs you’re getting more specifically “Failed to connect” is not an error we log
@Max I have about 250 chaos monkeys from a batch build, all monos with models, single realtime sending Vector3s every 3-7 seconds. They each have two ints, and a Vector3. The two ints are identifiers, Vector3 is the only thing thats continuously updated (every 3-7 sec). I'm not sure what the maximum is, but if I have one or two in a room, and a poorly connected client connects, no problem. But all of them at once, it leads to the aforementioned slow fail.
Hypothesis: the client gets overloaded with loading all the models at once and fails. If there was a way to drip them in piecemeal, that would probably resolve this situation.
To emphasize, the CMs are on a stable connection and run per spec, the problem are weakly connected clients. If a client is on WiFi, no packet loss, runs per spec.
we’re about 2-3 weeks away from shipping our network profiler that will help with this one but I think your thesis is accurate
that sounds like a lot of data for anyone with a weak connection