Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

Export in CSV format

{{MigrateTranslation}}
<languages/>
<div lang="en" dir="ltr" class="mw-content-ltr">
This article aims to help you when you experience problems with DDNet.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Useful information for developers to debug problems are:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
# Crash/Assertion logs
# Hardware information (GPU, CPU, RAM, operating system (e.g. Windows, Linux etc.)) - The used GPU can always be found by pressing F1 after client start. It should be highlighted in purple text.
# Steps to reproduce the problem
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Crashes ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Crashes are unexpected shutdowns, that are most likely caused by a bug in the DDNet code, or in other software.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The rule of thumb is that, if you can reproduce the crash, you should reach out to the developers.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
See '''external links''' or create an issue on [https://github.com/ddnet/ddnet GitHub].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Since DDNet 16 for Windows the client might create a crash log or assertion log which can be found in the [[Special:MyLanguage/FAQ#Where_is_the_DDNet_config.2C_config_directory_or_save_directory.3F|config directory under "dumps"]].
Just send them to the developers and they might be able to find useful information out of them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the client crashes at startup, it is commonly a broken graphics driver (see the [[Special:MyLanguage/GFX_Troubleshooting| GFX Troubleshooting]]) or an antivirus software (search the internet for how to disable it for a specific application/DDNet).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''<small>Note: Not all crashes / bugs are caused by DDNet code, you should always keep your system and your drivers up to date. Only reproducable or bugs with a crash log, that indicates a bug in the DDNet code, can be fixed easily.</small>''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Graphics problems ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you experience graphics glitches, and the developers cannot reproduce them, there is a good chance that your graphics drivers are outdated, contain bugs or simply are abandoned by the hardware company.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You can still try the following thing:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''If you have a modern GPU try to update your drivers first, all of the following steps are fallbacks that also have drawbacks (e.g. worse graphics).'''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<pre>
Inside the client go on Settings -> Graphics
Under "Renderer" select OpenGL 1
Restart
</pre>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you prefer to have a more appropriate solution for your problem, visit the [[Special:MyLanguage/GFX_Troubleshooting|GFX Troubleshooting]] page, which analysis graphics problems more specifically and gives extra details.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== ALT + TAB problems ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is most likely a graphics driver problem. However you can still try to fix it by using "Windowed Fullscreen".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a special fullscreen mode, that makes the window act like it is fullscreen, even if it's not.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''<small>Note: There is a drawback on some systems. E.g. under Windows it might leave the Windows desktop compositor active, which results in less FPS, and in worst case
more input delay.</small>''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
<pre>
Inside the client go on Settings -> Graphics
Click on "Fullscreen" (or whatever you last selected) and choose "Windowed Fullscreen" instead
</pre>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''<small>(if you experience bugs changing this mode, just restart the game once and make sure "Windowed Fullscreen" is still selected)</small>''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Broken streaming ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you experience a bug with streaming DDNet over discord, you are most likely using a nvidia graphics card.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A user already reached out to discord, and they told him to:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://github.com/ddnet/ddnet/issues/4711#issuecomment-1046824198 '''Toggle off the "Use our latest technology to capture my screen" setting under User Settings > Voice & Video''']
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems finding DDNet in nvidia shadow play.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Make sure you actually use the nvidia card to play DDNet (press F1 after a client start and see the purple text saying something like "gfx [...] Vendor:", it should mention nvidia)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Under Windows you can usually select the preferred graphics card under Windows' graphics options, or directly in the control panel of your graphics driver (e.g. nvidia control panel)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Network / Connection problems ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
DDNet and Teeworlds network code requires a stable connection with as less ping jitter as possible.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you experience problems make sure to:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
# Use a LAN cable instead of Wifi
# Turn off other applications on your computer and other computers in your network to tell if they are the source of the problem
# Prefer DSL/Fiber over cable internet
# Make sure it is not a DoS/DDoS attack on the server (did it ever work before, do other servers work fine?)
# Try <code>ping -t ger2.ddnet.org</code> in cmd.exe for a few minutes, stop it with ctrl-c, and check the if the ping jumps there too or you have packet loss
# Try to trace route the connection to the DDNet server (using <code>tracert ger2.ddnet.org</code> in cmd.exe) and see if there is bad routing (ask your ISP to fix it)
</div>