Page 1 of 1

Input delay/freeze bug

Posted: Fri Mar 10, 2017 10:08 am
by smittn
Hey /tg/ I've had an ongoing problem that I've never been able to solve so I'm asking here if anyone else has ever experienced this or knows a work-around/fix.

At random times during a round any input I try to send to the server gets ignored. I can see people move and talk around and at me normally but I cannot respond, move, use commands, and so on. I asked about this on supportbus and atleast one other person has said they've experienced this. The best way around this seems to be spamming connect and that takes 10-20 seconds to regain control.

What I've ruled out that could be causing this:
Shaky internet - I've had two different ISP's and a solid internet connection, different routers/modems as well. I tested for packetloss by pinging google while this was happening and it was at 0%.
Byond version - I've had this on a previous version, the new stable release, and now the beta release and it happens across the board.
/tg/ exclusive bug - Tested on Bay and some others (including one I hosted myself albeit on like 8month old tgmaster code)

Really scratching my head here so if you guys can help I would appreciate it as it makes muh favorite server unplayable.

Re: Input delay/freeze bug

Posted: Fri Mar 10, 2017 10:31 am
by kevinz000
traceroute to tg servers maybe?

Re: Input delay/freeze bug

Posted: Fri Mar 10, 2017 11:07 am
by Dax Dupont
kevinz000 wrote:traceroute to tg servers maybe?
I'd run an continuous traceroute while playing with something like MTR https://en.wikipedia.org/wiki/MTR_(software).
Better for packet loss detection and all.

Re: Input delay/freeze bug

Posted: Sat Mar 11, 2017 12:19 am
by smittn
How would I traceroute through the byond address? Doesn't seem to recognize anything I try to put in.

Re: Input delay/freeze bug

Posted: Sun Mar 12, 2017 3:57 am
by smittn
Got around to using a VPN to connect to the server, seems to have fixed the problem so I'm assuming its a DNS thing.

Re: Input delay/freeze bug

Posted: Sun Mar 12, 2017 4:01 am
by Haevacht
Command prompt ipconfig /flushdns
Low chance it'll work but eh.

Re: Input delay/freeze bug

Posted: Sun Mar 12, 2017 4:10 am
by MrStonedOne
smittn wrote:How would I traceroute through the byond address? Doesn't seem to recognize anything I try to put in.
just do the host name part, bagil.tgstation13.org or sybil.tgstation13.org (atm they both go to the same ip, but that won't always be the case) I can't remember if i have them blocking pings, but at the least you should find out the latency to the gateway they connect to.

Re: Input delay/freeze bug

Posted: Sun Mar 12, 2017 4:34 am
by kevinz000
MrStonedOne wrote:
smittn wrote:How would I traceroute through the byond address? Doesn't seem to recognize anything I try to put in.
just do the host name part, bagil.tgstation13.org or sybil.tgstation13.org (atm they both go to the same ip, but that won't always be the case) I can't remember if i have them blocking pings, but at the least you should find out the latency to the gateway they connect to.
Is this why I kept getting firewalled

Re: Input delay/freeze bug

Posted: Sun Mar 12, 2017 5:36 pm
by smittn
Haevacht wrote:Command prompt ipconfig /flushdns
Low chance it'll work but eh.
Did not work
MrStonedOne wrote:
smittn wrote:How would I traceroute through the byond address? Doesn't seem to recognize anything I try to put in.
just do the host name part, bagil.tgstation13.org or sybil.tgstation13.org (atm they both go to the same ip, but that won't always be the case) I can't remember if i have them blocking pings, but at the least you should find out the latency to the gateway they connect to.
So that worked, and pinging is blocked. So here is what I got:

During the freeze issue I did a trace
http://imgur.com/a/BDK6t

and I reconnected and did it while I could play and got
http://imgur.com/a/2BAOA

So yeah its definitely a hop on the way over, any ideas on how to ignore that one jump?

Re: Input delay/freeze bug

Posted: Mon Mar 13, 2017 1:18 am
by MrStonedOne
I'll send some emails around to the people who control the routers between those two points (it could be the one showing up slow, or it could be the one before it) and maybe somebody will kick the router.

Re: Input delay/freeze bug

Posted: Mon Mar 13, 2017 2:05 am
by MrStonedOne
Odds are they will email back for a MTR report. MTR is like traceroute, but more sustained. rather than do 3 pings, it just constantly pings each hop until you stop, once per second or so.

WinMTR is a good one for windows, or mtr on linux (apt-get install mtr (iirc))

Re: Input delay/freeze bug

Posted: Mon Mar 13, 2017 4:52 am
by smittn

Re: Input delay/freeze bug

Posted: Tue Feb 13, 2018 4:08 am
by RandomMarine
Excuse the necropost, but I've also been getting this exact same issue for the past year or two. /tg/ only, even on the recently-launched Terry. It's really been the reason I've been observing 99% of rounds because with my luck, this happens every time I'm in a dangerous situation.

https://pastebin.com/EvQeXJx0 - This report's from about an hour and a half of observing where at least two of these disconnections occurred.

Re: Input delay/freeze bug

Posted: Tue Feb 13, 2018 4:28 am
by oranges
fucking telia

Re: Input delay/freeze bug

Posted: Sat Feb 17, 2018 3:09 pm
by yorii
oranges wrote:fucking telia