Troubleshooting/es

El objetivo de este artículo es ayudarte con los problemas que experimentes en DDNet.

La información útil para que los desarrolladores depuren problemas son:

1. Registros de inicio/crash.
2. Información de Hardware (GPU, CPU, RAM, sistema operativo (Windows, Linux, etc.)) - Puedes ver qué GPU está usando tu cliente al presionar F1 cuando lo inicias. Debería haber un texto púrpura.
3. Pasos para reproducir el problema.

Crasheos

Los crasheos son cierres inesperados, los cuales son generalmente causados por un error en el código de DDNet, o en cualquier otro software.

La regla general es: si puedes reproducir el crasheo, debes contactar a los desarolladores.

Consulta links externos o crea un problema en GitHub.

Desde DDNet 16 para Windows, el cliente puede crear un registro de crash o un registro de aserción, el cual puedes encontrar en el directorio de configuración, dentro de "dumps". Envíaselos a los desarrolladores para que puedan encontrar información útil en cualquiera de los registros.

Si el cliente crashea al iniciarse, probablemente sea porque los controladores de tu tarjeta gráfica están rotos o desactualizados (revisa Solución de problemas gráficos), o por algún antivirus que está interviniendo (busca en internet cómo desactivar el antivirus para una aplicación específica).

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.

Problemas gráficos

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.

You can still try the following thing:

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).

Inside the client go on Settings -> Graphics
Under "Renderer" select OpenGL 1
Restart

If you prefer to have a more appropriate solution for your problem, visit the GFX Troubleshooting page, which analysis graphics problems more specifically and gives extra details.

ALT + TAB problems

This is most likely a graphics driver problem. However you can still try to fix it by using "Windowed Fullscreen".

This is a special fullscreen mode, that makes the window act like it is fullscreen, even if it's not.

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.

Inside the client go on Settings -> Graphics
Click on "Fullscreen" (or whatever you last selected) and choose "Windowed Fullscreen" instead

(if you experience bugs changing this mode, just restart the game once and make sure "Windowed Fullscreen" is still selected)

Broken streaming

When you experience a bug with streaming DDNet over discord, you are most likely using a nvidia graphics card.

A user already reached out to discord, and they told him to:

Toggle off the "Use our latest technology to capture my screen" setting under User Settings > Voice & Video

If you have problems finding DDNet in nvidia shadow play.

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)

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)

Problemas de red / conexión

El código de red de DDNet y Teeworlds requiere una conexión estable con la menor fluctuación de ping/jitter posible.

Si experimenta problemas, asegúrese de:

1. Use a LAN cable instead of Wifi
2. Turn off other applications on your computer and other computers in your network to tell if they are the source of the problem
3. Prefer DSL/Fiber over cable internet
4. Make sure it is not a DoS/DDoS attack on the server (did it ever work before, do other servers work fine?)
5. Try ping -t ger2.ddnet.org 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
6. Try to trace route the connection to the DDNet server (using tracert ger2.ddnet.org in cmd.exe) and see if there is bad routing (ask your ISP to fix it)