|
Notes |
|
|
|
I don't experience this issue on Debian GNU/Linux, and unfortunately there's not enough detail/logs in your original report about your environment to reproduce your issue.
- Which game(s) for the master server connection are affected?
- Is this Doomseeker in its default configuration? (Master server addresses set in configuration.)
If this issue is about Sonic Robo Blast 2, that upstream stopped maintaining their master server compatibility (0003958).
Unfortunately, I don't know how to guide you to post the standard output logs ("Starting Doomseeker. Hello World! :)") on Windows at this time. |
|
|
|
|
Quote from WubTheCaptain
Unfortunately, I don't know how to guide you to post the standard output logs ("Starting Doomseeker. Hello World! :)") on Windows at this time.
View → Log (Ctrl + L) works in the graphical user interface. |
|
|
|
|
[13:17:48] Starting Doomseeker. Hello World! :)
[13:17:48] Setting up data directories.
[13:17:48] Cache directory: *Censored*/AppData/Local/doomseeker/cache
[13:17:48] Config directory: *Censored*/AppData/Local/doomseeker
[13:17:48] Data directory: *Censored*/AppData/Local/doomseeker
[13:17:48] Loading extra CA certificates from '*Censored*/cacerts.pem'.
[13:17:48] Appending 2 extra CA certificate(s).
[13:17:48] Attempting to load plugins from directory: *Censored*/engines
[13:17:48] Loaded plugin: "Chocolate Doom"!
[13:17:48] Loaded plugin: "Odamex"!
[13:17:48] Loaded plugin: "Sonic Robo Blast 2"!
[13:17:48] Loaded plugin: "Turok 2 Remaster"!
[13:17:48] Loaded plugin: "Zandronum"!
[13:17:48] Listening to Zandronum's LAN servers broadcasts on port 15101.
[13:17:48] Loaded plugin: "Q-Zandronum"!
[13:17:48] Listening to Q-Zandronum's LAN servers broadcasts on port 15102.
[13:17:48] Initializing configuration file.
[13:17:48] Setting INI file: *Censored*/AppData/Local/doomseeker/doomseeker.ini
[13:17:48] Loading translations definitions
[13:17:48] Reading localizations definitions file: translations.def
[13:17:48] Loading translation "system".
[13:17:48] Translation loaded.
[13:17:48] Initializing IP2C database.
[13:17:48] Initializing passwords configuration file.
[13:17:48] Initializing configuration for plugins.
[13:17:48] Initializing IRC configuration file.
[13:17:48] Setting IRC INI file: *Censored*/AppData/Local/doomseeker/doomseeker-irc.ini
[13:17:48] Starting refreshing thread.
[13:17:48] Preparing GUI.
[13:17:49] Checking if IP2C database at '*Censored*/AppData/Local/doomseeker/IpToCountry.dat' needs updating.
[13:17:49] Please wait. IP2C database is being read. This may take some time.
[13:17:49] Init finished.
================================
[13:17:49] Parsing IP2C database: *Censored*/AppData/Local/doomseeker/IpToCountry.dat
[13:17:49] Total refresh initialized!
[13:17:49] Removing old update packages from local temporary space.
[13:17:49] Checking for updates...
[13:17:49] IP2C database read in 78 ms; IP ranges: 196041
[13:17:49] IP2C parsing thread has finished.
[13:17:49] IP2C parsing finished.
[13:17:49] Comparing IP2C hashes: local = aeca013c6eb838531099b9727f2187a0, remote = aeca013c6eb838531099b9727f2187a0
[13:17:49] IP2C update not needed.
[13:17:49] No new program updates detected.
[13:17:49] Program update detection & download finished with status: [0] Ok
[13:17:59] Error: Master server for Zandronum: Connection timeout (45.56.67.39:15300).
[13:17:59] Reloading master server results from cache for Zandronum!
[13:17:59] Error: Master server for Q-Zandronum: Connection timeout (70.35.196.63:15300). |
|
|
|
(0022223)
|
|
Zalewa
|
|
2022-05-19 21:43
|
|
It looks like something is blocking the UDP packets that communicate with the master servers, because the other connections that happen over HTTP work fine. The cause may be your anti-virus, firewall, router or the ISP. This is either a problem where the UDP packets never leave your computer/network, or they leave it but the incoming reply packets never reach your computer back.
It's difficult for me to guess where the packets may be getting blocked in your case, but maybe you can try temporarily disabling the anti-virus or maybe you recall changing something in the settings of the things I mentioned above?
You could also try checking if the problem is limited only to the master servers and if you can talk to servers directly, for example by trying to add this Zandronum server to the pinned servers: 88.198.7.58:10675. (Options -> Configure -> Pinned servers -> Select Zandronum -> Add -> double-click host and port and edit -> OK). Check if the server appears properly on the list as "[EB] Zombie Horde". |
|
|
|
|
|
Zalewa: This issue looks like 0003494. |
|
|
|
|
The attached patch 0001-udpsocketpool-Always-bind-to-host-0.0.0.0.patch is experimental. Please try it. It works on my Debian GNU/Linux machine. Zalewa, does it work for you on Windows?
Possibly the easiest for OP if Zalewa could publish a beta release binary (.exe) with that patch for OP, unless OP is also capable of compiling from source with the patch applied. |
|
|
|
|
|
Also be mindful of 0003654 with the attached patch. I did not test for that one. |
|
|
|
|
|
|
|
|
|
Wait, Zalewa!? you're Thinking that it's the Same Issue as that RTC Connecting Error I Just Can't Fix on Discord!? |
|
|
|
(0022229)
|
|
Zalewa
|
|
2022-05-20 20:08
|
|
@Wub I doubt that this issue is related to socket->bind(); It's more probable and apparent that the OP has networking issues.
@Oceanboy06 Well, I don't know the specifics of WebRTC but from what I see this protocol also relies on UDP. So if your Discord has problems with RTC then it's indicative that you may have a broader problem with UDP in general. If you don't mind setting up a remote desktop through TeamViewer I can take a look at your computer, just catch me on Discord: robikz#9390. I can't promise anything tho. |
|
|
|
|
|
Resolving as invalid per OP's WebRTC issues: This ticket is unlikely to be a bug in Doomseeker, but seems like a support request. |
|
0001-udpsocketpool-Always-bind-to-host-0.0.0.0.patch (759) 2022-05-20 09:52