The Witcher 3's Linux stutter looks like a network check running 10 times a second

The stutter Linux players report in The Witcher 3: Wild Hunt looks like a network check rather than anything to do with the graphics card. A Wine bug report filed on October 8 at 22:56 UTC says the game asks Windows whether the machine is online about 10 times a second on its main thread, and that under Wine each of those calls rebuilds the whole list of network adapters.

The stutter reports concern the Windows build of the game running under Proton. Image: CD Projekt Red Image: CD Projekt Red

The report puts the cost at a 35 ms stall roughly every 100 ms, measured on the reporter's own machine as 55 to 63 fps with a 1% low of 17 to 20, against 88 fps and a 1% low of 63 once the answer was cached for two seconds in a proxy DLL. It is filed as unconfirmed, so this is one developer's reading of the code rather than a diagnosis the Wine project has accepted.

The mechanism it describes is cumulative. Wine's nsiproxy driver never drops network interfaces that have gone away, so on a machine where containers, virtual machines or VPNs come and go, the list the game rebuilds 10 times a second keeps getting longer. On the reporter's host, 70 containers took the adapter count from 11 to 115 and one call from 5.0 ms to 39.8 ms.

A third-party Proton build has shipped a fix

Wineland 11.0 (20261011) was published at 12:01 UTC on October 11, and says it has "reduced stuttering in The Witcher 3 by avoiding repeated network adapter enumeration during frequent connectivity checks". This is the proton-cachyos project's own build, which a player installs for themselves, and not Valve's Proton.

The same release fixes a Wayland startup problem in AION2, improves fullscreen monitor selection when windows are moved or displays reconnected, restores native HDR signalling for overlays, and adds a setting that fully disables Steam's overlay for a Wayland launch. It also rebases DXVK and vkd3d-proton on upstream.

A second profile blames one network interface

A contributor posted measurements of their own on Valve's Proton tracker at 19:51 UTC on October 11, eight hours after that build went out, so the two arrived independently. On that machine the stutter they profiled appears while the game is signed in to a CD Projekt Red account: the game polls the same connectivity call about 10 times a second, each poll reads the statistics for all nine network interfaces, and an Intel I226-V takes about 107 microseconds per read with its link up against about six microseconds for the others.

That worked out at about 6 ms of blocked main thread per poll, or one roughly 15 ms frame every 100 ms at an otherwise steady 7 ms. Taking the Intel link down moved the 99th-percentile frame time from 16 ms to 8.8 ms, and signing out of the account did the same job. The post is an individual contributor's work rather than Valve's, it says it was generated with an LLM, and its numbers come from one machine with one network card. A profile is not a patch, but Valve's Proton maintainer answered an LLM-assisted fix on October 3 by pointing at Wine's rule against LLM-generated code.

The profiling went into Proton issue 607, the 2018 report that now carries the remaster's name alongside a 2015 Steam date and a Verified badge. A day later another contributor pointed that thread at the Wineland release and quoted the same fix line.

The fix a player can install today sits in that third-party build rather than in Valve's Proton, and neither Valve nor CD Projekt Red has commented on the stutter.