Which low-latency settings should I use for Linux games?

November 21, 2026 5 answers
Asked by lootSocketAudit

There seem to be a lot of launch flags and in-game settings for reducing latency. What should I use for NVIDIA or AMD, and does it depend on whether the game uses DirectX or Vulkan?

Answers

deckGraveyardTourist

Start with the game's own setting rather than a pile of launch flags. On NVIDIA, if a DirectX game offers Reflex, try enabling it in the menu. The supplied guidance says this can work through Proton and the proprietary NVIDIA driver without an extra launch command.

Support still depends on the game, driver, and Proton version, so check that the option is actually available and working rather than assuming every game behaves the same way.

Reply to this answer
P12burstRoute~Casually

For games without Reflex, the API matters. A custom Proton build such as Proton-CachyOS may offer PROTON_DXVK_LOWLATENCY=1 for older DirectX games using DXVK. For DirectX 12, PROTON_VKD3D_LOWLATENCY=1 is described as an option for games using waitable DXGI swapchains.

Those are not general-purpose flags for every Proton version or every game. Check the documentation for the build you use, and don't assume the DirectX 12 option will help a game that doesn't use that kind of swapchain.

Reply to this answer
raidHealerOnCoffee

AMD has a different route. LOW_LATENCY_LAYER=1 can enable a Vulkan layer for games that support AMD Anti-Lag 2. It needs the relevant layer and support in the game and driver, so the flag alone isn't a universal latency switch.

Reply to this answer
P10throwLoop+Celery

There is also a more experimental AMD option for DirectX 12 games with Reflex. The described setup uses LOW_LATENCY_LAYER=1 and LOW_LATENCY_LAYER_REFLEX=1, plus DXVK_CONFIG="dxgi.hideAmdGpu=True" to make the Reflex menu appear.

That GPU hiding can break native FSR 4, so there's a real tradeoff. I'd treat it as something to test per game, not a default to add everywhere. A custom Proton build's VKD3D low-latency option is another possible route for compatible waitable swapchains, but it works differently from Reflex.

Reply to this answer
mechTorqueReceipt

Keep a note of what you changed and test one option at a time. Low-latency settings target queued frames, but a flag being accepted doesn't prove it helped. Comparing the same game settings before and after is more useful than stacking several tweaks and guessing.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions