github RamazanKara/Rubylight v6.0.0
Rubylight 6.0.0

2 hours ago

Windows game streaming, written in Rust. Built for Radeon and NVIDIA. Made for Moonlight.

Download Windows x64 installer · Portable ZIP

New in 6.0.0

Rubylight 6.0.0 is a major release, and a lot happened on the way: it covers everything since 4.0.0, from 4.0.1 to 4.8.0, and a full round of new work. Since 4.0 your PC learned to reach your Nightjar devices over the internet without port forwarding, and now a friend joins your game from one link. Games that ship DLSS frame generation get frame generation from one switch, on Radeon and GeForce. RTX HDR and RTX Video enhancement moved into the regular, signed host. A stream keeps its frame rate under a capped game and an exclusive-fullscreen one, video packets grow to jumbo size on a 9000-byte wired network, and the console shows what every stream did and which stage took the time. Version 5 is skipped so the host and its client share one number: Rubylight 6.0.0 comes with Nightjar 6.0.0.

Highlights since 4.0

  • Invite a friend over the internet. One link from the console's Home or Nightjar's stream menu: the friend's Nightjar pairs as a guest without a PIN, finds your PC with no port forwarding and joins the game you play once you let them in. New in 6.0.0.
  • Play over the internet without port forwarding. Nightjar devices reach the PC from outside your network over a direct path through both routers, also behind carrier-grade NAT, found through a public peer-to-peer directory that holds only encrypted notes. No server of ours is involved.
  • Frame generation. A game's switch adds frame generation, through ANR (Apex Neural Rendering) by Apex Compute, to games that ship DLSS frame generation, on Radeon RX 5000 and newer or GeForce GTX 16, RTX 20 and newer. The game page says why a game can't have it before anything is downloaded, and a paired Nightjar device turns it on and off from the couch.
  • Play together from your own devices. A second paired device joins the game another one plays as its guest, with its own stream and controller, and you decide who joins and what a guest may do.
  • RTX HDR and RTX Video enhancement in the signed host. On a PC with an NVIDIA graphics card, one download from the console adds them, per game and from Nightjar. The installer and the host's programs carry a code signing certificate.
  • A stream that holds its frame rate. New virtual displays run at 1000 Hz, a game capped below the stream's rate keeps the stream at its full rate, an exclusive-fullscreen game no longer freezes the picture on Automatic, and a still desktop now keeps the full rate too.
  • See what every stream did. The Sessions page lists each stream, what it got against what it asked for, and the new stutter report names the stage that took the time: capture, conversion, encoding, packetizing or sending.

The sections below list what is new since 4.8.0; the earlier releases each have their own section.

Play over the internet

  • Invite a friend to play over the internet. Invite a friend on the console's Home, or in Nightjar's stream menu under Guests, makes a link to send to one person. Their Nightjar opens it, pairs as a guest without a PIN and finds your PC over the internet, with no port forwarding and no visit to your network; then they join the game you play once you let them in. The link works once and ends after a day by default; the friend's device gets guest rights only, is always asked about before it joins, and is unpaired when the invite ends. With Play over the internet off, the PC looks for invited devices only while an invite needs it.
  • Invite a browser guest from the internet in one step. A guest who watches or plays in a browser, without Nightjar, needs the guest ports forwarded. In the Stream page's Guests → Invite, pick On the internet: Rubylight asks your router to forward the guest ports (TCP 47991 and UDP 8002-8005) through UPnP, PCP or NAT-PMP, also with automatic port forwarding off, and puts your public address in the link, so there is nothing to type. Before you send it, the dialog shows each port the router forwarded or refused, your public address, and whether guests on the internet can reach the PC; behind carrier-grade NAT or a router that forwards nothing, it says so and what works instead (Tailscale, IPv6 or forwarding by hand). The ports stay forwarded only while such a link works or a guest watches, and nothing else is forwarded. Guests still click through the browser's certificate warning.
  • With automatic port forwarding on, the browser guests' ports are now forwarded only while an invite link works or a guest watches, instead of all the time.
  • The router notes tell carrier-grade NAT apart from a second router or modem. A private address such as 192.168.x.x or 172.16-31.x.x on the router's internet side now reads as another router or modem in front of it, with the advice to forward the ports there too or put it in bridge mode; only a 100.64.x.x address is the provider's shared address. The console's internet card and the invite dialog use the same words.

Streaming and bitrate

  • No more climb and collapse at a fixed limit. When the bitrate fails twice near the same rate, the host now holds at the rate it came down to and tries a small step above it only after a wait that doubles with each failure there, from 10 seconds up to five minutes. Before, it climbed back toward the requested rate and broke down again every 10 to 50 seconds on such a path (a device wired to a mesh node with a wireless backhaul, for example).
  • PyroWave under its own floor comes down too. A PyroWave stream whose requested bitrate is already under PyroWave's quality floor (4K120 at 800 Mbps, 1080p120 at 200 Mbps) is now lowered when the device loses video, to half its bitrate at most. Before, only the PC's own send failures could lower it, so a path that carried less held it in a full queue.
  • Deep buffers. Behind a router or mesh node that queues a lot, a step up now waits long enough for the queue to show it was too much, and a queue that stays after the bitrate came down is answered with a further cut.
  • When the PC cannot send fast enough. The sender waits about one frame for room in a full socket and then drops the rest of that one picture, instead of leaving holes in the next ones. The warning now says the PC could not send fast enough (its CPU or network adapter) instead of blaming the network, and such refusals alone no longer lower the rate the host learns for the network.
  • A connection that never fills up is unchanged.
  • A PyroWave stream below the level where the project's test scenes kept detail now warns in the player's stream. The host's stream card, the log and Nightjar's own notice say that text and textures may lose detail, with the floor, the mode and the rate the picture gets; the stream still starts at the rate the client asked for. Raise the bitrate with network headroom, lower the resolution or frame rate, or use HEVC or AV1.
  • A still desktop keeps the full frame rate. With constant-rate capture, or the still-picture resend, a desktop where nothing moves now holds the stream frame rate (180 instead of about 170 on a 180 fps stream).
  • NVENC streams above 800 Mbps keep changing their bitrate. The change limit is now the stream's own 2 Gbit/s negotiation limit, not a lower ceiling that failed a raise; a request above it uses the maximum and says so.
  • An older NVENC driver API shows a session warning naming the HDR10 metadata or split-frame encoding it cannot provide, instead of leaving that to the log.
  • A stock Moonlight client keeps its video while a jumbo-packet client streams. The shared video socket no longer has its don't-fragment setting turned on by a jumbo stream, so a stock client behind a WireGuard or Tailscale tunnel is never refused for the size of its packets; the jumbo path is still checked by the route's MTU offer and by the PyroWave probe on its own socket. If this PC's interface MTU on the route to a jumbo stream shrinks while it runs, the two-second route check now shows the network MTU warning on that stream instead of letting its packets fragment unnoticed.

