-
-
Notifications
You must be signed in to change notification settings - Fork 133
Quirks
This is a list of quirks we've found in various games. If you're 100% sure you have installed lsfg-vk correctly (verify through logs), try the following list.
This is the first line of defense. You need to enable VSync in the game settings and ideally set an FPS cap at the render framerate (if you're doing 2x to get to 240, set it to 120). Note that you can set a rendercap for D3D8-12 games with DXVK_FRAME_RATE.
I do mean literal windowed mode. The game should not take up your entire screen. There seem to be issues with synchronization on some titles when the game is in fullscreen mode.
This one only applies if you're on Wayland. The new tearing protocol can cause issues with some games. Disable it and see if it helps.
This one also only applies if you're on Wayland. Some compositors have a feature that allows you to pass through the game directly to the GPU, bypassing the compositor in case of fullscreen. This has also caused issues in some games, so try disabling it.
lsfg-vk can cause trouble with Variable Refresh Rate (VRR) on some monitors. If you're encountering stuttering and similar issues, try disabling VRR in your monitor settings or through your compositor.
If you're using mangohud, it too can disable vsync and break the game. Remove it or set vsync=3 in its configuration.
This project only works for Vulkan games, so you have to rely on Zink to translate OpenGL to Vulkan. You can do this by setting these environment variables:
__GLX_VENDOR_LIBRARY_NAME=mesa MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink
If your game now freezes or breaks in other ways, there's unfortunately not much we can do about it.
lsfg-vk does not load on 32-bit games, but some people have found that switching to an extremely new version of Proton (such as Proton Experimental Bleeding Edge) and setting the environment variable PROTON_USE_WOW64=1 can make some games work. If this doesn't work, you may try the Gamescope override described in the Gamescope wiki page, but it is not recommended at all.
This is intended(-ish?) behavior, there's nothing we can do about it.
Getting started:
Troubleshooting & More:
How lsfg-vk works: