Windows game streaming, written in Rust. Built for Radeon and NVIDIA. Made for Moonlight.
Download Windows x64 installer · Portable ZIP
New in 4.7.0
Rubylight 4.7.0 adds jumbo video packets on a 9000-byte wired network with Nightjar 5.8.0, streams only a windowed game's content, runs new virtual displays at 1000 Hz, and wakes a monitor that Windows switched off before a cold launch. NVENC uses both engines when one is not enough, and the controller settings and the host log explain more. The rest are fixes from the new issue reports.
Highlights
- Jumbo video packets. Nightjar 5.8.0 can stream up to 8192-byte video packets on an on-link path that carries 9000-byte frames; stock Moonlight clients and 1500-byte paths are unchanged.
- Only the game's content. A windowed game can be streamed without its title bar and borders, with input mapped to the content.
- 1000 Hz virtual displays. New virtual displays run at 1000 Hz, so a capped game waits at most 1 ms for a refresh.
- A cold launch wakes the display. A stream to a PC whose monitor Windows switched off while idle wakes it before the first frame, and the first-frame state is in the log.
- Both NVENC engines when one is not enough. Split encoding now follows the frame budget, and the Lowest latency preset asks for it.
- The DualSense note. The controller settings and docs explain a game that drifts with the VHF pad and the USB/IP alternative.
- HDR changes are logged. Every set, restore and skip names the display and the previous and applied state.
Details
- A cold launch wakes the console display. When a stream starts while the PC's monitor is off and nobody has used the PC for a minute, the host sends a net-zero mouse move on the input desktop and, if the driver still reports no swap chain after a second, does it once more. The host log now records the first-frame wait's swap-chain and ring flags, display path, secure desktop and idle time. Nothing changes when the display is on or the user is active.
- Controller settings explain a game that drifts with the DualSense. Some games read the controller's name and can treat the VHF DualSense as an unknown controller, so the camera or cursor can drift with no input; the controller settings and docs now say that the VHF pad reports the virtual gamepad driver's name and has no USB parent, and that such a game can use DualSense with waveform haptics (USB/IP) (usbip-win2, Sony's USB identity, any client) or Xbox Series. Automatic selection is unchanged.
- HDR changes are in the host log. The host log now records every HDR set, restore and skip with the display and the previous and applied state, on the normal teardown as well as startup recovery. The settings and the behaviour are unchanged.
- Larger video packets for clients that ask. On a path whose interface MTU is above 1500 bytes and whose peer is on-link, the host lists
MaxVideoPacketin serverinfo and the stream'sx-rl-max-packet-sizein DESCRIBE. Nightjar can then ask for up to 8192-byte video packets, so the stream sends far fewer packets at the same bitrate. The host refuses fragmentation on a jumbo video socket and reports a datagram the path refuses as anetwork_mtuwarning without ending the stream. Stock Moonlight clients ignore the fields and keep 1400-byte packets; a 1500-byte path (Wi-Fi, a tunnel or an unknown route) offers nothing. - Both NVENC engines when one is not enough.
nvenc_split_encode = autonow keeps the driver's implicit split and also splits HEVC or AV1 frames when one engine's estimated frame time misses the frame budget.driver_decideskeeps only the driver's implicit split, and the Lowest latency stream preset asks for split at every preset. Splitting is faster and can cost some picture quality. - The frame time guard no longer counts engines that cannot split. It accounts for H.264, drivers before NVENC API 12.2, one-engine GPUs and HEVC weighted prediction, and reports the split decision in the host log.
- 1000 Hz by default. New virtual displays run at 1000 Hz, so a game capped at the stream's frame rate waits at most 1 ms for a refresh. With a test picture capped at 60 fps, 0.04 % of frame intervals were more than 4 ms off at 1000 Hz, against 0.23 % at twice and 2.22 % at four times the stream rate, where frames can land in alternate refresh slots as the cap's timer drifts onto the display's refresh. An earlier run measured 1000 Hz about 1 ms slower than twice the stream rate at 60 fps. Twice and four times the stream rate stay selectable, and Off still ends the automatic FPS cap.
- A refused refresh no longer leaves the display slow. When Windows refuses the refresh a virtual display asks for and keeps a slower one at the right resolution, the display now asks for the fastest refresh it offers below the refused one, without a warning.
- Stream only what a windowed game draws. With What to stream set to the app's window, the new Window's frame setting (
capture_window_frame,fullby default) can keep only the game's content, cropping the title bar and the borders before encoding. Input maps to the cropped content, and a game that draws its own title bar keeps it. Set it for every app, one app, or one app on one device, as for What to stream; the default stays the whole window.
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.