Linux users who run competitive shooters through Proton have spent years wondering why their crosshair feels half a frame behind their Windows-using friends on the same hardware. The lag was real, and most of them quietly stopped trusting their aim on Linux without being able to name the cause. NVIDIA’s 615.71 New Feature Branch driver fixes this for real, and it does not get the headlines it deserves.
The headline item in 615.71 is that Reflex low latency now engages properly under Proton for Vulkan titles, and the Wayland-specific path that had been broken is fixed at the same time. Reflex is NVIDIA’s low-latency feature that synchronizes the CPU, the GPU, and your display refresh so the shot fires when you click. On Windows it has worked for years. On Linux, the Proton path had a hole in it that nobody at NVIDIA seemed to own in public. The 615.71 release quietly closes that hole.
What actually changed in 615.71
Four fixes are worth your time, grouped by what kind of user cares.
- Proton Reflex now engages without workarounds. Vulkan titles running through Steam’s Proton layer can use NVIDIA’s low-latency stack out of the box. Vulkan (a low-overhead graphics API designed as a successor to OpenGL) is the API that Proton translates DirectX calls into for most modern games. Before this release, Reflex support under Vulkan on Proton was a coin flip that depended on the title, the Proton version, and the phase of the moon.
- Wayland Reflex latency is fixed. NVIDIA’s relationship with Wayland has historically been bumpy, and Reflex-style input lag was one of the symptoms. After 615.71, the input-latency story on a Wayland session matches what Windows users have had for years.
- Xid 109 errors on PRAGMATA are gone. Xid errors are NVIDIA’s internal GPU fault codes, and Xid 109 specifically means an interrupt timed out. If you have never seen an Xid error in your terminal, count yourself lucky. If you have, you know the kernel log noise alone is enough to ruin a session.
- Blackwell display corruption and a hibernation bug are fixed. Output scaling (which lets you render at a lower resolution and upscale to your monitor’s native resolution) was triggering visual glitches on RTX 5000-series cards. That is patched, along with a rare compute crash on Blackwell silicon and a suspend bug that could prevent waking from hibernation.
If only one of those bullets applies to you, that bullet is reason enough to install. The Proton Reflex fix is the headline. The Blackwell fixes are the quiet win for non-gamers.
The Smooth Motion hang
NVIDIA Smooth Motion is a driver-level frame generation feature that inserts extra frames to smooth out your frame rate. It is the non-AI cousin of DLSS Frame Generation. The catch was a hard hang that happened sometimes at game launch and sometimes when you Alt+Tabbed out and back in. That turned the feature into a trap for any user who toggled it on and hoped for the best. The fix in 615.71 makes Smooth Motion stable enough to leave on, which is the only setting that makes sense for a feature like this. Nobody toggles frame generation per match.
If you do not play on a Reflex-enabled title and you do not care about Smooth Motion, the Blackwell fixes alone are probably reason enough to install. The 4070 generation is fine without this driver. The 5000-series Blackwell owners have been waiting for this release specifically.
The idle power option: read the warning
One new feature in 615.71 lets you reduce idle power draw on multi-monitor setups. NVIDIA is upfront about the cost. Enabling it can cause brief display glitches during transitions, the kind of flicker you see when a window drags across a monitor edge or when your second display wakes up from sleep. For a workstation running overnight with cron jobs and unattended renders, this is a non-starter. For any desktop where the operator sits in front of the screen, a 200-millisecond flicker once an hour is still a regression. The people who would benefit are the ones who already know they are the target audience: multi-monitor rigs where every watt at idle matters and a brief flicker is acceptable.
This is not a reason to install the driver. It is a reason to know the option exists.
Branch choice and the upgrade cost
615.71 sits on the New Feature Branch, not the Long Lived Branch. NFB is the release track that ships fixes and features faster, with the trade-off that regressions are more likely. LLB is the conservative track NVIDIA maintains for users who want every release to be a known quantity. If you run a workstation that needs to stay up, or a render box that clients depend on, wait for these fixes to land in the next LLB. If you run a Linux gaming desktop and want the Reflex fix this week, the NFB is the right call. The source notes that the NFB is geared toward users who want the latest fixes and features faster than the long-term branch provides, and the long-term branch remains the right track for stability-first operators.
The install is the standard NVIDIA installer flow. Run the .run file from a TTY (a virtual console you reach with Ctrl+Alt+F2, outside of any graphical session), let it rebuild the initramfs (the initial RAM filesystem the kernel mounts before the real root filesystem is available), reboot. Total downtime on a typical install is a few minutes, dominated by the reboot itself. If you have been on the 580 or 590 series drivers, the jump is uneventful.
Verify with cat /proc/driver/nvidia/version after reboot. You should see 615.71 in the version string. If your games still feel off after that, the bottleneck is almost certainly the Proton version in Steam, not the driver. Update Proton first, then come back to the driver.
Trade-offs
615.71 is not free in stability. NFB drivers ship faster, which means fewer soak weeks before release. Plan to spend an evening testing your most-played games before you commit to keeping it.
Idle power is not free in display stability. The flicker NVIDIA warns about is real. Budget extra debugging time if you turn it on inside a multi-monitor setup with mixed refresh rates, because the failure mode will not be obvious until something fails.
Branch choice is not free in either direction. NFB gets you the Reflex fix today. LLB gets you a more conservative codebase in two to four months. If you only care about the Blackwell display corruption fix and not about Reflex, the LLB wait is the right move. If gaming latency is the thing that drove you here, the NFB is the only choice.
Install downtime is not free either. Schedule the install for a moment when you can reboot without losing work.
Bottom line
If you play competitive shooters through Proton on Linux, install 615.71 this week. The Reflex fix is real, it shows up in the first match, and it is the kind of change that has been overdue for two driver generations. If you run a Blackwell GPU with output scaling enabled, install it for the display fix alone. If you run a workstation where uptime matters more than latency, hold for the LLB and stop reading here. Everyone else should treat this as the boring, important driver release NVIDIA should have shipped six months ago.