GFX Troubleshooting: Difference between revisions
Prepared the page for translation |
Marked this version for translation |
||
| Line 1: | Line 1: | ||
<languages/> | <languages/> | ||
<translate> | <translate> | ||
<!--T:1--> | |||
There are numerous graphics (gfx) related bugs users encountered. Not all are fixable, but might have workarounds. | There are numerous graphics (gfx) related bugs users encountered. Not all are fixable, but might have workarounds. | ||
This site is there to collect these to help those encountering the same issues. | This site is there to collect these to help those encountering the same issues. | ||
== Game not starting == | == Game not starting == <!--T:2--> | ||
<!--T:3--> | |||
Generally there are two different types of users encountering these problems. Users with old computers (2015 and older) and users with new computers. | Generally there are two different types of users encountering these problems. Users with old computers (2015 and older) and users with new computers. | ||
| Line 13: | Line 15: | ||
<span id="for-users with older computers"></span> | <span id="for-users with older computers"></span> | ||
<translate> | <translate> | ||
=== For users with older computers === | === For users with older computers === <!--T:4--> | ||
<!--T:5--> | |||
Usually it’s enough to force OpenGL 1.x and the game should start. | Usually it’s enough to force OpenGL 1.x and the game should start. | ||
Do this by editing settings_ddnet.cfg that is located inside the config directory [[Special:MyLanguage/FAQ#Where_is_the_DDNet_config,_config_directory_or_save_directory?|FAQ#Where_is_the_DDNet_config,_config_directory_or_save_directory?]] | Do this by editing settings_ddnet.cfg that is located inside the config directory [[Special:MyLanguage/FAQ#Where_is_the_DDNet_config,_config_directory_or_save_directory?|FAQ#Where_is_the_DDNet_config,_config_directory_or_save_directory?]] | ||
| Line 20: | Line 23: | ||
To the bottom of this file add: | To the bottom of this file add: | ||
gfx_gl_major 1 | <!--T:6--> | ||
gfx_gl_major 1 | |||
gfx_backend opengl | gfx_backend opengl | ||
If you are a steam user, you can also pass it as steam start parameter by writing “gfx_gl_major 1; gfx_backend opengl” (INCLUDING the “) (rightclick ddnet in steam, properties -> start arguments. | If you are a steam user, you can also pass it as steam start parameter by writing “gfx_gl_major 1; gfx_backend opengl” (INCLUDING the “) (rightclick ddnet in steam, properties -> start arguments. | ||
<!--T:7--> | |||
If all this still does not help, you can still fallback to software rendering. Software rendering means it runs all graphics calls on your CPU instead of your GPU. This results in far less FPS, but might still be playable with some tweaks. Grab the latest 64-bit version of ddnet from https://ddnet.org/downloads. Now download and install 7-Zip. Download the latest mesa for windows from https://github.com/pal1000/mesa-dist-win/releases | If all this still does not help, you can still fallback to software rendering. Software rendering means it runs all graphics calls on your CPU instead of your GPU. This results in far less FPS, but might still be playable with some tweaks. Grab the latest 64-bit version of ddnet from https://ddnet.org/downloads. Now download and install 7-Zip. Download the latest mesa for windows from https://github.com/pal1000/mesa-dist-win/releases | ||
which should be named like this: mesa3d-xx.y.z-release-mingw.7z. | which should be named like this: mesa3d-xx.y.z-release-mingw.7z. | ||
Unpack the DDNet client somewhere, unpack mesa. From mesa move all .dll files from the x64 directory inside the DDNet client’s directory. So all .dll files are next to DDNet.exe. If you did everything right it should start the client again, if not try to add | Unpack the DDNet client somewhere, unpack mesa. From mesa move all .dll files from the x64 directory inside the DDNet client’s directory. So all .dll files are next to DDNet.exe. If you did everything right it should start the client again, if not try to add | ||
gfx_backend Vulkan | <!--T:8--> | ||
gfx_backend Vulkan | |||
<!--T:9--> | |||
to the settings_ddnet.cfg as described above | to the settings_ddnet.cfg as described above | ||
=== For users with new computers === | === For users with new computers === <!--T:10--> | ||
<!--T:11--> | |||
Usually this is caused by bad drivers. You should check the manufacturers website for the newest drivers | Usually this is caused by bad drivers. You should check the manufacturers website for the newest drivers | ||
([https://www.amd.com/en/support AMD], [https://www.nvidia.com/download/index.aspx?lang=en-us NVIDIA], [https://www.intel.com/content/www/us/en/download-center/home.html Intel]). For Intel also note this article: [https://www.intel.com/content/www/us/en/support/articles/000058958/graphics.html Warning: Installing This Graphics Driver From Intel May Overwrite Customizations From Your Computer Manufacturer (OEM)]. | ([https://www.amd.com/en/support AMD], [https://www.nvidia.com/download/index.aspx?lang=en-us NVIDIA], [https://www.intel.com/content/www/us/en/download-center/home.html Intel]). For Intel also note this article: [https://www.intel.com/content/www/us/en/support/articles/000058958/graphics.html Warning: Installing This Graphics Driver From Intel May Overwrite Customizations From Your Computer Manufacturer (OEM)]. | ||
| Line 42: | Line 50: | ||
To the bottom of this file add: | To the bottom of this file add: | ||
<!--T:12--> | |||
<pre>gfx_backend Vulkan</pre> | <pre>gfx_backend Vulkan</pre> | ||
If you are a steam user, you can also pass it as steam start parameter by writing “gfx_backend Vulkan” (INCLUDING the “) (rightclick ddnet in steam, properties -> start arguments | If you are a steam user, you can also pass it as steam start parameter by writing “gfx_backend Vulkan” (INCLUDING the “) (rightclick ddnet in steam, properties -> start arguments | ||
| Line 49: | Line 58: | ||
<span id="some-text is invisible with the vulkan backend"></span> | <span id="some-text is invisible with the vulkan backend"></span> | ||
<translate> | <translate> | ||
== Some text is invisible with the Vulkan backend == | == Some text is invisible with the Vulkan backend == <!--T:13--> | ||
<!--T:14--> | |||
[[File:Vulkangraphicsbug.jpg|thumb|Vulkan graphics bug with missing text|center]] | [[File:Vulkangraphicsbug.jpg|thumb|Vulkan graphics bug with missing text|center]] | ||
<!--T:15--> | |||
Users with an AMD card reported this and it’s caused by AMD driver from 2021. Just visit and download a driver from march 2022 or newer from https://www.amd.com/en/support. | Users with an AMD card reported this and it’s caused by AMD driver from 2021. Just visit and download a driver from march 2022 or newer from https://www.amd.com/en/support. | ||
If there is no driver from 2022 you should switch back to OpenGL, you sadly cannot use Vulkan then, inside the client just paste | If there is no driver from 2022 you should switch back to OpenGL, you sadly cannot use Vulkan then, inside the client just paste | ||
| Line 58: | Line 69: | ||
== Some text looks broken == | == Some text looks broken == <!--T:16--> | ||
<!--T:17--> | |||
[[File:Razer-Cortex-Overlay.png|thumb|Razer Cortex-Overlay makes text unreadable|center]] | [[File:Razer-Cortex-Overlay.png|thumb|Razer Cortex-Overlay makes text unreadable|center]] | ||
<!--T:18--> | |||
Some users reported broken text, e.g. text that is unreadable as if the text was streetched. | Some users reported broken text, e.g. text that is unreadable as if the text was streetched. | ||
This is caused by external overlays. Most people with this problem reported they used the "Razer Cortex" overlay. Disabling/uninstalling fixed the problem. | This is caused by external overlays. Most people with this problem reported they used the "Razer Cortex" overlay. Disabling/uninstalling fixed the problem. | ||
== The client randomly crashes with an Intel GPU == | == The client randomly crashes with an Intel GPU == <!--T:19--> | ||
<!--T:20--> | |||
Usually DDNet has a strong fallback system for Intel GPUs on Windows as they often caused bugs with OpenGL 2.1+ | Usually DDNet has a strong fallback system for Intel GPUs on Windows as they often caused bugs with OpenGL 2.1+ | ||
If you have a recent Intel GPU you can simply switch to Vulkan in the graphic settings inside the client. | If you have a recent Intel GPU you can simply switch to Vulkan in the graphic settings inside the client. | ||
| Line 73: | Line 87: | ||
== Absolutely nothing helps == | == Absolutely nothing helps == <!--T:21--> | ||
<!--T:22--> | |||
If you are sure you did everything correct and nothing helped report this bug on ddnet’s discord #bugs channel. You are the first encountering this situation. The only known modern GPU that caused problems is an AMD ryzen 3 2200g, if you don’t use the AMD beta drivers (confirmed with Adrenalin 22.5.1 Recommended (WHQL)) | If you are sure you did everything correct and nothing helped report this bug on ddnet’s discord #bugs channel. You are the first encountering this situation. The only known modern GPU that caused problems is an AMD ryzen 3 2200g, if you don’t use the AMD beta drivers (confirmed with Adrenalin 22.5.1 Recommended (WHQL)) | ||
You can simply switch to OpenGL backend, see [[Special:MyLanguage/#some-text is invisible with the vulkan backend|#Some text is invisible with the Vulkan backend]]. Else you have to accept to use an OpenGL 1.x backend as described in [[Special:MyLanguage/#for-users with older computers|#For users with older computers]]. | You can simply switch to OpenGL backend, see [[Special:MyLanguage/#some-text is invisible with the vulkan backend|#Some text is invisible with the Vulkan backend]]. Else you have to accept to use an OpenGL 1.x backend as described in [[Special:MyLanguage/#for-users with older computers|#For users with older computers]]. | ||
| Line 80: | Line 95: | ||
== Some ingame tiles are invisible or look broken == | == Some ingame tiles are invisible or look broken == <!--T:23--> | ||
<!--T:24--> | |||
You are probably an user with an old GPU, just see [[Special:MyLanguage/#for-users with older computers|#For users with older computers]] for the solution. | You are probably an user with an old GPU, just see [[Special:MyLanguage/#for-users with older computers|#For users with older computers]] for the solution. | ||
</translate> | </translate> | ||
Revision as of 19:05, 11 February 2023
There are numerous graphics (gfx) related bugs users encountered. Not all are fixable, but might have workarounds. This site is there to collect these to help those encountering the same issues.
Game not starting
Generally there are two different types of users encountering these problems. Users with old computers (2015 and older) and users with new computers.
For users with older computers
Usually it’s enough to force OpenGL 1.x and the game should start. Do this by editing settings_ddnet.cfg that is located inside the config directory FAQ#Where_is_the_DDNet_config,_config_directory_or_save_directory? Make sure no DDNet Client is running (best is you even check in the taskmanager) To the bottom of this file add:
gfx_gl_major 1 gfx_backend opengl
If you are a steam user, you can also pass it as steam start parameter by writing “gfx_gl_major 1; gfx_backend opengl” (INCLUDING the “) (rightclick ddnet in steam, properties -> start arguments.
If all this still does not help, you can still fallback to software rendering. Software rendering means it runs all graphics calls on your CPU instead of your GPU. This results in far less FPS, but might still be playable with some tweaks. Grab the latest 64-bit version of ddnet from https://ddnet.org/downloads. Now download and install 7-Zip. Download the latest mesa for windows from https://github.com/pal1000/mesa-dist-win/releases which should be named like this: mesa3d-xx.y.z-release-mingw.7z. Unpack the DDNet client somewhere, unpack mesa. From mesa move all .dll files from the x64 directory inside the DDNet client’s directory. So all .dll files are next to DDNet.exe. If you did everything right it should start the client again, if not try to add
gfx_backend Vulkan
to the settings_ddnet.cfg as described above
For users with new computers
Usually this is caused by bad drivers. You should check the manufacturers website for the newest drivers (AMD, NVIDIA, Intel). For Intel also note this article: Warning: Installing This Graphics Driver From Intel May Overwrite Customizations From Your Computer Manufacturer (OEM). If it’s still crashing you should try to use vulkan Do this by editing settings_ddnet.cfg that is located inside the config directory (FAQ#Where_is_the_DDNet_config,_config_directory_or_save_directory? Make sure no DDNet Client is running (best is you even check in the taskmanager) To the bottom of this file add:
gfx_backend Vulkan
If you are a steam user, you can also pass it as steam start parameter by writing “gfx_backend Vulkan” (INCLUDING the “) (rightclick ddnet in steam, properties -> start arguments
Some text is invisible with the Vulkan backend
Users with an AMD card reported this and it’s caused by AMD driver from 2021. Just visit and download a driver from march 2022 or newer from https://www.amd.com/en/support.
If there is no driver from 2022 you should switch back to OpenGL, you sadly cannot use Vulkan then, inside the client just paste
gfx_gl_major 3;gfx_gl_minor 3; gfx_backend opengl in the F1 console and restart the client.
Some text looks broken
Some users reported broken text, e.g. text that is unreadable as if the text was streetched. This is caused by external overlays. Most people with this problem reported they used the "Razer Cortex" overlay. Disabling/uninstalling fixed the problem.
The client randomly crashes with an Intel GPU
Usually DDNet has a strong fallback system for Intel GPUs on Windows as they often caused bugs with OpenGL 2.1+
If you have a recent Intel GPU you can simply switch to Vulkan in the graphic settings inside the client.
Else type gfx_gl_major 2;gfx_gl_minor 0; gfx_backend opengl in the F1 console of the client and restart.
Absolutely nothing helps
If you are sure you did everything correct and nothing helped report this bug on ddnet’s discord #bugs channel. You are the first encountering this situation. The only known modern GPU that caused problems is an AMD ryzen 3 2200g, if you don’t use the AMD beta drivers (confirmed with Adrenalin 22.5.1 Recommended (WHQL)) You can simply switch to OpenGL backend, see #Some text is invisible with the Vulkan backend. Else you have to accept to use an OpenGL 1.x backend as described in #For users with older computers. It’s also quite possible that the problem is not GFX related. Try to disable your Anti-Virus for DDNet, make sure you use a recent Windows/Linux/macOS version. Always try 64-bit versions first as they are more tested.
Some ingame tiles are invisible or look broken
You are probably an user with an old GPU, just see #For users with older computers for the solution.