How To Play on Linux: Difference between revisions
add troubleshooting tip for patcher-rendering issues on wayland |
mNo edit summary |
||
| Line 126: | Line 126: | ||
* Above example had success using KDE Plasma and niri (niri requires the <code>xwayland-satellite</code>-package though), <strong>but</strong> the patcher only ran successfully using <code>GDK_BACKEND=x11 ./Muh_Patcher</code> | * Above example had success using KDE Plasma and niri (niri requires the <code>xwayland-satellite</code>-package though), <strong>but</strong> the patcher only ran successfully using <code>GDK_BACKEND=x11 ./Muh_Patcher</code> | ||
* Adjusting environment-variables in nix-config may require a reboot (or at least logging out and back in again) before they fully apply | |||
* Switching from <code>wine</code> to <code>wineWow64Packages.stable</code> required me to wipe my wineprefix before it took effect | * Switching from <code>wine</code> to <code>wineWow64Packages.stable</code> required me to wipe my wineprefix before it took effect | ||
* DXVK option in the patcher addons doesn't seem to work for me on nix, but running <code>winetricks dxvk</code> <em>did</em> work, and brings dramatic(!) performance improvements. You can double-check whether or not dxvk works by running the Patcher with <code>DXVK_HUD=full ./Muh_Patcher</code> | * DXVK option in the patcher addons doesn't seem to work for me on nix, but running <code>winetricks dxvk</code> <em>did</em> work, and brings dramatic(!) performance improvements. You can double-check whether or not dxvk works by running the Patcher with <code>DXVK_HUD=full ./Muh_Patcher</code> | ||