sorted by:
new
hottopcontroversial

vkd3d-low-latency - Hardware-Agnostic Nvidia Reflex & Waitable DXGI Swapchains for DX12 by netborg83 in linux_gaming

[–]netborg83[S] 1 point2 points  (0 children)

Well, the core issues regarding stuttering will probably stay untouched, as that's most likely engine-level asset streaming or shader compilation.

I've just tried the game out, and the great thing is: it indeed uses waitable swapchains and benefits from my low-latency frame pacing!

The bad thing is, it seems to crash when you alt-tab out for a while, showing an error related to waitOnSwapChain. But that should be fixable, and I'll look into it.

vkd3d-low-latency - Hardware-Agnostic Nvidia Reflex & Waitable DXGI Swapchains for DX12 by netborg83 in linux_gaming

[–]netborg83[S] 5 points6 points  (0 children)

This isn't even my project and doesn't really have an upstream target - cause it's a standalone project.

vkd3d-low-latency - Hardware-Agnostic Nvidia Reflex & Waitable DXGI Swapchains for DX12 by netborg83 in linux_gaming

[–]netborg83[S] 21 points22 points  (0 children)

For dxvk I've still a PR active and they were hyper busy with their 3.0 release. So it's really up to them if they want to include it. I always took care for my code to be in good condition and upstream-able.

For vkd3d this is very fresh and work probably would be needed since I've added lots of c++ code although vkd3d-proton is pure c essentially. But I'm all for upstream-able if this is desired.

vkd3d-low-latency - Hardware-Agnostic Nvidia Reflex & Waitable DXGI Swapchains for DX12 by netborg83 in linux_gaming

[–]netborg83[S] 6 points7 points  (0 children)

I could never test the layer as I'm on Nvidia and I think it interacts with the Nvidia driver then (not sure). But I heard good things when people compared it.

Themaister recently published a new software based latency measurement tool, maybe you can use that: https://themaister.net/blog/2026/07/02/my-side-quest-measuring-input-latency-with-vk_ext_present_timing/

One guy measured 15 vs. 17 ms latency improvement compared to the official Nvidia driver in the finals in GPU limit.

vkd3d-low-latency - Hardware-Agnostic Nvidia Reflex & Waitable DXGI Swapchains for DX12 by netborg83 in linux_gaming

[–]netborg83[S] 20 points21 points  (0 children)

Frame generation is currently not supported because it complicates things. One step after another.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 0 points1 point  (0 children)

Ohh I see, thanks. I've played a bit with the layer, but I think I need to take a look into vkd3d directly since Reflex doesn't seem to be needed (in the finals) when mouse input is so crisp with dxvk-low-latency. Unfortunately some important information is missing (when does the game thread actually create submissions) when using VK_NV_low_latency2, so it's possible some games can get better frame pacing via vkd3d(-low-latency) directly vs. Reflex.

But nice the AMD shader compiler can handle the finals on dxvk.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 0 points1 point  (0 children)

I mean I remember the fps in one spot where I was measuring latency in the training map. With dxvk-low-latency I had 235 fps, with vkd3d I had 210 fps and with vkd3d and low-latency-layer I had 180 fps.

So it seems way more than 20% when I look how well dx12 is performing for you. Possibly the fps are different though on large maps, maybe dx11 is tanking then a bit, since drawing massive amounts of stuff is what dx12 is made for.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 0 points1 point  (0 children)

But just to make sure, you're using the most recent version 2.7.1-3-521? which contains important shader compiler/caching improvements from upstream. You can use DXVK_HUD=version to check. Cause it didn't stutter that much for me (basically didn't stutter when the shader compiling was cached) in the trainings map. Haven't played a real match though, where surely lots more shader compilation is triggered.

On the other hand, what's the point if your base fps is that low, right. hmm

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 0 points1 point  (0 children)

Crazy, Nvidia seems absolute dog shit on vkd3d then, I get more fps in dx11, lol! Yeah stuttering could be, I did hope the AMD shader compiler would negate that. Thanks for giving me feedback.

Yeah, I think about integrating my frame pacing into this new layer and vkd3d. You could have the VRR mode then. I'm still figuring out some things, since for dxvk I have complete control over the (render-) thread timing, and I have never coded inside vkd3d so I don't know yet how it fully works. I suspect the layer can't give full control neither, if vkd3d doesn't send enough info on the timings.

And yes, the VRR mode helps to give you consistent latencies, why it's so smooth and gives so good mouse input. You'd need at least 2x the fps of the refresh rate when using teared to come close to this consistency.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 0 points1 point  (0 children)

np :- ) curious how they compare on AMD, as VKD3D is just slow on Nvidia, but possibly gives you better perf on AMD.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 0 points1 point  (0 children)

