Windows game streaming, written in Rust. Built for Radeon and NVIDIA. Made for Moonlight.
Download Windows x64 installer · Portable ZIP
New in 4.8.0
Rubylight 4.8.0 is about a stream that never lets go of its frame rate, and a console that tells you why. A game capped below the stream's rate now keeps the stream at its full rate, an exclusive-fullscreen game can no longer freeze the picture on Automatic, and the console names the game or the desktop when it is what holds the stream back. A new Sessions page lists what each stream did, SteamGridDB fills in missing covers, a resolution cap and a DualSense haptics strength join the settings, and controllers play again after the PC wakes. It comes with Nightjar 5.10.0.
Highlights
- Full rate under a capped game.
capture = wgccsends the last picture again whenever the game has none ready, so a 90 fps game on a 180 fps stream keeps one frame per stream frame. - No frozen picture from an exclusive-fullscreen game. On Automatic, a display that sends nothing for 2 seconds is captured with Desktop Duplication instead.
- The source's frame rate in the console. A game or desktop that renders below the stream's rate is named after 15 seconds, with what to change.
- Sessions page. Advanced, Sessions lists the streams running now and the last 200 that ended, kept for 90 days.
- Covers from SteamGridDB. Apps without a cover get one, in Moonlight, Nightjar and the console.
- Smaller picture for a slower network. A host-wide stream resolution cap, while the PC's display keeps the size the device asked for.
- Controllers after sleep. A controller connected when the PC slept plays again when it wakes.
- Signed releases. The installer and the host's programs carry a code signing certificate.
Streaming and capture
- An exclusive-fullscreen game or emulator no longer freezes the picture on Automatic. Windows Graphics Capture reads what Windows composes, and an app in exclusive fullscreen presents past that, so its picture stops with no error while the app keeps running. On Automatic, a streamed display that sends no picture for 2 seconds while Windows reports an exclusive-fullscreen app in front is captured with Desktop Duplication instead, which reads what the display shows, and the stream card says why. A named Capture method is never changed automatically; timing and HDR under Desktop Duplication can differ.
- A game capped below the stream's frame rate keeps the stream at its full rate. Capture method → Windows Graphics Capture, constant rate (
capture = wgcc) sends the last picture again whenever the game has no new frame ready for a stream frame, so a 90 fps game on a 180 fps stream keeps one frame per stream frame instead of the encoder repeating a still picture between the game's frames, and a new game frame is never held back for its slot. Every repeat is encoded like any frame, so the stream spends its bitrate between the game's frames too, and a still picture keeps the full rate; leave it off on a mostly still screen. It applies to the launched app's window as well; on a display, Desktop Duplication keeps the rate when Windows Graphics Capture is unavailable. Off by default. - A configuration that already says
capture = wgccnow turns this on. Earlier builds read that Vibepollo spelling as plain Windows Graphics Capture; usecapture = wgcfor variable-rate capture. Configurations that never set it keep Automatic, so nothing changes for them. - Maximum stream resolution. A host-wide cap keeps a 4K device from streaming 4K to a network that cannot carry it: the picture is encoded no larger than the cap while the PC's display still runs at the size the device asked for, and the device scales the smaller picture up, so fine detail softens (
max_stream_resolution, native by default). The console's stream card and the host log name the coded and display sizes; a Nightjar device that changes size mid-stream can keep the smaller picture as its next request until its resolution is chosen again. - The console says when the game or desktop holds the stream back. When the source stays below 97% of what the stream can show for 15 seconds it shows about how many frames per second it is rendering: on a game stream it suggests lowering the game's settings or the stream's frame rate to match, and on a desktop stream it only says how often the screen is updating. What the stream can show is its own frame rate, or the display's refresh rate when that is lower, so a 60 Hz monitor streamed at 120 fps is not reported. A short dip, a level change or a still picture does not trigger it, a still screen clears a standing warning after 30 seconds, and the host log says when the source keeps up again.
Controllers and input
- Controllers keep working after sleep. A controller connected when the PC went to sleep plays again after it wakes, instead of only after reconnecting it. This covers the built-in gamepad driver's controller types, the default; the optional ViGEmBus and USB/IP controller types are not changed.
- DualSense haptics strength. A game's own waveform haptics on a DualSense with waveform haptics (USB/IP) can be scaled from 0 to 4 times what the game sent, under Sound & controls → Controllers (
dualsense_haptics_gain, 1 by default); ordinary vibration, the lightbar, adaptive triggers and controller speaker sound keep the game's strength. A device or an app can set its own. - The Steam Controller's left grip works. With the Steam Controller controller type selected, the left grip touch now registers on the PC instead of being dropped along with a Switch 2 Pro Controller's C button.
Console and setup
- What each stream did, and what runs now. Advanced → Sessions in the console shows the streams running now and up to the last 200 that ended, with the device, game, codec, resolution, average and p95 frame rate, bitrate, the loss the device reported, how long each ran and why it ended, in the host's words. The history is kept in the host's data directory for 90 days and drops the oldest sessions by itself (the caps are fixed, not settings), the list reloads when a stream ends, and the live half refreshes every 2 seconds without the stream card's polling.
GET /api/sessions/historylists it for scripts and a Home dashboard. - Covers for apps without one. Paste your SteamGridDB API key under Settings → Games → Covers and every app without a cover gets SteamGridDB's best-voted 600x900 grid, found by its Steam app ID or else by its name, in Moonlight, Nightjar and the console alike. Covers you chose and launcher covers are never replaced, a launcher's cover found later takes over, and a cover you clear stays cleared. The lookups run in the background, a few apps at a time, and wait whenever SteamGridDB asks for fewer requests. The key is kept where only administrators can read it, is sent only to SteamGridDB, is never shown again or logged, and a settings backup holds it only with secrets.
- The console says where to start. Once a device is paired, Home says where a game starts and names the device, Stream resolution is on the Settings home (Match the device, or keep the current resolution), the stream preset reads as delay against picture quality, and the launcher, capture and Steam Deck options open in place under All settings.
- Signed releases. The setup program and the host's own programs are signed with a Certum code signing certificate for open-source developers, issued to Open Source Developer Ramazan Kara, by the release workflow.
Fixes
- A stream returns to Windows Graphics Capture after a UAC prompt or the lock screen. Windows Graphics Capture falls back to Desktop Duplication on the secure desktop, and a reopen now uses the capture method the stream is set to again, instead of staying on Desktop Duplication for the rest of the stream. Only a game picture moved to Desktop Duplication by the fullscreen fallback stays there for the session. A display push or AMD Direct Capture that was unavailable once is tried again on a reopen too.
- The NVIDIA components install and remove on PCs where another account may change the drive or
C:\ProgramData. Before Download or Remove, Rubylight checked every folder above its own, up to the drive, and refused when Windows lets any other account change one; the installer never needed that, so the console showed "can be changed by another account" even when Rubylight ran as administrator (issue #115). It now checks only its own folder,%ProgramData%\Butterpollo, and what is inside it: a link on the way, or one of its own folders another account may change, is still refused. From that check until the components are loaded, Rubylight holds its own folder open and every folder down to the components, and Windows then refuses to rename or delete any of them, so the folder named a moment later still holds the files that were checked, even on a PC where another account may move folders inC:\ProgramDataitself. Neural Rendering's download is still checked up to the same folder.
Tested. No stream was run on this release's changes: constant-rate capture, the fullscreen fallback, the resolution cap, the haptics gain, the source frame-rate warning, session history and SteamGridDB covers are covered by unit tests (the SteamGridDB lookups with a fake HTTP layer), and none has run on a GPU, a DualSense or against SteamGridDB itself; the next reports settle that. Rubylight's builds, tests, clippy and the console's checks pass in CI on the tagged commit.
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.