Having some issues with DDNet Client

[ijopr]

Hello!

Two days ago I had to reinstall Windows 10 64-bit due to filesystem problems, therefore I had to download DDNet Client again, but now I'm having some issues with it.

First of, it doesn't complete searching for servers, it basically always stops at 58 %. Secondly, I can't join some servers at all, and if it manages to connect to one server, it takes ages until it finished doing so. Standard client doesn't have any of those problems.

I tried both the 32-bit and 64-bit version, I also tried the nightly client. I deleted/downloaded the normal DDNet client several times, also deleted the teeworlds folder in appdata. Also I tried to disable windows firewall/av software, but nothing seems to solve this problem.

Any help would be appreciated, thanks in advance.

---

any clues?

[deen]

The only relevant difference here is that DDNet client uses a random port for connecting, while Teeworlds does not. Maybe your provider just doesn't like the random ports DDNet client chooses. Since you tried disabling your firewall, I don't have any other ideas.

Edit: Maybe you could try with your Laptop at someone else's home to find out if it's your internet connection.

[ijopr]

thanks four your reply, but my isp didn't change... before I reinstalled windows it worked perfectly... i'm also using the exakt same hardware

[ijopr]

Any more suggestions? I honestly don't want to reinstall Windows just because of that (because I'm running out of ideas as what could cause those problems), though I obviously prefer the DDNet client over the standard one... are there any other builds I could try? Or any similar clients I could use?

I would also like to mention that the "Internet" tab laggs a lot while it searches for servers (and, as I said, it always stops betwenn 50 and 60 %), the DDNet tab doesn't lag at all but I can't join every server it finds anyway... I might be able to join one out of ten servers I try.

[deen]

If you're on wifi you could try disabling the powersave function for your wifi card. Otherwise I believe it is a firewall issue (for example the Windows firewall).