this is 1.5.0-rc.1, for people who choose Beta. Stable 1.5.0 isnt published yet, so use the files attached to this release. also the one-command repository installer still installs Stable, not this RC, and updates from repo.papi-ux.com stay on Stable too. the change list below describes the planned 1.5.0, thank you for trying it early!
Polaris v1.5.0
There's a lot in this one, which is why it's 1.5.0 and not 1.4.14. Mission Control is rebuilt around the game you're playing, Steam can be driven from the couch, Fedora 45 and SteamOS 3.9 hosts get packages of their own, PyroWave gets the bitrate it needs, Live Tuning is on and acts on the frames a stream really loses, and when a stream can't work the host tells you why instead of guessing. Your settings, paired devices and Spaces keep working.
Coming from 1.4.13? All of it is new. Ran a 1.5.0 beta? The last part of Heads up before you update is for you. Nova's side of these changes is in its own release notes. And thank you to everyone who sent a report, a log or a PR this cycle, you're all named under Thank you near the end!
Highlights
- Mission Control, rebuilt. One stage for what's playing or up next, with the game's own Steam art, a Recent games shelf, a live session card while you stream and one Diagnostics section. There's a sixth theme,
< Congratulations, Director >, and the console fits phones and tablets. - Launch to the device in your hands. Nova for Android opens the console as Host Console, and Launch there streams the game to that device instead of only starting it on the host.
- Steam, from the couch and on the Deck. Desktop Steam can stay open after End Session, Nova can open or quit Steam on the host, and SteamOS 3.9 gets its own package. An app can opt in to leaving Game Mode before it launches, on SteamOS 3.9.
- Fedora 45, packaged. Fedora 45 gets its own package beside Fedora 44, and the one-command install sets up either one, checking the signing key before it trusts it.
- Updates you approve on the host. On Fedora 44 and 45, Mission Control reviews an update, asks for approval through the host's own administrator prompt and restarts Polaris only when you choose Finish.
- Live Tuning, redesigned and on by default. It reads the frames each client report says were lost, settles just under what the link carries, leaves alone loss a lower bitrate can't fix, and climbs back a step at a time after a link drops. Turn it off and it stays off.
- Enough bitrate for PyroWave. Advice from the model PyroWave's author published, up to 500 Mbps set by hand, and a stream the host can't feed is turned away before it starts, with the reason.
- Evidence, not guesses. Fix My Stream shows the host's own findings before a stream, Doctor talks plainly and names the mode a stream really uses, and a Tailscale peer readout describes the control connection, not where video goes.
- Games from Epic's Linux Preview. Library imports games you installed with Epic's official Linux Preview launcher. They play in Mirror Desktop, or in Private Stream if you choose it for the game, and End Session leaves a Mirror Desktop game running unless you let Polaris close that exact game.
- Spaces is no longer a preview. It's fleshed out now, so it shows up as a full feature, with no Preview labels left in the console or the docs. It's still one Space at a time, and the limits that are left are written down plainly in the guide.
- Experimental, off by default. Source-paced VRR on Private Stream, which current Nova builds do not request, a Recording tab that saves raw video with no audio, wire pacing, and a native step-down trial for Live Tuning that only the config file turns on.
Mission Control and the console
- Mission Control leads with one stage for what is happening now: the running title while you stream, or the next title while the host is idle. Behind it is the title's own Steam background, or a softened copy of its cover when it has none, and its logo takes the place of the name when the logo reads clearly. Each state has one main action, and a reading the host didn't send shows a dash and a reason instead of a zero. Frame health, pacing, host vitals, launch checks and session history sit in one Diagnostics section.
- While you stream, a live session card shows the game and its cover, the device, how long it's been going, Disconnect Client and End. Over Tailscale it adds a chip for what the host confirms about the connection: direct, DERP relay or peer relay. It says nothing about the video route, and a stream over your LAN gets no chip.
- Recent games is a shelf of up to eight posters under the stage. Selecting a poster features it and starts nothing; Launch on the poster starts it. To show those backgrounds and logos, the host fetches a Steam title's missing images once, in the background, from Steam's own image servers, never from SteamGridDB, and fetches nothing for Desktop entries or after Remove artwork.
- When Nova for Android opens the console as Host Console, the console takes Nova's theme for that visit and hides its guide links, and Launch hands the title to Nova, which streams it to the device in your hands. Your saved theme doesn't change.
- A sixth theme,
< Congratulations, Director >, brings Nova's Director look to the console: near-black charcoal, warm white text, and red kept for focus and active markers. Polaris Aurora stays the default, and a theme you already chose is kept. - The console fits phones and tablets in portrait and landscape, and with doubled text: the sidebar becomes a drawer whenever the page is narrow, and the theme picker stays on screen.
- Little touches too: when a stream ends, the Last session cell briefly shows how it went; a device that pairs or connects is named once in a quiet toast; the browser tab says when a stream is running; the command palette has Spaces shortcuts; the Bitrate and Loss charts mark where Live Tuning changed something; and posters fade in, with a soft tint from the now-playing art. Reduced motion turns the decoration off.
- Library rows get a Launch button, poster fallbacks and Move up/down, and secondary text is easier to read.
- Settings says what Save changes, when a restart is needed and that restarting disconnects streams, and keeps edits made while a save is in flight. PyroWave gets one card above Encoder Profiles with availability, requested and encoded bitrate, and the encoder input route. Launch cards name the provider and what happens to your physical screen.
- The Where games run cards point AMD and Intel GPUs to Private Stream, and supported NVIDIA hosts to Private Stream (GPU-native). Thanks to coreydeli. (#804)
- Welcome's Network step lists the ports Polaris really uses for the base port you configured, with RTSP on TCP and the web console listed separately. It used to name a UDP port nothing listens on.
- An End confirmation you left open no longer carries over to a different stream that replaced it, and narrow cards wrap instead of overflowing.
- Side note: click the version in the sidebar a few times. And try
polaris --versionin a terminal.
Steam and the Steam Deck
- Desktop Steam can stay open after End Session. Settings has Keep Desktop Steam Running After End Session, each app can inherit it, keep Steam or close it, and End Session then closes only the game that stream launched. Steam and games that were already open stay yours.
- Nova can open Steam, open Big Picture or ask Steam to quit on the host, from its PC menu or Command Center. Quitting with a game running asks first. Viewers, another client's session, private runtimes and Game Mode are refused.
- SteamOS 3.9 gets its own package,
Polaris-steamos3.9-x86_64.pkg.tar.zst, with its own capture helper and debug symbols, because SteamOS 3.9 can't load the 3.8 package's libraries. Each SteamOS package refuses to install on the other release, and the Update Center picks the one for the release your Deck runs. - An app can opt in to leaving Steam Deck Game Mode for Desktop Mode before its private launch, and go back when the session ends or the launch fails. Off unless set per app. It needs SteamOS Manager 26.4.1, which ships with SteamOS 3.9; on SteamOS 3.8 an opted-in launch is refused before anything changes. It reads SteamOS Manager from SteamOS's own package database, waits until the new desktop is really there before launching, refuses a private Steam that already quit, and stops the stream's media before a Close from the console returns the Deck to Game Mode. See the SteamOS guide. (#792)
- For a Steam game with several launch options, Mission Control and Nova's launch settings say Steam may ask which version to start, so the question doesn't catch you mid-stream. If it asks, choose one in the stream. Polaris doesn't pick for you or change your Steam settings.
Fedora 45 and the guided install
- Fedora 45 gets its own package,
Polaris-fedora45-x86_64.rpm, and its own DRM/KMS helper, built against Fedora 45. Fedora 44 keeps its own pair. They aren't interchangeable, so install the one for the release your host runs, whichVERSION_IDin/etc/os-releasenames. - Fedora 44 and 45 are supported equally, and Fedora 44 has the longer history. The 1.5.0 streaming, benchmark and device testing ran on a Fedora 45 host.
- The Fedora RPMs attached to this release are signed with the same key as the package repository, the one whose fingerprint is on the repositories page.
- On Fedora 44 and 45, Arch and CachyOS,
curl -fsSL https://repo.papi-ux.com/install.sh | shadds the signed repository, installs Polaris and runs host setup. It runs four steps, signing key, repository, packages and host setup, and prints each command before it runs it, while what dnf, pacman and host setup print goes to a log only you can read. It checks the downloaded key against the pinned fingerprint before importing anything and writes the repository file itself. Another Fedora release stops before the key or the repository is touched. - One repository file serves both Fedora releases: dnf reads the Fedora 44 or 45 tree to match the host, and follows it from 44 to 45.
- Before this release, on clean Fedora 44 and 45 installs, the guided install, pointed at a private copy of the repository, installed Polaris, started it and served the web console, and it refused unsigned and wrongly signed packages.
- The install guides, Quick start and Compatibility describe Fedora 44 and 45, and SteamOS 3.8 and 3.9, as this release ships them.
- Building from source, Polaris compiles against OpenSSL 4, which Fedora 45 ships.
Updates you approve on the host
- On an existing Fedora 44 or 45 RPM install, System → Update Center has Review update. It picks the newest Stable release, or the newest Stable, Beta or release candidate with Include beta releases on, labels which it is, and lists the exact packages and their checksums. It takes only the pair built for the Fedora release your host runs, refuses a downgrade and updates
polaris-kmsonly when it's already installed. - Before anything changes, it checks both packages' signatures against the public key Polaris ships, imports that key only when RPM doesn't already trust it, and installs with RPM's own signature checks left on. An unsigned package, or one signed by another key, stops the update.
- Install with host approval opens the operating system's administrator prompt on the host's desktop. The console never asks for a password. An update waits while a stream, a launch, a Space or other host work is running, and Polaris never ends a session to make room for one.
- Finish restarts Polaris when you choose it, and the page checks that the new version is the one running. A failed or interrupted update shows the versions actually installed and asks for a new review before trying again.
- Other hosts keep the guided install commands in Update Center.
Live Tuning, on and acting on lost frames
- Live Tuning is on by default now. It's on for new installs, and existing hosts get it once on upgrade. Heads up has how. It still changes only encoders that can take a new bitrate mid-stream.
- It reads the frames lost in each media report a client sends. It used to average each report with the 0% every control ping brought, ten a second, so it rarely cut for the loss Nova reports.
- It lowers the bitrate when loss rises over what the stream usually loses in two of three reports, each losing 3% of its frames or more, so one burst doesn't start it. It settles just under the bitrate the link carries and tries higher again after 8 reports, then about every 20.
- Loss that doesn't depend on the bitrate it learns and leaves alone, and bursty loss of that kind no longer drags a stream far down while it figures that out.
- When a link drops under a rate it was holding, Live Tuning stops trusting the rates the old link carried and climbs back from the new one a judged step at a time, instead of jumping straight back to where it was. At its floor, loss over a fifth of the frames that's clearly more than background is the link's: it holds the floor and climbs from there. A return to your bitrate that no report has judged yet is taken back if the reports stop for 2.5 seconds right after it.
- A single high round trip reading no longer cuts the stream. Live Tuning treats a sustained rise in round trip time as queue evidence and lowers the bitrate while checking whether it drains. A replay of the round trip times a Steam Deck's Wi-Fi background scan produces, about 83 ms for 5 seconds every five minutes, makes no cut.
- A change Live Tuning asks for reaches the encoder after the next frame, instead of waiting up to 30 frames, which at a low frame rate could take seconds.
- While Live Tuning is on and your encoder can change its rate during a stream, Doctor takes no bitrate step of its own for sustained loss. It measures again and says what Live Tuning found, points at the Wi-Fi link for loss a lower bitrate doesn't help, and says when loss is too light for Live Tuning to cut.
- With Live Tuning on, a Linux host using NVENC can raise FEC for a Nova stream that reports partly lost frames, lowering the video bitrate to keep video and parity inside what Nova asked for. Now that Live Tuning is on by default, so is this; other streams keep the FEC you configured.
PyroWave gets the bits it needs
It's a hungry codec. Now the host knows how hungry.
- Polaris carries the bitrate model PyroWave's author published. For a TV or monitor it aims for what the author calls good quality, and for the device's own screen a lower target, matched to what looked right on a Retroid Pocket 6. At 1920x1080 and 60 fps in 4:2:0 that's about 101 Mbps on the device's own screen and 246 on a TV or monitor (109 and 298 in 4:4:4), at the default 10% FEC with stereo audio.
- When a PyroWave stream runs more than a tenth below the lower of those figures and the network is clean, Doctor offers to raise it in guarded steps, with Undo. Apart from Live Tuning lifting a request below
adaptive_bitrate_min(2 Mbps by default) to that floor, it's the only thing that goes above the bitrate you asked for, and never past 300 Mbps or yourmax_bitrate. With Live Tuning on (the default from 1.5.0), Doctor says what to set instead. This is the clean-network PyroWave quality raise, not a response to sustained loss. - Doctor quotes one figure: the bitrate to set in your client, FEC and audio included. With Live Tuning on it names the live bitrate instead, a little lower, because a live change skips the FEC and audio. Control on the Retroid Pocket 6 at 1920x1080, 120 fps and 4:4:4 looked right at 200 Mbps. The figure there is 215, so 200 reads healthy.
- Where 300 Mbps or your
max_bitrateis less than PyroWave asks, as at 3840x2160 and 120 fps in 4:4:4 on the device's own screen, and most frames still fill the codec's byte budget, Doctor says so and suggests a lower resolution or frame rate, or HEVC. If only Doctor's 300 stands in the way, it adds that you can set more yourself. - Polaris takes a bitrate you set yourself up to 500 Mbps now, up from 300, and tells your client it does. Doctor's raise, and anything else Polaris recommends on its own, still stops at 300.
- The Stability preset, a device profile and a saved paired profile stop capping a PyroWave request to H.264 sizes. Only
max_bitratedoes, and the log names any cap that applied. - Live Tuning stops at half the advice, and Doctor suggests HEVC or a lower mode from there.
- Nova's own PyroWave advice uses the same handheld target. Its notes have the figures, and its automatic suggestions stay at or below 300 Mbps. This is advice for that picture and link, not a promise that Wi-Fi can carry it.
- A client can see how your bitrate splits on any codec, not just PyroWave: what you asked for, any cap the host put on it, what the encoder gets, what it runs at right now, and the audio and FEC around it. PyroWave advice asked for during a stream counts that stream's own audio too, so 5.1 asks a little more than stereo.
Evidence before guesses
- Before a stream, Fix My Stream shows the host's own configuration findings: a saved KMS capture a Private Stream sets aside, a configured mode this host can't enter and why, and the last stream's capture findings marked unverified until the next one.
- Doctor leads with what's happening and what to try, in plain words, with one button, and keeps its evidence and confidence a level down. Nova shows the same words, because they come from the host.
- Doctor shows the mode the running stream really uses, with the host default named separately, so a per-game Mirror Desktop no longer reads as Private Stream. Its pacing advice stops telling everyone to turn VRR off and asks about the game's frame cap and capture timing first. On Game Mode it reports the compositor's adaptive-sync feedback as an aged observation, not a current state.
- When the host's encoder check can't start NVENC and picks the CPU encoder, Mission Control and Doctor & Support say NVENC is unavailable on this GPU with this build, so video is encoded on the CPU before a stream, with the host's reason beside it and a pointer to the NVIDIA driver and package variant. It appears only for a confirmed NVENC-to-CPU fallback, and it doesn't change which encoder is picked.
- Doctor stops guessing Tailscale from an address. A Tailscale peer readout asks your local tailscaled whether the connected client is a peer, and whether its control connection is direct, through DERP or through a peer relay. Nova for Android shows the same reading. It describes the control connection, not where video and audio go.
- Stream stats and Doctor's advanced evidence keep a short history of Live Tuning's decisions, what the encoder confirmed, and the client's media report intervals and cadence, so a change that reverses between polls is still visible.
- Mission Control's frame-health reading names what it measures against: the frame interval you asked for, or, on a source-paced stream, the encoder's handoff against the game's own frame intervals. When the host has no current timing evidence it says so instead of showing a number. Live Tuning says it saw frame timing vary instead of calling the stream stable. None of these readings claim VRR on the client's display.
Turned away up front, with a reason
A stream that can't work shouldn't connect and then show you nothing.
- Host Virtual Display no longer looks available on GNOME Wayland just because EVDI can add a connector. Polaris also checks that it can capture that exact screen. A forced or stale choice is turned away with the reason before adding a display. Use Mirror Desktop for the existing GNOME desktop, or Private Stream for an app on its own screen. GNOME virtual-screen streaming is not added in this release.
- When Host Virtual Display can't run because Polaris isn't connected to a Wayland desktop, the reason says so, names what usually causes it, like headless boot or an X11 session, and asks for a Plasma or Hyprland Wayland login, instead of asking for a connector. Reported in discussion #813.
- On a KDE desktop in HDR with
capture = kms, PyroWave used to connect and carry nothing, because it can't read the sixteen bit float KWin scans out. Now the host refuses it before the stream, and tells a client that names its codec at launch what to do instead. Private Stream captures its own session, so it keeps offering PyroWave. capture = nvfbcrefuses PyroWave by name too, and so does a second stream that would share the host's one capture with another codec, which used to get no picture.- HDR Gamescope Stream on a stock gamescope that can only send 8-bit video ends that attempt with an HDR-unavailable reason instead of retrying, never quietly falls back to SDR, and leaves other viewers of the same capture streaming. Thanks to Jailoris for the report in #806.
- A client that leaves during video setup, like one whose GPU can't run PyroWave, gets named: for fifteen minutes Doctor and the support report lead with the failed start and a next step, not two
Initial Ping Timeouterrors.
No more falling back in silence
- When a stream mode or host rule sets your capture backend aside, the log says which mode, what you chose and for how long.
- The System page has a Capture row under Host Now: where DRM/KMS capture stands for the capture this host is really set to, and the one step still missing, with a Copy button.
- Doctor's network-path check tells you what it tested. A check the host runs against itself covers local listeners and UDP hints, not the streaming device's loss, latency or bitrate ceiling. Missing client measurements stay unavailable; another stream's readings are not a clean bill of health for yours.
- Settings > Encoder Profiles has PyroWave and 4:4:4 rows: whether this host can stream PyroWave, why not when it can't and which launches it turns away, the advice and what it assumes while a PyroWave stream runs, and which encoder here gives you 4:4:4.
- A settings file Polaris won't read says why, in the log and the console, with the fix. Settings used to sit on its loading placeholder.
Games from Epic's Linux Preview
- Library can import games you've finished installing with Epic's official Linux Preview launcher. They launch in Mirror Desktop through the launcher you already opened and signed in to on the host desktop. Epic still handles installs, updates, Proton and cloud saves.
- A game you already imported through Heroic stays put. When Polaris can verify it's the same title, the scan shows one entry with Use Epic Launcher or Use Heroic, and switching keeps its artwork, history and settings. Polaris never switches it for you.
- In Mirror Desktop, these games keep running unless you say otherwise. Disconnect and Resume in your client keep the game running, and End Session ends the stream and leaves the game open.
- In Mission Control, signed in to the host's web console, you can choose Allow close on End Session and confirm it for the exact game Polaris sees. End Session then asks that game to close. Turn off close on End takes it back, and a new or restarted game needs a new confirmation. Polaris never assumes a game is its to close, and never closes the Epic launcher or other games. If it can't verify the game or confirm that it quit, close it on the host.
- Private Stream can run these games too, on a host with labwc, when you choose it for the game. Open Epic on the host desktop once so Polaris can recognise its launcher, then quit Epic; Polaris starts it inside the private session. Play a game once in Mirror Desktop before its first Private Stream. End closes the whole private session, Epic and any game started in it, and nothing outside it. Imported games still start in Mirror Desktop until you change them. The Epic guide has the steps and what refuses.
- Another AppImage running on the host keeps a Private Stream launch from starting, because Polaris can't tell it apart from Epic. When there's exactly one, Mission Control, signed in on the host's console, names it, like
example.AppImage (an AppImage) is running; quit it to use Private Stream. A client gets the general reason, and the host log never records the name. - Library → Import Games has an Epic Private Stream setup checklist, even before any Epic games are found. It keeps what the last scan saw with Epic open apart from what it can check right now. Prerequisite support is unknown, so a selected title is never labelled ready. A line it can't check says Can't check rather than guessing. The checklist launches nothing and changes no imports; Polaris checks again when you launch.
- Game Mode, Host Virtual Display, Spaces and native Linux Epic games aren't supported yet, and neither is Epic's Flathub package. I'm aiming for 1.5.1 with Flathub, but I'm not promising it.
Spaces, out of preview
- Spaces shows up as a full feature now, in the console, the docs and Nova. It's still one Space at a time, and the Spaces guide says plainly what's left.
- First Space setup on an NVIDIA host offers your NVIDIA cards for the runtime that borrows this PC's driver. It offered none, so setup stopped at choosing a graphics card. (#807)
- A Space launch turned away for its settings names the one to change, like HDR, the encoder, the bitrate or the audio channels. When stream setup asks a Space for something it can't carry, the host log says what didn't match, and it notes when a Space caps the bitrate you asked for. Space limits, 8 Mbps included, are unchanged. (#809)
- On a Docker host that uses AppArmor, such as a typical Ubuntu install, Host Setup no longer calls Spaces security ready, and a Steam Space launch is refused before the Space starts. Polaris has no verified AppArmor support for Steam Spaces yet. Keep AppArmor on, and don't run a Space privileged or unconfined. (#808)
- The first Space for a launcher works on Docker's containerd image store, the default on a fresh Docker 29, and a failed Space create names its cause in the host log.
Clearer for Moonlight players
- Moonlight players can opt in to Close Steam on the host to start games for each paired device. It is off by default, asks desktop Steam to quit before a private Steam launch, and refuses the launch if Steam does not finish closing. It leaves SteamOS Game Mode and unsaved game state alone. Nova for Android keeps asking the player at launch. (#797)
- Each app has a Launch as setting, so a Moonlight library can mix a private game, your real desktop and a desktop on a screen of its own. It replaces Mirror the host desktop and Always create Virtual Display, which did nothing on a Private Stream host and left you in an empty session. A mode the host can't run is greyed out, and a launch that needs it is turned away with the reason.
- Refusals Moonlight shows word for word name the setting to change, instead of sending you to Nova.
- Mission Control says whether each live stream is Nova or Moonlight / Artemis.
- Session Snapshot on Doctor & Support has a Client type tile, Nova or Moonlight / Artemis (the host can't tell those two apart), and for Moonlight or Artemis it says what that player can't use.
- The compatibility guide has one table of what each client gets, and what the host can set for a Moonlight player instead.
What a Nova client can read from the host
- A Nova client can read the host's own VRR record for its stream from the paired session status: whether it asked for source pacing, whether the host allows it, what the host is doing (
effective,pacing_modeand afallback_reason) and, once the host has recorded a pacing receipt for that stream,host_pacing. It is the record Doctor reads, served whether Doctor is on, collecting or off, and only ever that stream's own. Current Nova builds do not request VRR, so for them it reads as not requested. - Nova for Linux and Android can optionally pace decoded video by the host's frame times at the display's fixed refresh rate. That client setting is off by default and does not request source-paced VRR from Polaris. Current Nova builds do not request VRR. The host's separate Allow source-paced VRR (experimental) opt-in applies only to an eligible Private Stream whose client asks for VRR. Nova's own notes cover its side.
- The stream stats show how each client's own handshake split its bitrate request into video, FEC and audio, beside that stream, and never another stream's figures.
- A Nova client that reports which video packets reached it, and how its decoder was fed, gets a receipt that ties those frames to the exact encoder setting that produced them, or says why it can't. The host records these reports; by default nothing acts on them. Frames missing at the decoder are not network loss, and none of it changes Live Tuning, FEC, pacing or Doctor's verdict.
- A Nova client that is the only active owner of its session can ask the host for Doctor's optional AI explanation of the current reading, with one explicit request. The host says first whether it has a provider configured and whether that client may ask. The answer is plain text beside Doctor's own result and changes no setting or action; a host without a provider keeps the Doctor it had.
Experimental, off by default
- Allow source-paced VRR (experimental) under Audio/Video, Stream pacing. With it on, a client that asks for VRR on a Private Stream gets frames paced from the game's own clock when the capture route can prove its timing, and a fixed grid with a named reason when it can't. It covers H.264 and HEVC in SDR; AV1, HDR, PyroWave and the other stream modes keep fixed-rate pacing. Settings shows each client's requested and effective pacing. Nonary's VRR work in Moonlight is the design this follows.
- Host & Runtime has a Recording tab: Off, which is the default, Manual continuous, or a Replay buffer that keeps the last minutes of one stream in memory until a host admin saves it. Files are raw
.h264or.hevcvideo with no audio or container;ffmpeg -i clip.hevc -c copy clip.mkvwraps one in a container. Each paired device gets an Approve recordings for this device switch that is stored for later and changes nothing yet. - Wire pacing, with
wire_pacing = enabledinpolaris.conf, spaces each session's video packets at its negotiated bitrate timeswire_pacing_headroom(200% by default). - A native step-down trial for Live Tuning, off by default and turned on only by
adaptive_bitrate_native_downwardinpolaris.conf; Settings doesn't show it and the configuration API refuses it. With it on, a Nova client that reports which video packets reached it lets Live Tuning make one 15% step down, never below its floor, after a four-second reference at the current rate and eight seconds standing, and only after the stream, the writer and the encoder's own receipt are checked again. The lower rate is then held: nothing in those readings brings the rate back up or cuts it again, and they never stand in for loss, a clean link or capacity. Set a live bitrate yourself, or start a new stream, and ordinary tuning resumes. Live Tuning on by itself changes nothing here.
Fixed
Squashed.
- Saving one setting in Configuration no longer resets settings the page doesn't send, like your capture and compositor choices, and
polaris.confstays private to you (mode 0600) when it's saved or first created, the Nix modules and the installer launcher included. - On a fresh account, Polaris creates its folders private to you, and if a folder above them is writable by others, the login page says why and how to fix it instead of failing with HTTP 500.
- Anonymized diagnostics exports leave out your Linux username, file links included, and the sharing notice explains what it still can't take out. Headless KDE setup guidance tells a missing desktop login apart from headless boot, and an idle Host Virtual Display no longer warns about a missing output. Thanks to jokke009, whose setup in discussion #813 found these.
- On Bazzite and other ostree hosts,
sudo -H polaris --setup-host --enable-kmsadds you to thepolaris-kmsgroup, which lives in/usr/lib/groupthere, and names the command to finish if joining fails. Thanks to Jailoris for the report in #806. - A stream the host ends, because the game quit or someone pressed End, ends cleanly on the client instead of looking like a dropped connection, and the host stops reporting it as streaming while it tears down, so a client doesn't reconnect and start the game again.
- Polaris no longer crashes when the service stops during a launch.
- When a Space's worker can't start, the host log now says which check refused it, like a GPU or input device this account can't use, the Space's Docker volume or the exit code from
docker run, where it used to give two numbers. (#821) - During Desktop Takeover on Hyprland, your monitors leave the layout as well as powering off, so the pointer can't wander off the stream onto a dark monitor, and they come back the way they were. Thanks to Dimariqe for PR #799.
- Gamescope Stream no longer calls its own nested display not ready, and gives up after 30 seconds, because an app had connected to it through its socket path. Found while looking into #806.
polaris --versionprints the version and build features without reading your configuration first, and no longer rewrites the running service's crash record or calls it killed.- When a client's video falls behind, Polaris drops only the oldest queued frame instead of clearing the queue.
- Fuzzing the RTSP, control-stream and launch request parsers found a handful of malformed-input bugs, all fixed: a read past the end of an RTSP message, unchecked lengths on fixed-size control messages, a GCM input shorter than its tag, a numeric overflow, a leak on repeated RTSP headers, and a launch request with no app that kept going after it was refused.
- Release packages record their source commit in the version line Doctor and support bundles use; the published Fedora 1.4.13 package left it blank.
- Software centers like Discover and GNOME Software show this release's real date, taken from its release commit. Polaris packages used to call themselves 1990-01-01.
- A private launch waits for a virtual DualSense's controls to appear before it starts the game, instead of starting it with no controller. A pad whose controls never appear is reported.
- On a Private Stream, taps from a touchscreen client did nothing: the host said it took native touch and then dropped it. Polaris doesn't offer native touch there now, so your taps arrive as mouse input. Checked with Nova on a Retroid Pocket 6, where a tap on a game cover opened its page.
- Doctor calls a Steam Input conflict for the Polaris Xbox pad only when an Xbox pad is in use and every local Steam profile opts Xbox controllers in. A DualSense pad, which some Steam Controller clients get, now reads as something to watch, with the reason.
- On Nix, the game-host module no longer collides with nixpkgs' Polaris music server, builds without CUDA now carry the Vulkan headers and loader, a new configuration leaves the encoder on Auto and
streamMode = "labwc"seeds Private Stream, and the session helper no longer collides in Home Manager. The package reports its real version too, andgamescope-polarisbuilds on stable NixOS 26.05, with the Nix README naming the unfree packages to allow. Thanks to winterofhell, whose PR #811 found the module, Vulkan, default settings and helper problems. - A new game library copied from a read-only install, as on Nix, stays editable, so adding, editing and importing games saves. A library you already have is left as it is. Thanks to winterofhell, who found this in PR #811.
- The documented Nix flake install, with
?submodules=1, fetches and evaluates again. Granite's nested SPIRV-Tools pin pointed at a fork that no longer carried it, so Polaris now takes Granite from papi-ux/Granite, the same Granite with only that submodule address changed. Thanks to Elkiehirvi for the report in #814. - The Nix package drops its obsolete
pcredependency and keepspcre2, so it evaluates on nixpkgs revisions without legacy PCRE. Thanks to Elkiehirvi for PR #819. - The AI optimizer's per-game history no longer doubles its session and poor-outcome counts, and a healthy session it already judged clean no longer gets frame-rate issues added afterwards.
- The Ubuntu packages ship their post-install scripts as executable.
- An idle host says Waiting for a stream instead of Needs attention, and the post-session report labels captured quality as historical, blames no client by default, and shows nothing where it has no measurement.
- End Session no longer stalls the console: stream stats and the app list answer during teardown instead of waiting behind cleanup, and Library and Dashboard pause Launch and Stop while the running app is unknown.
- Ending a stream from Moonlight no longer times out after 30 seconds when the stream has its own private session. Polaris answers End first and then stops the session; until that cleanup finishes, the host says so and holds new launches back.
- An encoder that fails to start, like NVENC with no VRAM left, stops after a bounded run of attempts instead of retrying 99 times in eleven seconds while the client waits.
- GPU-native DMA-BUF capture keeps a buffer's lease alive while a conversion still uses it, and releases a lease the GPU queue refused for lack of memory instead of holding it until teardown.
- Gamescope cleanup inside a PID namespace, Spaces included, no longer reads a process group id of 1 as missing.
- Troubleshooting's Detect and Test rumble pick up a controller plugged in after the page opened and say why rumble is unavailable. Settings search takes Enter and Escape and opens the matching collapsed section.
- A huge client media timestamp gap no longer slips past the five-second coverage check and publishes loss evidence that had no coverage.
- The timing benchmark forgets raw samples thirty minutes after a run ends, lets a reconnected device start a new run instead of being blocked by its old one, and refuses a start for a session generation that's gone.
- From-source builds in a warm CMake tree pick up a new prepared FFmpeg pin instead of downloading the old archive and failing the hash check, and a tag or URL you typed yourself stays what you typed. (#791)
- With headless boot on, the Polaris service skips its desktop tray, so closing Desktop Mode no longer ends the host through the tray and makes the service restart.
- A SteamOS HEVC check that gets back video Polaris can't read no longer offers HEVC, and a failed HEVC check takes HDR HEVC with it.
- Doctor no longer counts Nova's PyroWave CPU call time as decode latency, or frames handed to the screen as frames shown. Those readings stay unavailable, including from older Nova builds, and Doctor needs two windows that both have them before it judges a stream or offers a change.
- Desktop Takeover on Hyprland supports the Lua dispatcher interface and restores monitor power even when the desktop has no windows to move. The existing special-workspace safety checks stay in place. (#783)
- With HEVC or AV1 set to Auto, Nova now sees the codecs Polaris detected as available. The paired capability list used the Auto setting itself instead of the encoder result, so a working codec could appear Unavailable before launch. A codec that is disabled or fails its encoder check remains unavailable.
- If End game cannot finish cleaning up a Host Virtual Display session, Polaris keeps its virtual screen and session owner available for another End attempt. Removing the screen first could move a surviving game to your physical monitor. This safeguard also keeps the session when screen removal fails; it does not make an unverified Heroic process safe to terminate. Private Stream keeps its existing shutdown route.
- The mouse lands where you point on a desktop with a rotated or scaled monitor, with wlroots capture, and with KMS capture when Wayland names every output KMS sees. Polaris measured your desktop by each monitor's resolution before rotation, so a 1920x1080 monitor turned to portrait counted as 1920 wide and 1080 tall instead of 1080 wide and 1920 tall, and the pointer landed off from where you aimed. It measures each monitor the way your compositor lays it out now, and on a HiDPI monitor the pointer still reaches every pixel. This applies when the monitor you stream is not itself rotated 90 or 270 degrees. Streaming a rotated monitor itself behaves as in 1.4.13: its picture looks as it did, usually sideways, and the pointer lands where it did, and a later fix will turn that picture upright. On other streams, touch and pen use the corrected desktop size too, but still leave out where the streamed monitor sits on your desktop. Thanks to ertywastaken, who tracked down the cause (#793).
- Streaming a monitor that sits right of or below another puts the pointer on that monitor, not on the one in the corner of your desktop. This is for wlroots, KMS and X11 capture, NvFBC included. With wlroots or KMS, streaming a monitor rotated 90 or 270 degrees keeps its 1.4.13 input mapping. Portal and KWin capture work as before.
- Doctor holds its verdict. It graded the network one second at a time, so over Wi-Fi the same stream could read as under network pressure and as fine a few seconds apart. It now judges video frame loss and round trip time over the last 20 seconds, calls loss network pressure at 2% and clears it below 1%. Doctor, the Dashboard's Loss tile and chart, Fix My Stream and the post-session report quote that one figure: the share of video frames that never arrived whole after FEC. With Live Tuning on and loss at that level, Doctor measures again and says what Live Tuning found, and takes no bitrate step of its own.
- Gamescope Stream starts again on the gamescope your system ships, SteamOS's included. Since 1.4.12 Polaris asked gamescope to draw the pointer into the stream with an option only Polaris's own gamescope build has, and a stock gamescope quit on it, so every launch failed. Polaris now checks first and leaves the option out when your gamescope doesn't have it. Those streams show no pointer, as before 1.4.12. On 1.4.12 and 1.4.13, add
Environment=POLARIS_GAMESCOPE_COMPOSITE_CURSOR=0under[Service]withsystemctl --user edit polarisand restart the service. sudo -H polaris --setup-host --enable-kmsno longer leaves the service unable to start until your next login: it waits for that login, says so, and a second run finishes the job.- Doctor and the Update Center stop calling the
polaris-kmshelper a stale copy, and with betas on and nothing newer out, the Update Center says so. - On Fedora, removing only
polaris-kmskeeps your Spaces setup. The helper ran the main package's removal step, and every update printed the install message twice. On 1.4.13, update before you remove the helper. - The Ubuntu package depends on PipeWire's client library now. Without it, on a minimal Ubuntu 24.04, every
polariscommand stopped. On 1.4.13,sudo apt install libpipewire-0.3-0t64fixes it. - NVENC with
nvenc_vbv_increaseat 258% or more no longer overflows its buffer at 500 Mbps. - Polaris removes the filler AMD drivers add to H.264 and HEVC at constant bitrate, rather than sending padding the client throws away. In the earlier RX 7900 XTX encoder-output tests, a synthetic still screen at 1080p60 fell from 20 Mbps to about 0.04 Mbps with identical decoded pictures. That was a test of driver output, not a live game-stream measurement or a promise for every AMD card.
- Clients on Tailscale, WireGuard or another tunnel with no MAC of its own now learn the host's MAC for Wake-on-LAN. Whether a magic packet from outside reaches a sleeping host still depends on your network.
- Private Stream asks the game's owned windows to close before stopping its display, then waits before escalating to process termination. An already-open desktop app is not signalled. This keeps the existing private-session route; it is not a guarantee that every launcher can close its game cleanly.
- Desktop Takeover on Hyprland no longer hands hyprctl a special workspace name it would read as a different request, like one holding
/--batch. That workspace stays where it is, and the host log says why.
Shipped in 1.4.13, announced now
Its notes forgot these. Sorry about that!
- Peers in the shared
100.64.0.0/10range, Tailscale's included, get the WAN policy: a LAN-only web console or Browser Stream refuses them, and streaming useswan_encryption_mode. Pairings are kept. - Heroic finds installed Amazon and sideloaded games, and earlier Heroic imports report their platform and runtime without a re-import.
- Doctor & Support has a Spaces checks section, collapsed until you open it, and Mission Control shows running Space sessions.
- Arch and SteamOS releases carry matching debug packages.
Known limits
Here's what isn't proven yet, in plain words.
- Source-paced VRR, Nova's pacing by host frame times and Leave Game Mode Before Launch are default-off opt-ins with limited hands-on checks, not wide testing. Turn them on to help test, and expect a named fallback.
- Source-paced VRR works only on Private Stream with labwc, for H.264 and HEVC in SDR. On a VRR monitor, VRR switched on and the stream played with no frames discarded at the display, but whether the frames you see follow the game's own timing hasn't been measured frame by frame yet: the tool that measures it isn't precise enough so far. I'm aiming for 1.5.1 with that check, but I'm not promising it. Until it passes, treat source-paced VRR as a test feature.
- The VRR record a Nova client can read says what the host asked for and did; it is not evidence of what the client's display showed, and current Nova builds send no VRR request. Nova's pacing by host frame times keeps the display at its fixed refresh rate and is separate from a VRR request. It was checked on fixed-refresh screens, a Steam Deck and a Retroid Pocket 6, where Nova paced each stream by the host's frame times. What's still open is the cadence check on a VRR display, above, which moved to 1.5.1.
- Live Tuning's loss handling passes 22 of the 26 cases on its replay bench. A link that shrinks while the client's media reports pause can go unnoticed without fresh congestion evidence; those are the four cases it misses. Its policy tests pass on this build, including replays of real Retroid Pocket 6 and Steam Deck streams. In simulation, with 1% to 2.9% of frames lost at any bitrate, a stream spends about 1% of its time or less below half its bitrate and never reaches its floor.
- On a Retroid Pocket 6 over a shaped link, with Live Tuning on, a stream rode out random loss at the bitrate it asked for after a short learning stretch, held an 8 Mbit/s cap with its reports flowing where Live Tuning off lost nearly every frame, and after a drop from 15 to 6.5 Mbit/s no longer jumped back over the new link. Two things from those runs are still open: the learning stretch at the start of a stream once kept it under half its bitrate for about 25 seconds, and after a big drop it once held its floor for about a minute and a half while repeated keyframes kept the link nearly full. I'd like to fix both in 1.5.1, but that's not a promise.
- Whether round trip time shows a queue on a real Wi-Fi link hasn't been measured. Moonlight and Artemis send no media reports, so Live Tuning can't see their lost frames; it still reacts to round trip time.
- With Live Tuning on, a Linux host using NVENC can try more FEC for a single stream when the client sends fresh media reports and feedback about partially lost frames, as Nova does, and the encoder can change bitrate in place. The raise and restore were checked on a Retroid Pocket 6; whether they reduce lost frames hasn't been measured.
- Wire pacing, on a clean Wi-Fi link to a Retroid Pocket 6 at 30 Mbps with the default headroom, spread each frame's packets over about 3.7 ms at the host, with no measurable change in video frame loss. Its effect on end-to-end delay hasn't been measured.
- The native step-down trial is checked in the host's own tests. One downward response was observed in a scoped Retroid Pocket 6 test; full device qualification and any delivery-quality benefit remain unconfirmed.
- For Leave Game Mode, checks on a docked Steam Deck OLED on SteamOS 3.9.2 covered an opted-in launch from Moonlight on a PC, five minutes of picture, sound and controls, reconnects, an End that returned the Deck to Game Mode without a manual switch, and a failed launch that returned it too. The picture, sound, controls and reconnect checks ran on an earlier build than the End check. The observed streams ran H.264 at about 60 fps; HEVC, 120 fps and HDR on the Deck, and other devices, are not checked.
- On the Steam Deck tested as a host, Polaris offered H.264 only. Making HEVC work there is still open.
- Recording is host only: raw video, no audio or timestamps, 128 MiB or 32,768 packets per replay buffer, and a buffer that empties when its first keyframe expires with no later one. Playback is not qualified.
- The Tailscale peer readout describes the control connection and the stream's matching peer; it doesn't verify where video and audio travel. Its direct, relay and split-tunnel cases haven't been tried on real networks yet.
- The console's phone and tablet layout was checked in a browser emulating those screens.
- Heroic games on Host Virtual Display still have an unresolved shutdown limitation: Polaris may not be able to prove which game processes it can stop. The display and owner are kept when cleanup is unconfirmed, so you can close the game yourself and try End game again. An accepted End game request is not proof that the game quit. Private Stream remains the recommended default; this update does not switch an existing host's chosen mode.
- In testing, the
polaris-kmscapture helper crashed once while a Private Stream was stopping. The cause is still being investigated. - The PyroWave advice is an objective metric on four game clips. The device's own screen figure is matched to one check on a Retroid Pocket 6, the TV figure hasn't been checked on a big screen yet, and Doctor's 300 Mbps ceiling may move.
- Epic games in Mirror Desktop were checked hands-on with one game on one host: launching it, saving its entry and cover, Disconnect and Resume, and an End that closed the game and left Epic open. In Private Stream, one game streamed to a Retroid Pocket 6 with controller isolation on: it launched, controller input reached it, and End closed the whole private session and left nothing behind. Keyboard input, play past the game's opening screens, saves and cloud sync, Disconnect and Resume in Private Stream, and Epic's AppImage build in a private session haven't been checked.
- Epic games in Private Stream need Polaris to see Epic open on the host desktop once after every Polaris restart or Epic update. With controller isolation on, Epic can't update itself inside the private session: an update there is likely to end the launcher and leave the stream black until End, so let Epic update on the desktop first. The setup checklist's line for whether Epic is closed reads Can't check even when it is, because the host only looks when you launch.
- Host-approved updates cover an existing Fedora 44 or 45 RPM install. Other hosts, such as Arch, CachyOS, Ubuntu, Bazzite and SteamOS, keep their guided instructions. Stable and Beta update packages come from the official GitHub release. The installed Review, approval and Finish journey runs for real only once a release is published, so it hasn't been checked end to end on a host yet. Fedora 45 has no earlier package to update from, so its first update there is the release after this one.
- The ostree group fix for
--enable-kmsis checked in tests, not yet on a Bazzite install.
Heads up before you update
Here's what changes under you.
- Games you imported from Steam, Lutris, Heroic or a ROM folder had Always create Virtual Display on without you setting it. They're Host default now, and so is any app with a Steam app id, so on a host whose mode isn't Private Stream they follow that mode instead of getting a virtual display. Set Launch as to Host Virtual Display on any that should keep one.
- On AMD, Auto now tries Vulkan Video first on Gamescope Stream through the portal. A historical report on an RX 9070 XT at 4K60 measured host processing latency of 9 ms with Vulkan Video and 16 ms with VA-API. These are that tester's readings, not a new benchmark or an encoder-only measurement. It costs AV1 and HDR there, and a client that picked AV1 fails as it starts when its launch switches into Gamescope Stream from another mode.
encoder = vaapiorav1_mode = 2keeps VA-API. capture = kwinnow captures through the portal, andcapture = drmthrough KMS. Both used to take whatever the automatic check found.adaptive_bitrate_maxlimits nothing now. With Live Tuning on, its 100 Mbps default cut every stream encoding above that for good, PyroWave included. It still loads, with a warning: move a cap you relied on tomax_bitrate, which now caps live changes too.- A live bitrate set by hand turns Live Tuning off for that stream only, not for every stream after.
- Live Tuning is on by default from 1.5.0. Older releases saved its Off default into
polaris.conf, so the first start after upgrading turns a saved Off on once, says so in the log and records thelive_tuning_on_by_defaultmigration insettings_migrations.jsonbeside the settings file. This also turns on a host that chose Off on purpose before 1.5.0: turn it off again after the upgrade, in Quick Controls or Audio/Video settings, and later starts keep it off. A config that already setsadaptive_bitrate_enabled = enabledstays on. An unreadable migration record changes nothing, and a settings file the store refuses is tried again at the next start. - The bitrate in your client includes FEC, audio and packet overhead; the encoder's live video rate does not. Nova uses the host's split to convert between them when it is known. If the split is unavailable, the UI keeps the available video or unknown units instead of inventing a request. For example, a 500 Mbps request at the default 10% FEC with stereo audio leaves about 449 Mbps for video. A raw live-bitrate API write uses video units, so it is not the same number.
- Every package builds Polaris with link time optimisation again, as before 1.4.13. If one misbehaves where 1.4.13 didn't, just hit me up in Discussions or on Matrix.
- Upgrading Fedora 44 to 45? A repository file fetched or written before 1.5.0 names the Fedora 44 tree only. Before you upgrade Fedora, run the one-command install again, or fetch the repository file again as the repositories page shows, so dnf follows the host to Fedora 45.
- On Nix, the overlay now follows your host's
cudaSupport, which nixpkgs leaves off. An NVIDIA host that relied on the CUDA build setsnixpkgs.config.cudaSupport = true. An existingpolaris.confis left alone, so an olderencoder = nvencstays until you change it. The Nix README has the details. - Building from source, Granite now comes from papi-ux/Granite. An existing checkout fetches from the old address until you run
git submodule sync --recursive, updatethird-party/Granite, and sync again before the recursive update; a fresh clone needs nothing extra. Packages are unaffected. - Ran 1.4.14-beta.1 or 1.5.0-beta.2? 1.5.0 replaces a beta in an ordinary upgrade, because betas sort below their release (
1.5.0~beta.2in RPM and DEB,1.5.0beta.2in pacman).polaris-kmsneeds its exact Polaris: install both files in one command. New since beta.2: Fedora 45 packages and the guided install for Fedora 44 and 45, host-approved updates, Epic's Linux Preview games, Live Tuning on by default with its redesign, the live session card, plainer Doctor, what a Nova client can read from the host, the Steam launch option notice, the Spaces fixes, and Fixed from its first bullet down to the Ubuntu post-install scripts.
Thank you
A lot of what's above started with one of you, a PR, a bug report, a log or a test run, so here's everyone in one place. Thank you, all of you!
Code
- coreydeli: AMD encoders that stop sending filler (#785), Close Steam on the host to start games for Moonlight players (#797), the Where games run hints (#804) and the Host Virtual Display measurement scripts (#805).
- Dimariqe: Desktop Takeover on a Hyprland with a Lua config (#783), and monitors that leave the layout during a takeover (#799).
- Elkiehirvi: the Nix package without its obsolete
pcredependency (#819). - winterofhell: the Nix module, Vulkan, default settings and helper fixes, and the read-only library find (#811).
Reports and testing
- CarlosSouza: the RX 9070 XT readings behind Auto trying Vulkan Video first on AMD (#635).
- Elkiehirvi: the Nix flake install that couldn't fetch its SPIRV-Tools pin (#814).
- ericeslinger: the first-run 503 that became a settings file that says why it can't be read (#782), and Host Virtual Display on GNOME (#796).
- ertywastaken: tracked down why the pointer missed on a rotated or scaled monitor (#793).
- FabianZettl: the per-app virtual display a Private Stream host threw away, which became Launch as (#790), and the FFmpeg pin that failed its hash check (#791).
- Jailoris: Gamescope Stream on Bazzite, HDR on a stock gamescope and the
polaris-kmsgroup on ostree, with logs and probes (#806). - jokke009: a headless KDE host, which led to clearer setup guidance, the Host Virtual Display session reason and the username fix in support exports (discussion #813).
- ruun3r: Spaces on AMD and Docker's containerd image store, with two full reinstalls and the
docker image lsthat pointed at the fix (#664). - todiadiyatmo: the pre-launch hook request that became Leave Game Mode Before Launch (#792).
- TonicArtos: the Space that wouldn't start and logged only two numbers, which led to refusals that now name their check (#821).
- zmarty: first Space setup on NVIDIA, Steam Spaces under AppArmor on Ubuntu, and a Space's quality settings (#807, #808, #809).
Built on
- Apollo and Sunshine, the host Polaris grew from.
- Granite by Themaister, which Polaris now builds from papi-ux/Granite with only one submodule address changed.
- moonlight-common-c from the Moonlight project, through Apollo's fork, the protocol under every stream.
- Nonary's VRR work on moonlight-qt, the design source-paced VRR follows.
- PyroWave and the bitrate model its author published, by Themaister.
Install (Fedora 44 and 45, Arch / CachyOS, Ubuntu 24.04, SteamOS 3.8 and 3.9)
Already added repo.papi-ux.com? Updating is sudo dnf upgrade on Fedora or sudo pacman -Syu on Arch, then restart Polaris. On Fedora 44 and 45, Arch or CachyOS, curl -fsSL https://repo.papi-ux.com/install.sh | sh adds the repository, installs Polaris and runs host setup in one go. The repository publishes on a schedule, so for a few hours after a release it can still serve the previous one. To install by hand instead:
Fedora 44
wget --output-document=./Polaris-fedora44-x86_64.rpm https://github.com/papi-ux/polaris/releases/download/v1.5.0-rc.1/Polaris-fedora44-x86_64.rpm &&
sudo dnf install "./Polaris-fedora44-x86_64.rpm" &&
sudo -H polaris --setup-host &&
systemctl --user restart polarisFedora 45
wget --output-document=./Polaris-fedora45-x86_64.rpm https://github.com/papi-ux/polaris/releases/download/v1.5.0-rc.1/Polaris-fedora45-x86_64.rpm &&
sudo dnf install "./Polaris-fedora45-x86_64.rpm" &&
sudo -H polaris --setup-host &&
systemctl --user restart polarisArch Linux / CachyOS
wget --output-document=./Polaris-arch-x86_64.pkg.tar.zst https://github.com/papi-ux/polaris/releases/download/v1.5.0-rc.1/Polaris-arch-x86_64.pkg.tar.zst &&
sudo pacman -U ./Polaris-arch-x86_64.pkg.tar.zst &&
sudo -H polaris --setup-host &&
systemctl --user restart polarisUbuntu 24.04
wget --output-document=./Polaris-ubuntu24.04-x86_64.deb https://github.com/papi-ux/polaris/releases/download/v1.5.0-rc.1/Polaris-ubuntu24.04-x86_64.deb &&
sudo apt install ./Polaris-ubuntu24.04-x86_64.deb &&
sudo -H polaris --setup-host &&
systemctl --user restart polarisSteamOS 3.8
Run this in Desktop Mode. It sets up the package keyring when needed and restores the read-only root before starting Polaris.
wget --output-document=./Polaris-steamos3.8-x86_64.pkg.tar.zst https://github.com/papi-ux/polaris/releases/download/v1.5.0-rc.1/Polaris-steamos3.8-x86_64.pkg.tar.zst &&
(
set -e
trap 'sudo steamos-readonly enable' EXIT
sudo steamos-readonly disable || exit $?
sudo pacman-key --init || exit $?
sudo pacman-key --populate || exit $?
sudo pacman -Sy || exit $?
sudo pacman -U ./Polaris-steamos3.8-x86_64.pkg.tar.zst || exit $?
sudo -H polaris --setup-host --enable-headless-boot || exit $?
sudo steamos-readonly enable || exit $?
trap - EXIT
) &&
systemctl --user enable --now polarisSteamOS 3.9
The same steps with the 3.9 package. Install the package for the release your Deck runs, which VERSION_ID in /etc/os-release names.
wget --output-document=./Polaris-steamos3.9-x86_64.pkg.tar.zst https://github.com/papi-ux/polaris/releases/download/v1.5.0-rc.1/Polaris-steamos3.9-x86_64.pkg.tar.zst &&
(
set -e
trap 'sudo steamos-readonly enable' EXIT
sudo steamos-readonly disable || exit $?
sudo pacman-key --init || exit $?
sudo pacman-key --populate || exit $?
sudo pacman -Sy || exit $?
sudo pacman -U ./Polaris-steamos3.9-x86_64.pkg.tar.zst || exit $?
sudo -H polaris --setup-host --enable-headless-boot || exit $?
sudo steamos-readonly enable || exit $?
trap - EXIT
) &&
systemctl --user enable --now polarisBazzite users should follow the Bazzite guide and use the Fedora RPM through rpm-ostree. SteamOS 3.8 and 3.9 users should follow the SteamOS guide, which also covers keeping Polaris running in Game Mode.
Assets: Polaris-fedora44-x86_64.rpm · Polaris-fedora45-x86_64.rpm · Polaris-arch-x86_64.pkg.tar.zst · Polaris-ubuntu24.04-x86_64.deb · Polaris-steamos3.8-x86_64.pkg.tar.zst · Polaris-steamos3.9-x86_64.pkg.tar.zst
DRM/KMS capture, only if you use it: Polaris-kms-fedora44-x86_64.rpm · Polaris-kms-fedora45-x86_64.rpm · Polaris-kms-arch-x86_64.pkg.tar.zst · Polaris-kms-ubuntu24.04-x86_64.deb · Polaris-kms-steamos3.8-x86_64.pkg.tar.zst · Polaris-kms-steamos3.9-x86_64.pkg.tar.zst
Debug symbols, for crash reports: Polaris-debug-arch-x86_64.pkg.tar.zst · Polaris-debug-steamos3.8-x86_64.pkg.tar.zst · Polaris-debug-steamos3.9-x86_64.pkg.tar.zst