Windows game streaming, written in Rust. Built for Radeon and Moonlight.
Download Windows x64 installer · Portable ZIP
New in 2.5.11
- Return completed capture buffers without a cursor update. Since 2.5.6, completed GPU conversions could keep all four frame-push capture slots owned when no separate cursor overlay was drawn. PyroWave then waited for a new frame that capture could not produce. Conversion now releases completed slots on every frame. This is unrelated to Nightjar's local cursor setting and addresses a reproduced cause of the slowdown investigated in #42.
- Keep PyroWave alignment inside the wire budget. Record padding could enlarge a frame after the codec had applied its bitrate budget: a native GPU fixture configured for 400 Mbps produced packets requiring about 447 Mbps at 60 fps. Alignment is retained when its packets, headers and adaptive critical parity fit; otherwise the existing unpadded record format preserves the encoded pixels. Recovery protection can be reduced on that fallback, with the existing warning retained. The budget also covers lower adaptive FEC percentages that restore parity at the 255-shard limit. The padding issue predates 2.5.6.
- Interrupt packet pacing when a PyroWave stream stops. An extremely low pacing cap could leave disconnect waiting for a long packet deadline and send another packet afterward. Shutdown now wakes that wait and rechecks cancellation before sending, without changing normal pacing or its adaptive wake lead.
Verification and limits: All 1,302 workspace tests, six native AMD Radeon 780M GPU tests, 78 release-tooling tests, formatting and workspace Clippy passed. The capture regression fails before the fifth frame without its fix and completes 16 frames with it. The framing regression checks 12 scene/bitrate combinations at every adaptive critical FEC percentage from 0 to 20 and preserves decoded pixels. The real-sender cancellation regression fails before its fix and now completes teardown within 250 ms without another packet. Independent QA reviewed the changes. The desktop AMD driver reset remains unexplained, and performance recovery on the reporter's setup still needs a live stream test.
Install or upgrade
Disconnect your stream and close host-launched games, then run the installer. Your settings, paired devices and game library are preserved. Open the console at https://localhost:47990.