Displays, HDR and capture

  • No magenta tint on small text in HDR. With HDR on, Windows' ClearType text (File Explorer's file lists, for example) could look magenta on the device: the stream shares one colour between neighbouring pixels, and the host mixed ClearType's red and blue glyph edges by their HDR signal values instead of by their light, which HDR's steep brightness curves turn into a visible cast. The host now mixes them by their light in HDR10 and HLG streams, PyroWave's included, so text keeps its colour with ClearType on. SDR streams and full-chroma (4:4:4) streams are unchanged. AMD's video converter (the amd_vpe setting, off by default) does this mixing in hardware and still shows the tint.
  • RTX HDR streams describe the HDR picture they generate. The stream's mastering peak is the peak RTX HDR was set to produce, not the SDR monitor's reported peak, and its content light levels stay unknown instead of claiming the panel's; HDR tone mapping on the client now follows what it receives.
  • Two streams share a display's capture only when their Capture method agrees. An explicit Windows Graphics Capture stream is no longer moved to Desktop Duplication because an Automatic stream opened the shared capture, so choosing a method keeps it.
  • The virtual display stays the main screen with "Extend — make virtual display primary". When a game or Windows moved the main screen back to your monitor, every later stream from that device started that way and the setting looked ignored. When Windows changes the displays by itself, such as a monitor arriving or leaving or coming back from the lock screen, the stream now puts the virtual display back as the main screen within about a second, and its card says so if Windows refuses or keeps taking it back. A main screen you pick yourself in Windows stays yours. Devices that kept the wrong layout follow your setting again.
  • Older device layouts are updated once. When the host asks for the virtual display as the main screen, an older device layout is dropped and the device follows the host's display layout again; otherwise the device keeps Extend, now marked as learned, and an app's own layout or a later change of the host's layout replaces it. Pick it again under Devices to keep it everywhere.
  • The device page says when a stream set its layout. Next to Virtual display layout, a learned layout reads "Learned from your last stream: …", and Clear makes the device follow the host setting again.

Console and sessions

  • See which stage took the time. The console's Stream details & performance now says where a stream's new pictures lost time against the stream's own usual path, naming capture, conversion, encoding, packetizing or sending, and each stream's end writes a stream stutter report line to the log with the same figures. It measures the host's part only: the network, the decoder and the display come after the last packet, and a game slower than the stream shows as repeated pictures instead.
  • The Sessions page shows what the stream got against what was asked. A stream the network held below its request reads "X of Y Mbps" instead of the lower rate alone.
  • A game that waits for sign-in can be cancelled from its device. A launch started after sign-in is now owned by the device that asked for it, so End session or Quit on that device cancels it while it prepares.
  • Turning automatic updates off removes a half-finished download from the install folder at the next housekeeping pass, instead of leaving it there until the host restarts.
  • A settings save that fails no longer changes the SteamGridDB key. The key is stored only after the settings file has been written, and when the key itself cannot be stored or removed the other settings still apply and the console says what happened to the key.

Controllers and input

  • The motion server for emulators now serves this PC only. It listens on 127.0.0.1 unless Motion server on the local network (dsu_server_lan) is turned on, so an emulator on this PC works as before while a cafe, hotel or public network no longer reaches the streamed controllers. The server also serves at most 16 emulators and four controller addresses each, so a flood of requests can no longer hold up controller input; turn the new setting on only on a network you trust.
  • The console has the local-network switch beside the motion server. It appears under Controllers when the DSU server is on, says what it exposes, and warns that the server has no password; like the server, it applies after a host restart.
  • A controller the client turns back on is no longer dropped as removed, and one controller's failed report no longer skips the other controllers' back-button update.
  • A virtual controller is unplugged before its replacement is plugged, so two pads never exist for a moment in the same slot.

Fixes

  • A console launch is cancelled when the host service stops, as a device's launch already was, so no game outlives the host and its preparation commands are undone.
  • A game that ignores close no longer keeps the stream's display and audio route at shutdown. The display layout goes back before the game is asked to close, and the audio route follows once the game's processes have stopped, before its undo commands, or before the shutdown's stop wait runs out for a game that never closes.
  • Exiting Playnite Fullscreen after playing a game ends the stream again, once the Wait after a game closes time has passed, instead of leaving the stream on the PC's desktop.

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.

Full release notes · Build and tests · Code signing policy · Host validation

Don't miss a new Rubylight release

NewReleases is sending notifications on new releases.