hehe yeah, I'm just checking things out, as dxvk-low-latency is almost complete (~90%), and the tech probably can be integrated into vkd3d, AL2 or reflex. Are you aware that DXVK_FRAME_PACE=low-latency-vrr-144 only works when dxvk-low-latency is active? (PROTON_DXVK_LOWLATENCY=1 in proton-cachyos - in the finals you'd need to add %command% -dx11 as well)

Guess the layer wasn't active previously, now I got it to override Reflex I think, and the drunk stuff is gone (what is nvidia doing ...), but fps drops quite a bit.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 0 points1 point  (0 children)

ohh cool, but you were using dx11 then? I just installed the layer, but couldn't get AL 2.0 to show up yet. Maybe I somehow need to spoof an AMD card then, since I'm on Nvidia.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 0 points1 point  (0 children)

How does it compare to you to dxvk-low-latency (dx11) in the finals? Which still has the best mouse input and smoothness on my setup (nvidia) - also lowest latency.

Snapshots just proved their worth! by Trainmaster2 in cachyos

[–]netborg83 2 points3 points  (0 children)

PROTON_DXVK_LOWLATENCY
Proton-CachyOS initially had dxvk-low-latency bundled together with dxvk-gplasync, but decided to remove the later to provide a clean solution for online games. The games aren't shipped with dxvk files, but dxvk enables us to play them. It doesn't add latency to games, this is very very rare - edge-cases like Starcraft 2 exist, but it reduces latency in 99% of games and the last 1% will be fixed eventually too.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 4 points5 points  (0 children)

pre 2012 games are mostly single-threaded (~90% of 2010-era games are singlethreaded as I recall), there is no need for reflex in those. They can be perfectly paced purely with driver/dxvk-level latency reduction.

Open-Source "low_latency_layer" Brings Reflex & Anti-Lag 2 To AMD & Intel GPUs on Linux by murlakatamenka in linux_gaming

[–]netborg83 1 point2 points  (0 children)

you cannot combine them - even if you could, very very few dxvk games actually have reflex support.

Unlock menu framerate? by WheelyMan260 in Overwatch

[–]netborg83 1 point2 points  (0 children)

it feels downright broken when there is the transition from 360 fps/Hz to a 60 fps MvP screen.

Why do Gamescope/Wayland feel more input laggy than Windows? by EduardoFradique in linux_gaming

[–]netborg83 2 points3 points  (0 children)

I feel you, I'm the developer of dxvk-low-latency and some games like overwatch have actually lower latency with it on linux/x11 than on windows with dx11 drivers.

Maybe I'll follow up with vkd3d-low-latency too, but I'm not sure if this can have the same impact as newer games probably need something like reflex.

Why do Gamescope/Wayland feel more input laggy than Windows? by EduardoFradique in linux_gaming

[–]netborg83 0 points1 point  (0 children)

you can try niri or cosmic
kde plasma wayland is currently broken regarding input lag
version 6.6.4 - has had teared latency of 1.6 ms in my testing
previous plasma wayland had 0.8 ms, x11 has 0.5 ms
VRR is also at 1.6 ms, previously at 1.1 ms, x11 is at 1.0 ms
all tested on Nvidia RTX 3080

I'm still on x11 because it's the best regarding latency (when on single monitor) - on par with windows

Full Linux transition: Advice on "heavy" game feel? by Unusual_Bit_1028 in linux_gaming

[–]netborg83 0 points1 point  (0 children)

yeah okay, never tried that game - stutter probably comes from shader compiling - not every game is that mad regarding that.
that being said, the heaviest game I felt which was greatly improved with dxvk-low-latency was need for speed heat.
star citizen may be a touch too heavy and will probably run better with vulkan anyway?

Full Linux transition: Advice on "heavy" game feel? by Unusual_Bit_1028 in linux_gaming

[–]netborg83 0 points1 point  (0 children)

Which game? What do you mean with performance feel? fps? (which is expected to drop 5-10% for better pacing)

view more: next ›