Skip to content

SPLYT 0.3.0 — first public pre-release

Pre-release
Pre-release

Choose a tag to compare

@Shayammy1 Shayammy1 released this 08 Sep 17:02
· 24 commits to main since this release

Early and rough around the edges — the point of this build is to get it running on hardware I don't have, so please report what breaks.

What it does

SPLYT lets two people game at the same time on a single PC, each with their own screen and their own keyboard/mouse. It runs a full Windows VM on Hyper-V with GPU-P (GPU partitioning), so the VM gets real GPU acceleration while the host keeps using the same GPU in parallel — no "pick one" tradeoff like traditional passthrough.

Player 1 plays directly on the host. Player 2 plays in the VM, on a second screen plugged into the same GPU, using Sunshine/Moonlight locally for 100+ Hz and fully independent inputs.

It aims to be an all-in-one tool that a non-technical person can actually use: one-click VM creation (Secure Boot + vTPM for Windows 11), automatic GPU-P setup and driver preparation, Hyper-V auto-enable, and a few gaming-oriented tweaks.

Requirements

  • Windows 10 version 2004+ or Windows 11, x64
  • Pro / Enterprise / Education. Home works too, via an unofficial workaround SPLYT applies for you (not guaranteed on every build)
  • Hyper-V — SPLYT offers to install it for you on first launch
  • A GPU-P capable GPU (WDDM 2.9+ driver)

Install

Download SPLYT-Setup-0.3.0.exe below and run it. It's self-contained: no .NET or other prerequisite to install.

The installer isn't code-signed, so SmartScreen will warn you on first run ("More info" → "Run anyway"). That's expected for an unsigned solo project, not a sign that something is wrong — the full source is in this repo if you'd rather build it yourself.

Interface is available in English and French (asked on first launch).

Known state / what's most useful to report

GPU-P behaviour varies a lot by hardware, and that's where I need testers most. Two distinct GPU-P bugs on AMD integrated GPUs were found and fixed in the last few days purely from user reports:

  • driver files missing in the guest → GPU absent from Device Manager entirely
  • MMIO space too large → GPU present but in error (orange triangle / Code 43)

NVIDIA GeForce cards deliberately block GPU acceleration inside VMs. SPLYT includes an unofficial community patch for this, but it's based on byte patterns from 2020-2021 drivers and will most likely fail cleanly on a recent driver.

If something breaks, please open an issue with your CPU model, GPU model, Windows edition/version, and what happened. That's what makes these fixable.