Windows game streaming, written in Rust. Built for Radeon and NVIDIA. Made for Moonlight.
Download Windows x64 installer · Portable ZIP
New in 6.2.0
Rubylight 6.2.0 puts every setting in its own topic tab and turns clusters of related switches into single choices. The console's Expert section is gone, and adaptive bitrate, packet pacing, error correction, what happens when a device disconnects, removing a remote monitor and updates are each one setting that carries your earlier choices over. The host also does less work per frame, a refused gamepad driver connection is recovered, Battle.net games installed by current launchers are recognized again, and a display left in a half-applied mode by a crash is put back.
Highlights
- One topic tab for every setting. The Expert section is gone; groups most people leave alone start collapsed, and search still finds every setting.
- Related switches became single choices. Adaptive bitrate, Packet pacing, Error correction, Library sync, Updates, Remove remote monitor and When a device disconnects each replace two or three settings, and your saved choices carry over.
- A lighter host. Fewer copies, allocations and lock round-trips per frame, and audio and control loops that sleep to their deadlines.
- The virtual gamepad driver's refusals are recovered by reconnecting to it, with a clear message in the console when it keeps refusing.
- A TV left at the wrong resolution or refresh rate by a crash is put back, and ending the Windows session during a stream now ends it at once on the client.
- Couch menu, Night mode and Headphone surround have settings in the console, and Battle.net games installed by current launchers are recognized again.
Settings
- All settings has no Expert section any more. Every setting is in its own topic tab, with the others in its group; groups most people leave alone start collapsed and open once one of their settings is changed. Search still finds every setting, and links to the former Expert groups lead to the topic tab.
- One Graphics card choice. Two identical graphics cards are now listed one by one in the Graphics card list, so the separate device ID row is gone from the console. Your saved card, and a saved device ID, still apply.
- Send batch size and Overlap PyroWave frames moved to Advanced, Debug switches. They are only for troubleshooting.
- The NVIDIA minimum quantizer switch is gone. Each codec has its own minimum QP, and 0 (the default) is off. A minimum quantizer you had on keeps its values; one that was off stays off.
- Three driver switches are gone. The compute queue that copies and converts captured frames, and PyroWave's encode queue, always run at high priority; the real-time option that could hang the graphics driver is removed. The AMD encoder always uses the driver's own input queue size and low-latency mode.
- Updates is one choice. Off, Tell me (the default) or Install automatically. Tell me checks for a new release and lets you know; Install automatically also installs it when nothing is streaming. Your saved choices carry over: automatic installation on becomes Install automatically, and checks turned off become Off. How often it checks, and the daily check time, show when Updates is not Off.
Streaming and performance
- Adaptive bitrate is one setting. The console's two bitrate switches, Lower the bitrate when the link cannot carry it and Adapt to network congestion, are now one Adaptive bitrate setting with three choices: Off, On, and On, and react to network delay. Your earlier choice carries over, also in each app's and device's own settings: if you had the bitrate adaptation off, it stays off.
- One Error correction percentage for every codec. PyroWave now follows Error correction like H.264, HEVC and AV1, so a stream that used PyroWave's own 20% now uses your Error correction percentage; a PyroWave value you had set to something different stays and keeps showing. The settings Adapt error correction (which saved no picture bitrate) and Most error correction a device may ask for (fixed at 50%) are gone; Nightjar's Automatic still works.
- One Packet pacing setting replaces three. Pacing rate, Adaptive packet pacing and Adaptive packet pacing for Wi-Fi clients are now Packet pacing: Automatic (the default, as before), Always adaptive, Off, or a fixed rate in Kbps. Your saved choices carry over.
- On AMD, a new picture no longer waits for the host's check on the encoder before it is encoded. The encoder's output is now collected on a thread of its own. Beside a 60 fps GPU load at 1440p120, up to 2 % of pictures had waited about 1 ms there; at 4K120 with the GPU saturated, 7 % waited up to 2.2 ms. Now at most 0.3 % wait, for at most 0.06 ms, and the slowest encodes finish sooner. End to end latency did not improve. It costs about 1 to 1.5 % of one CPU core.
- Capped games' frames are sent as they arrive. The phase lock no longer holds a game running at the stream rate or slower for the device's refresh, whatever Hold capped games for the device's refresh said: on a Shield TV the hold added 8 to 11 ms of latency, and it halved only its rare display gaps.
- The still-picture resend keeps to its schedule with the default frame pacing. When nothing on screen moves, the still-picture resend no longer falls further behind with every frame under arrival pacing (6.0.0 fixed this only for Fixed grid pacing and constant-rate capture), and a resend never delays the next new picture.
- The host does less work for each frame, and its loops sleep until their next deadline. The send path, the error-correction plan, the encoder wrappers, input handling and the control loop make fewer copies, allocations and lock round-trips per frame, and the audio and control loops and the idle maintenance loop sleep to their own deadlines instead of polling. The 30-second library check skips work whose inputs did not change, and Moonlight discovery reads the network interfaces again only when Windows reports a change.
- Shutting down Windows during a stream now ends it at once on the client. Windows ended the host with the session before the Rubylight service heard of the shutdown, so clients waited for their connection to time out, and a USB device forwarded from the client ended with an error. The host now notices the end of the session itself: it tells its clients that the stream ends and detaches forwarded USB devices, as when the service stops, and lets Windows go on within a few seconds.
Controllers and input
- When the virtual gamepad driver stops accepting the host's connection, Rubylight reconnects to it instead of failing every request. After a reboot on some PCs, the driver refused every controller request with 0x80070006 about half a second after a controller connected; the host kept asking about 118 times a second until it restarted, and the console blamed the gamepad profile (issue #138). Rubylight now closes the refused connection and opens the driver again a second later, without waiting for input, and connects each controller again as the same controller type, in the same order. From the third refusal without a minute of working controllers in between, it waits at least 10 seconds before each new attempt, and the console names the driver and suggests restarting the Vibeshine Virtual Gamepad device or running setup again. After the fifth, until the next stream or game launch starts, it tries again only when a controller is used and at most once a minute, and the console says so. A driver whose device has gone missing is not counted as refusing and is still tried every 10 seconds. Whether a new connection keeps working on an affected PC has not been reported yet.
- The controller type Automatic picks the Steam Controller for Nightjar's on-screen Steam Controller controls in apps started through Steam. It does so when the stream's app starts through Steam (Steam Big Picture, a
steam://link, asteam.execommand or a game from the Steam library), Steam was running as the controller connected and the gamepad driver has the Steam Controller. Every other app, the Desktop included, keeps the Xbox-type controller; so does a Steam app without Steam running or with an older gamepad driver, and the stream then says what to do. - Nightjar's on-screen Steam Controller controls no longer turn player 1 into a DualSense. With the controller type on Automatic, their trackpads made the PC pick one, which has none of their back buttons or grips and which games that read only Xbox controllers cannot see.
- Touch and pen click delay per app and device. Set it for one app (under Video and input) or one device (under Touch and pen), for a game that misses taps or reads them as a drag.
Displays
- A TV stuck at the wrong resolution or refresh after a crash is now put back. When the host died between asking a display for a new mode and recording the mode it actually took, the TV could keep a half-applied mode (the new resolution at the old refresh) until it was changed by hand. Recovery now recognises that the stream never finished and restores the mode it had before, while a mode you changed yourself after a stream is still left alone.
- A game or video behind the window in front is no longer held when that window repaints in short bursts. A terminal app printing in front of a 60 fps picture made the host hold that picture 50 ms at a time: 56.0 fps with 21 such holds in 12 s on an RX 7900 XT, now 60.0 fps with none. The window in front now counts as moving only once it has kept changing for half a second, as a game or video does.
- A fixed resolution, refresh rate or rotation is set in the same row. Choosing the fixed option under Resolution, Refresh rate or Rotate the display now shows its value right under the choice, instead of a separate row. Your saved values are unchanged.
- With no display attached, the host reports the codecs of the graphics card that encodes the stream. On a PC with an AMD integrated GPU and an NVIDIA card, the check ran on the integrated GPU, so clients were offered its codecs (for example no 4:4:4) while the NVIDIA card encoded.
- Removing a remote monitor is one setting. The console's two switches, Remove when its stream ends and Remove when the device disconnects, are now one Remove remote monitor setting with three choices: Never, When its stream ends, and As soon as the device disconnects. Your earlier choice carries over.
- One choice for what happens when a device disconnects. The console's Restore displays on disconnect is now When a device disconnects: Restore after the delay (the default) or Keep while paused. If you had restoring turned off, it carries over as Keep while paused, also in each app's and device's own settings. Keep monitors off while paused stays its own setting, and exclusive layouts still bring your monitors back after the delay unless you turn it on.
Library
- Battle.net games installed by current versions of the launcher are recognized again. Diablo IV and other products that Battle.net records under a long id such as
fenrisshowed up under that id in Add games, marked as not recognized and with no way to add them. Rubylight now looks each product up by its product code and gets its name and launch command from that. A product it still doesn't know is named after its install folder. - One Library sync group for every launcher. The Games page had the same five options for each launcher (Sync automatically, Remove uninstalled games, Every installed game, Recent games, Played within). They are now one Library sync group, and each launcher keeps only its on/off switch and Games to leave out. Your saved choices carry over: the value all your launchers agreed on becomes the shared one, and a launcher you had set differently keeps its own value.
Console and sound
- The couch menu has its own settings under Sound & controls. Turn the menu off, choose which ways open it (controller chord, keyboard chord, top-left corner hold), and change the chord and hold times. Before, this took editing the configuration file.
- Night mode and Headphone surround are now settings under Sound. Each device can also set its own in its editor, in place of the host's choice. Before, they could be switched only from the couch menu during a stream or in the configuration file.
Tested. Before the tag, a release candidate built from this release's code ran the hardware check on a PC with a Radeon RX 7900 XT: H.264, HEVC, AV1, HEVC with variable refresh rate, PyroWave and PyroWave HDR 4:4:4 streamed at about 60 fps with no long frame interval, two HEVC runs at 1440p and 120 fps held 120.0 fps, and the protocol checks passed. With a laptop with Radeon 780M graphics as the host and desktop Nightjar's 6.2.0 candidate on that PC as the client, HEVC at 30 Mbps and PyroWave at 150 Mbps at 1080p and 120 fps showed 74.6 and 77.1 fps, against 77.9 and 75.7 fps from 6.1.0 on the same pair; no encoder hang was logged and encoder focus was applied with every codec.
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.