-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent Connectivity with US Modem #1
Comments
Resolved by expanding the response detection evaluation to include partial strings: "ER" instead of "ERROR" or "CO" instead of "CONNECT" since random new-line characters were seen in modem responses and screwing up the string comparison. |
This is still an issue. 0.98 had code to strip newlines and buffered the output - I don't suppose you could print out the buffer variable when the timeout exception is thrown? |
I'm not sure exactly which is the buffer variable, but I modified the end of send_command, thusly: if (datetime.now() - start).total_seconds() > timeout: And get this output when a connection fails... Last string in buffer... Another attempt looked like this: Last string in buffer... |
Discussed at length on AssemblerGames, but adding here for tracking. There seems to be timing issues when using a US Dreamcast modem that reduce the odds of a successful connection to about 1 in 3. Some games (Maximum Pool, 4x4 Evo, Starlancer) won't accept even a successful connection, and hang up immediately after connection (rage quit). Logs attached.
BadGoodConnectionLog.txt
Starlancer-RageQuit.txt
The text was updated successfully, but these errors were encountered: