Descriptive Problem Summary:
I have been having consistent disconnection issues with BYOND games for a few months now, and have been trying to troubleshoot things to the best of my ability to solve it. I cannot idle for too long without being disconnected with a "Connection failed. Reconnecting in 10 seconds..." message, or at the very least, realize my screen / chat features are frozen and it takes a few minutes for everything to flood in at once, including any actions I have seen or chat messages.
I've tried what I can to research the issue to see if there was a definitive fix around, referencing the following two threads.
Losing connection for no reason [Dream Seeker] - http://www.byond.com/forum/post/1341422
Possible connection time out bug. - http://www.byond.com/forum/post/2021781
What games I have tried tried?
- SS13
- Final Revelations
- Curtain Call
The problem is a lot more noticeable on Finale Revelations (FR) and Curtain Call (CC) than it is on SS13, due to how SS13 isn't that much of an idle game like FR and CC can be.
Due to how FR and CC function, there are benefits to idling under AFK with the client connected / minimized due to how stat gaining works there, but I cannot maintain an "AFK" connection without using some form of automated input, such as an autoclicker, to sustain a connection. It even happens while I am on my computer, where I could be watching a 10 ~ 30 minute youtube video on my other monitor, click back into CC and either have the frozen client or a connection failed.
BYOND Version: 513.1542 (I was originally somewhere in the 1520 range before troubleshooting)
Operating System: Windows 10 Pro - Version 21H1
ISP: Comcast
Things I have done to try fixing the issue myself:
- Clearing my Cache
- Upgrade to 513.1542
- Clean install of 513.1542 and 514
- Attempted using a different skin file for CC
- Making sure Dreamseeker / Daemon were both allowed on Windows Firewall
- Upgraded my motherboard (ASUS X570 TUF)
- Tested with both a wired and wireless internet connection
- Clean install of Windows 10 on a new hard drive (This and the motherboard were things I already had planned, not specific to fixing Byond)
- Ran Winmtr based on MSO's post in referenced thread
- Ran a Traceroute to the CC server, and compared results with their Host and friends with similar results
- Contacted Comcast's support and all they essentially did was restart my modem and try to tell me the issue was my ethernet cable, despite clear explanation that my issue was trying to maintain connection to a certain IP address and I wasn't losing total internet connection, given I can still watch youtube and play Warcraft but DC only on Byond games.
ID:2686594
 May 26 2021, 5:54 pm
|
|
The client isn't minimized at all times. I could have the window up on my other monitor and I still get disconnection issues.
| |
Packet loss really sounds like the culprit to me. The continuous connection BYOND requires is gonna be highly susceptible to that kind of problem. It must actually be pretty bad if ordinary error handling in your TCP/IP stack isn't handling it.
| |
Is there a better way to test for packet loss?
| |
BYOND strictly uses TCP, whereas WoW might be using some UDP for connections, and stuff like YouTube is gonna be using HTTP requests that the browser will try to resend if they fail. If your modem or cable is dying it's possible you have enough small-scale packet loss that it's severely disrupting TCP.