Vulkan layer brings Reflex to Linux

Korthos-Software has published an open-source project called `low_latency_layer` that tries to solve a long-running Linux gaming problem: many games expose Nvidia Reflex, far fewer expose AMD Anti-Lag, and both features are usually tied to vendor-specific driver support. The project does that by adding an implicit Vulkan layer that implements the `VK_NV_low_latency2` and `VK_AMD_anti_lag` device extensions in a hardware-agnostic way. That means AMD and Intel GPUs on Linux can present low-latency features that games normally reserve for Nvidia or AMD-specific paths. ### Why is a Vulkan layer the key piece here? The GitHub README says the layer sits between the game and the driver, exposing the low-latency Vulkan extensions without waiting for official vendor enablement. When paired with `dxvk-nvapi`, it can forward the relevant calls for Proton titles as well, extending the approach beyond native Linux Vulkan games. VideoCardz reported that this matters because Reflex support is already common in PC games, while Anti-Lag 2 support is much less widespread. (github.com) By exposing the Nvidia path on non-Nvidia hardware, the layer gives Linux users access to the option developers have already integrated most often. ### What does it actually change for AMD and Intel users? (github.com) The README says the default behavior is to expose `VK_AMD_anti_lag`, which lets native Linux applications such as Counter-Strike 2 toggle AMD Anti-Lag from their menus. It also includes an environment variable, `LOW_LATENCY_EXPOSE_REFLEX=1`, to expose `VK_NV_low_latency2` instead, and another option to spoof an Nvidia GPU because some games otherwise will not show Reflex in settings. (videocardz.com) GamingOnLinux said the first public release is intended for both native Linux titles and Windows games run through Proton. That gives the project a broader target than a single engine or a single vendor stack. ### Are there benchmark claims behind the release? The project README says its benchmarks suggest the layer performs “as well as or better than” proprietary Windows implementations on equivalent hardware. (github.com) GamingOnLinux, citing the developer’s published tests, said results in some games matched or exceeded native Windows paths and that the Reflex and Anti-Lag implementations appeared to perform identically in those tests. (gamingonlinux.com) VideoCardz said the published test set includes The Finals, Counter-Strike 2, Cyberpunk 2077, Resident Evil Requiem, Marvel Rivals and Overwatch 2. Those results, as reported, point to the project’s main pitch: lower click-to-photon latency on Linux without requiring Nvidia hardware or official vendor driver support. (github.com) ### How does this compare with earlier Linux latency work? GamingOnLinux said the developer also compared the new layer with Mesa’s Anti-Lag Vulkan layer and found Mesa’s implementation appeared to provide no latency benefit in at least some tests. That is the comparison most likely to matter for Linux users who assumed the open graphics stack already covered this ground. (videocardz.com) The release also fits a broader Linux pattern: community layers often recreate features that vendors first ship as hardware- or driver-specific advantages. In this case, the abstraction is the story. A game only needs to see the expected Vulkan extension; the underlying GPU vendor matters less if the layer can deliver the same pacing behavior. That is an inference from how the project is designed and from the published extension-based approach. (gamingonlinux.com) ### What are the limits right now? The GitHub page says installation is still manual: users need Vulkan headers, Vulkan utility libraries and CMake to build from source, then must configure environment variables depending on whether they want Anti-Lag or Reflex exposure. Proton users also need `dxvk-nvapi` enabled. The first release is already live on GitHub, and GamingOnLinux reported it as an initial public release on May 18. (github.com) That means the next concrete step is testing across more games, more distros and more driver combinations as users begin trying the layer in native Vulkan titles and Proton setups. (gamingonlinux.com)