Eclipse

The screen-side app: everyday game streaming and two-host couch co-op on LG webOS, NVIDIA SHIELD, Windows and Linux.

Project Hub · Installation Guide · Eclipse · Umbra · Development · Acknowledgements

New here? The Project Hub explains the setup, co-op, hardware coverage and both applications. This repository owns Eclipse source and client release files. Eclipse descends from Moonlight, Moonlight TV and Aurora.

Downloads and installation

Open Eclipse releases, choose the latest compatible release and expand Assets. Download the attached package for your device—not GitHub’s generated Source code archives. If no release/package is listed, that platform’s installer has not been published.

Device	Asset to choose	Install
LG webOS TV	Standard com.aurora.gamestream_<version>_arm.ipk (not beta)	LG TV steps
Windows x64	Installer eclipse-windows-x64-setup-unsigned.exe (or portable eclipse-windows-x64-unsigned.zip) + checksum	Windows steps
Linux x86_64	Flatpak Eclipse-<version>-linux-x86_64.flatpak + checksum (the older tarball eclipse-linux-x86_64.tar.gz is still attached)	Linux steps
NVIDIA SHIELD TV	eclipse-android.apk + checksum	SHIELD steps

LG webOS

1. Follow LG’s Developer Mode setup on the TV.
2. Install webOS Dev Manager on your computer (on webOS 26, version 1.99.20 or newer) and connect the TV using its Developer Mode address/passphrase.
3. Download the standard Eclipse IPK above, choose Apps → Install in Dev Manager and select the file.
4. Launch Eclipse on the TV. Keep the Developer Mode session active; close/reopen Eclipse after updates.

Full LG installation and prerequisites. Physical testing: LG G5 on webOS 26; other models/versions need reports.

Windows x64

1. Download the installer and its matching SHA-256 file from the same release; compare with Get-FileHash .\eclipse-windows-x64-setup-unsigned.exe -Algorithm SHA256.
2. Run it as your normal Windows user. It installs Eclipse for your user only, without administrator access, adds Start menu entries and an uninstaller, and keeps settings and pairings when installed over an earlier version.
3. For portable use instead, extract eclipse-windows-x64-unsigned.zip with Extract All, keep every DLL/data folder together and run moonlight-tv.exe (the inherited executable name is expected).

Both packages are unsigned; check its provenance and checksum before responding to a Windows warning. Signing through SignPath Foundation is being set up: see the Code signing policy. Windows 11 is tested. The source minimum is Windows 10 version 1803, but its coverage is not equivalent. A compatible D3D11VA GPU/driver is required.

Full Windows installation.

Linux x86_64

The Flatpak is the Linux package from 1.3.6 on. It runs on any x86_64 distribution with Flatpak, on Wayland or X11, and uses the same Freedesktop runtime as Umbra for Linux.

1. Install Flatpak and add Flathub if you have not already (Ubuntu does not include Flatpak by default): sudo apt install flatpak, then flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo.
2. Download Eclipse-<version>-linux-x86_64.flatpak and its .sha256 into one folder and check it: sha256sum -c Eclipse-<version>-linux-x86_64.flatpak.sha256.
3. Install it for your user: flatpak install --user Eclipse-<version>-linux-x86_64.flatpak. Flatpak fetches the runtime and, on NVIDIA, the driver extension matching your installed driver.
4. Start Eclipse from the applications menu, or with flatpak run io.github.PreceptorOfMagic.Eclipse.

The Flatpak uses the tarball's settings folder (~/.local/share/com.limelight/moonlight-tv), so a PC that already runs the tarball keeps its paired hosts and settings. To update, install the newer bundle with --reinstall added; to remove it, flatpak uninstall --user io.github.PreceptorOfMagic.Eclipse (settings and pairings stay in that folder).

Tested on Ubuntu 26.04 with an AMD Radeon RX Vega (VA-API; GNOME, and KDE Plasma on Wayland and X11) and an NVIDIA RTX 2060 SUPER (NVDEC; GNOME), and installed and streamed on Ubuntu 26.04, Fedora 44, openSUSE Tumbleweed, Arch Linux and Debian 13 under WSL. Intel graphics are untested.

Older package: the Ubuntu-built tarball eclipse-linux-x86_64.tar.gz stays on each release. Extract it, enter eclipse-linux-x86_64 and run ./install.sh (or ./eclipse in place). It needs glibc 2.35+ (Ubuntu 22.04 baseline).

Full Linux installation.

NVIDIA SHIELD TV

1. Download the APK and its matching SHA-256 file from the same release.
2. Sideload it: with the Downloader app on the SHIELD (allow it under Settings → Device Preferences → Security & restrictions → Unknown sources), or from a computer with adb connect <SHIELD address>:5555 then adb install eclipse-android.apk.
3. Launch Eclipse from the SHIELD's apps row. Install updates the same way; your hosts and settings are kept.

Requires SHIELD Experience 8 or later. Tested on a 2019 SHIELD TV running SHIELD Experience 9 (Android 11) with streaming, two-PC co-op, the SHIELD remote and Xbox and Nintendo Switch Pro controllers. The other SHIELD models run the same software; reports are welcome. There is no Play Store listing.

Other Android TV and Google TV devices (Android 9 or newer) may run the same APK, but none has been tested and they are not supported: decoders, refresh-rate switching and remote input differ between devices. See the installation guide's risks before trying one.

SHIELD installation, remote keys and building.

What Eclipse provides

• Discover or add an Umbra host, complete PIN pairing and launch its games or desktop.
• Choose decoder-aware 720p, 1080p, 1440p, 3584×2016 “3.6K”, 4K, native or custom resolutions.
• Select frame rates from 30 to 240 fps where the active decoder permits them.
• Use automatic bitrate or a manual 5–400 Mbps selector; the negotiated protocol path may impose a lower effective limit.
• Use H.264 or HEVC on desktop targets, with capability-gated AV1 and HDR10 paths on compatible webOS hardware and HDR10 on the NVIDIA SHIELD where the TV supports it.
• Send gamepad, keyboard and mouse input, including supported rumble, trigger rumble, touchpad, gyro, accelerometer and RGB capabilities.
• Open the on-screen keyboard, use the gamepad virtual mouse and inspect live codec, size, frame rate, latency, drop and bitrate statistics.
• Hold Start on any controller for the shortcut wheel (stream menu, virtual mouse, keyboard, performance); the button combinations still work, and either can be turned off in Settings > Input.

First stream and co-op

1. Install Umbra on the gaming PC. Discover/add it in Eclipse and approve Eclipse’s PIN on the host.
2. Launch a normal game or desktop and verify picture, audio and input.
3. For co-op, install a compatible Umbra release on a second PC and test it individually.
4. Choose Co-op in Eclipse, select both PCs and layout, assign players/controllers and start. Matching host/client releases negotiate the encoder path; no manual Co-op Pane application or hidden encoder settings are part of setup.

Each PC runs its own game session. See the Project Hub for the full system map and current hardware matrix.

Reporting and contributing

Use Settings → About → Keep diagnostic logs, restart, reproduce the issue, then Share logs…. Follow the log-export instructions, review private details and attach the bundle to Eclipse issues. Include exact versions, hardware and whether a normal stream works.

Development and build entry points · Acknowledgements

Eclipse/Umbra licence & notices · GPL-3.0