Split-screen gaming never really died on consoles, but it quietly disappeared from most PC releases over the last decade. Publishers cut couch co-op to save development budget, and online-only multiplayer became the default even for games built around shared adventures. Nucleus Co-op fills that gap by launching multiple instances of a single-player or online-only game on one PC, routing a controller to each instance, and tiling the windows into a split-screen layout, with no native support required. As of October 2026 the project, associated with the NucleusFramework/Nucleus repository on GitHub, remains a free, open-source Windows tool, and version 3.0.0 development builds were published from October 7 through October 20, 2026 as pre-releases. This tutorial walks through the full install, handler configuration, controller assignment, and the specific problems that trip up first-time users, from anti-cheat bans to Steam login conflicts.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Nucleus Co-op Actually Does
Nucleus Co-op doesn’t patch a game or inject new code into it. It launches separate, sandboxed instances of the same executable, one per player, each with its own save folder, configuration files, and window. A companion system called a handler, which is a small game-specific script maintained by the community, tells Nucleus how many players a title supports, how to size and position each window, and how to route controller input so Gamepad 1 only ever touches Instance 1. For Steam games that check in with Valve’s servers even during local play, handlers often lean on local API emulation so each instance behaves like an independent local player without needing four separate Steam accounts logged in at once.
This is fundamentally different from Steam Remote Play Together, which streams a single running game over the internet to remote friends. Nucleus Co-op keeps everything local: every instance runs on the same PC, and every player is physically in the same room, typically split across quadrants of one monitor or spread across multiple displays. It’s also different from games that ship native split-screen, since Nucleus adds the feature to titles that were never built with it, using window management and input routing rather than in-engine code.
The project’s GitHub releases page lists Nucleus Co-op v2.4.2 as the latest build, shipped August 23, 2026, under the SplitScreen-Me/splitscreenme-nucleus repository. The official site describes it plainly as a free and open-source tool for Windows that “adds remarkably smooth split-screen functionality” to games that don’t support it out of the box. There is no Mac or Linux native build; Steam Deck users typically run it through a Windows compatibility layer or a separate desktop PC.
Why Native Split-Screen Disappeared From PC Gaming
It’s worth understanding why a tool like Nucleus Co-op needed to exist in the first place. Split-screen support isn’t hard to build technically, console games shipped it constantly through the 2000s and early 2010s, but it’s expensive to test and maintain across every engine change, and it rarely shows up in sales data the way a flashy single-player trailer or a battle pass does. As live-service and always-online models took over big chunks of the industry through the late 2010s and 2020s, local multiplayer modes were among the first things cut from scope, since matchmaking servers and online progression systems don’t require a second player physically in the room.
The result is a strange gap: games explicitly designed around cooperative play, extraction shooters, survival-crafting titles, horror co-op experiences, frequently ship with zero local multiplayer support, forcing everyone in a shared household onto separate accounts, separate PCs, or separate online sessions just to play together. Community tools filled that gap because publishers weren’t going to. Nucleus Co-op’s handler system essentially crowdsources the split-screen engineering that studios decided not to fund, one game at a time, which is also why coverage is uneven: popular co-op-focused titles get handlers fast, while niche or newly-released games can take weeks or months before someone builds and tests a working configuration.
Prerequisites and Requirements
Before downloading anything, confirm your hardware can handle running a game twice (or four times) simultaneously. Nucleus doesn’t render anything itself, it just manages windows and input, so every instance you add multiplies CPU, GPU, and RAM load almost linearly.
| Component | 2-Player Minimum | 3-4 Player Recommended |
|---|---|---|
| OS | Windows 10 64-bit | Windows 11 64-bit |
| CPU | 6-core / 12-thread (Ryzen 5, Core i5, recent gen) | 8-core / 16-thread or better |
| RAM | 16 GB | 32 GB |
| GPU | RTX 3060-class or equivalent | RTX 3080 / 4080-class or equivalent |
| Storage | SSD (NVMe preferred) | NVMe SSD, dedicated drive if possible |
| Controllers | 2 XInput controllers | 3-4 XInput controllers plus 1 keyboard/mouse |
| Display | 1440p or 4K monitor, or 2 monitors | Ultrawide or 2-4 separate monitors |
Each instance of a mid-2020s AAA title can eat 8-10 GB of RAM on its own, which is why 16 GB is a hard floor for two players and 32 GB becomes the practical minimum once you’re running three or four. Lighter games change the math considerably: Terraria, Left 4 Dead 2, and Minecraft Java Edition will run four instances comfortably on far less powerful hardware than Elden Ring or Grand Theft Auto V will tolerate at two. An SSD matters more than people expect here, since every instance streams the same assets independently, and a mechanical drive turns simultaneous load screens into a stutter-fest.
You’ll also need legitimate ownership of the game on Steam (or whichever launcher it’s on), because Nucleus Co-op is built for local co-op with games you already own, not for bypassing purchase requirements. Handler authors and the project’s own documentation are explicit that this tool is meant for offline or local multiplayer sessions, not for evading online DRM checks tied to matchmaking or ranked play.
Step 1: Download Nucleus Co-op
Go to the official GitHub releases page for the SplitScreen-Me/splitscreenme-nucleus repository and download the latest NucleusApp.zip asset (v2.4.2 as of this writing). Avoid third-party mirrors, forum reposts, or file lockers — the project is 100% free, so any site charging for the download or bundling extra installers is not the real thing.
# Example folder layout after extraction
C:\Games\NucleusCoop\
├── Nucleus.exe
├── handlers\
├── profiles\
├── saves\
└── logs\Step 2: Extract and Launch
Extract the ZIP into a dedicated folder outside your normal Downloads directory, something like C:\Games\NucleusCoop\ works well (the project’s own GitHub guidance has recommended extracting outside restricted folders since a June 2025 advisory, and the October 2026 setup documentation lists C:\NucleusCo-op as the standard install path), since the app needs write access for logs, profiles, and per-instance save folders. Run NucleusCoop.exe as administrator: as of the October 2026 setup guide, launching elevated is now the documented requirement rather than an optional step, since most handlers depend on elevated privileges for the window and input hooks that route controllers to the correct instance.
On first launch, Nucleus creates its internal folder structure: a handlers directory where game-specific scripts live, a profiles directory for per-player configuration, and a logs directory that becomes essential the first time something breaks. Windows Defender or your antivirus may flag the executable on first run since it hooks into window and input APIs, this is expected behavior for a tool that manages multiple simultaneous game windows, but you should still only trust it because you downloaded it from the official GitHub repo.
Step 3: Add Your First Game
Inside the Nucleus UI, use the “Add Game” option and point it at the game’s installation folder or executable. For Steam titles, Nucleus can often auto-detect the install path from your Steam library; for games from other launchers (Epic, GOG, Battle.net), you’ll browse to the executable manually. Before doing anything else, launch the game normally outside of Nucleus and confirm it runs without errors, this single step eliminates half of the “Nucleus isn’t working” troubleshooting threads, because a game that’s broken on its own will stay broken inside multiple instances.
Step 4: Check the Supported Games List First
Before configuring anything by hand, check the official supported games list, which documents more than 800 titles with pre-built handlers, player counts, source platform, and a rough difficulty rating. If your game is already on the list, Nucleus can usually fetch the matching handler automatically or link you straight to the download. If it isn’t listed, you can still attempt a manual handler, but expect more trial and error.
| Game | Players | Platform | Setup Difficulty |
|---|---|---|---|
| Halo: The Master Chief Collection | 2-4 | Steam | Easy |
| Left 4 Dead 2 | 2-4 | Steam | Easy |
| Borderlands 2 | 2-4 | Steam | Easy |
| Deep Rock Galactic | 2-4 | Steam | Easy |
| Risk of Rain 2 | 2-4 | Steam | Easy |
| Terraria | 2-4 | Steam | Easy |
| Lethal Company | 2-4 | Steam | Easy |
| Elden Ring | 2 | Steam | Medium |
| Grand Theft Auto V | 2 | Steam | Medium |
| Minecraft Java Edition | 2-4 | Launcher | Medium |
| Project Zomboid | 2-4 | Steam | Medium |
| Phasmophobia | 2-4 | Steam | Medium |
Titles marked “Easy” typically need nothing more than downloading the handler and setting player count. “Medium” titles often require extra steps like disabling a launcher’s overlay, forcing a specific Steam API version, or manually setting a shared save folder so progress carries between sessions. There’s also a curated Steam curator page that tracks which Steam titles currently have working handlers for the latest Nucleus release, which is worth bookmarking since handler compatibility shifts with game updates.
Step 5: Configure the Handler
Open the handler configuration screen for your chosen game and set the number of instances, typically 2, 3, or 4, based on what the supported games list recommends. Then choose a window layout: horizontal split (side by side), vertical split (stacked), or a 2×2 grid for four players. If you’re running more than two instances on a single monitor, drop the per-instance resolution proportionally (a 1440p display split four ways effectively gives each player a 720p window), or performance and readability both suffer.
# Typical handler settings for a 4-player split on a 1440p monitor
players: 4
layout: grid_2x2
resolution_per_instance: 1280x720
window_mode: borderless
input_lock: enabledIf the game runs through Steam, review the handler’s DRM options. Most handlers configure this automatically, using a local API emulation layer so each instance recognizes itself as a separate local player without needing four logged-in Steam accounts. You generally don’t need to touch this manually, but if a game refuses to launch a second instance, this is the first setting worth checking in the handler’s documentation.
Step 6: Assign Controllers Per Player
Plug in every controller before opening Nucleus or launching the game, devices added mid-session are the single most common cause of “my controller isn’t responding” complaints in community troubleshooting threads. In the Nucleus input settings, manually map Controller 1 to Player 1, Controller 2 to Player 2, and so on; the October 2026 setup documentation confirms this same workflow now extends to assigning input devices directly to separate screen sections (NucleusCoop.org describes assignment for 3 input types: controllers, keyboards, and mice), so a controller is tied to both a player slot and the window it should control. Enable input locking so each instance only reads from its assigned device; without it, one controller can end up steering two windows at once, which looks like a broken game but is actually an input-routing miss.
Standard XInput controllers (Xbox-style pads) have the most reliable support across handlers. If you’re mixing in a DirectInput device, an older PlayStation pad or a generic USB gamepad, consider running it through an XInput wrapper like x360ce for that specific instance, since mixed input types are a frequent source of dropped inputs. For a 3-4 player split, it’s common to dedicate one instance to keyboard and mouse while the rest use controllers; running multiple keyboard layouts simultaneously through Nucleus is technically possible but noticeably more fragile.
Step 7: Launch and Verify the Split
Click “Play” or “Start Split-Screen” inside Nucleus. The tool launches every configured instance, resizes and repositions each window according to your chosen layout, and applies the input mapping you set in Step 6. Give it a moment on the first run, multiple instances launching simultaneously puts a real spike on disk I/O, especially the first time shaders compile for each window.
Once every instance is up, most games still need you to manually connect them into a shared session through the game’s own menu: one instance hosts a local/LAN lobby, and the others join it, exactly as if four separate PCs were networked together. Nucleus creates the multiple instances and manages the windows and controllers; it does not touch the game’s own networking code, so the in-game “host game” / “join local game” flow still applies.
Step 8: Set Up Multi-Monitor Layouts (Optional)
If you have more than one display connected, Nucleus can assign a specific monitor to each instance rather than tiling everything onto a single screen. This produces a noticeably better experience for 3-4 player sessions, since each player gets a full-resolution window instead of a quarter of one shared display. In the handler’s window settings, look for a monitor index or display assignment field and match it to your Windows display arrangement (checked under Settings > System > Display).
Ultrawide monitor owners have a middle-ground option: a 2×1 or 3×1 horizontal split across a 21:9 or 32:9 panel avoids the aspect-ratio squeeze that a 2×2 grid produces on a standard 16:9 display, since each window gets a wider native shape closer to what the game expects.
Step 9: Handle Shared Saves and Progression
Each Nucleus instance gets its own isolated save folder by default, which is correct for games where every player needs independent progress (character levels in Borderlands 2, for example). For games where you want shared world progress, a Minecraft Java world, a Project Zomboid save, the handler needs to point every instance at the same save directory instead of separate ones, the same approach the community’s Minecraft setup guide documented for LAN play through Nucleus Co-op back in August 2025, which used MultiMC v1.17.1 and notes Forge limitations. That guide covers a setup with 1 account offline as well as multiple accounts through repeated account launches. This setting lives in the handler configuration and varies by game, so check the specific handler’s notes on the supported games list before assuming the default behavior matches what you want.
Step 10: Tune Performance for More Than Two Players
Every instance you add scales CPU, GPU, and RAM demand almost linearly, since Nucleus isn’t doing anything clever to share rendering work between windows, it’s genuinely running the game multiple times. For 3-4 player sessions on anything short of a high-end desktop, drop graphics presets to Medium or Low across all instances, lower per-instance resolution, and close background overlays (Discord, GeForce Experience, RGB software) that hook into the graphics pipeline and can conflict with window management.
# Performance checklist before a 4-player session
1. Disable Windows Game Mode
2. Close Discord overlay, GeForce Experience overlay, MSI Afterburner OSD
3. Set graphics preset to Medium or lower on all 4 instances
4. Cap resolution per instance to 1280x720 or lower
5. Confirm SSD has 20%+ free space for shader cache and temp filesWindows’ own Game Mode, which is designed to prioritize a single foreground game, can actively work against Nucleus by starving background instances of CPU time. Turning it off (Settings > Gaming > Game Mode) is one of the more counterintuitive but consistently effective fixes for stutter across multiple simultaneous instances.
Step 11: Confirm Anti-Cheat Compatibility Before You Commit
This is the step most new users skip, and it’s the one that causes actual account bans rather than just annoyance. Games running kernel-level anti-cheat, the class that includes many competitive shooters and battle royales, frequently detect window and input hooking as suspicious behavior and can flag or ban the account, even when the player’s intent is purely local co-op. Community handler documentation is consistent on this point: avoid running Nucleus Co-op against ranked or competitive online modes, and stick to offline, LAN, or explicitly local multiplayer modes where publishers tolerate multi-instance tools.
Before adding any online-capable game to Nucleus, search the handler’s notes or the supported games list for anti-cheat warnings. If none are listed but the game has known anti-cheat (BattlEye, EAC, or a proprietary system), treat that as a signal to test cautiously in an offline mode first rather than assuming it’s safe because a handler exists.
Step 12: Save Your Profile for Next Time
Once a game is configured the way you want, player count, layout, controller mapping, save behavior, save it as a profile inside Nucleus so you don’t have to rebuild the configuration every session. Profiles are stored in the app’s local folder structure and persist across updates, though it’s worth checking release notes when you update Nucleus itself, since a handler occasionally needs a small tweak after a game patch changes its executable behavior.
Common Pitfalls to Avoid
- Skipping the standalone launch test. Adding a broken or unpatched install straight into Nucleus makes debugging far harder than confirming the game runs on its own first.
- Plugging in controllers after launching Nucleus. Devices connected mid-session frequently fail to register correctly; always connect every controller before opening the app.
- Running competitive online modes through Nucleus. Kernel-level anti-cheat can flag multi-instance tooling as cheating and risk an account ban, even without malicious intent.
- Downloading Nucleus from anywhere other than the official GitHub repo. Third-party mirrors have bundled unwanted installers with the free tool in the past.
- Assuming default save behavior fits your game. Some titles need a shared save folder across instances for co-op progression; others need isolated saves. Check the handler notes rather than guessing.
- Ignoring Windows Game Mode. It’s designed for single-game prioritization and can starve background instances, causing stutter that looks like a hardware limitation but isn’t.
- Trying 4-player splits on 16 GB of RAM with a AAA title. Match your player count to your hardware headroom, especially for memory-hungry games; drop to 2 players rather than fighting constant swapping.
Nucleus Co-op vs. Universal Split Screen vs. Steam Remote Play Together
Nucleus Co-op isn’t the only tool in this space, and picking the right one depends on what you’re actually trying to do. Universal Split Screen takes a more generic approach: it hooks into windows and input without relying on per-game handlers, which makes it more flexible for obscure titles but requires more manual configuration since there’s no library of 800+ pre-built profiles to lean on. Nucleus trades some of that flexibility for a much larger, better-documented catalog of ready-made setups.
Steam’s own Remote Play Together feature solves a completely different problem: it streams an already-local-multiplayer game from one host PC to remote friends over the internet, so only the host needs to own the game, and up to four players can join in ideal network conditions. It’s accessed through the Steam overlay by right-clicking a friend and selecting Remote Play Together, according to Valve’s own support documentation. The key distinction is that Remote Play Together makes existing local multiplayer playable online; it does not add split-screen support to a game that has none. Nucleus does the opposite, it adds local split-screen to games that were never built with it, for players physically sharing one PC and one room.
| Tool | Adds Split-Screen to Non-Split Games | Works Over the Internet | Setup Style | Cost |
|---|---|---|---|---|
| Nucleus Co-op | Yes | No (local only) | Pre-built handlers, 800+ games | Free / open source |
| Universal Split Screen | Yes | No (local only) | Manual, generic hooks | Free / open source |
| Steam Remote Play Together | No | Yes | Built into Steam client | Free |
Since big co-op-focused releases like Lethal Company, Phasmophobia, Grounded, Sons of the Forest, and Deep Rock Galactic ship as online-only with no native couch mode, tools like Nucleus fill a real gap that publisher decisions created rather than one caused by technical limitations. If your goal is playing an online-only game with someone across the country, Remote Play Together is the right tool; if your goal is two or four people on one couch playing a game that only supports network multiplayer, Nucleus is built specifically for that.
Advanced Tips
For games not yet on the official supported list, you can build a manual handler by studying an existing one for a similar engine (Unreal Engine titles often share enough launch-parameter structure that a working handler for one game gives a solid starting template for another). Community wikis document the handler format, and testing incrementally, confirming Instance 1 launches cleanly before adding Instance 2, saves significant debugging time over configuring everything at once and troubleshooting blind.
If you’re running Nucleus on a system that also handles game mod management, keep Nucleus profiles and mod-manager profiles separate; mixing them can cause a handler to launch the wrong executable version, especially for titles managed through tools that swap between vanilla and modded builds. For households running multiple co-op sessions regularly, dedicating a folder per game with its own handler config avoids configuration drift when you update Nucleus itself.
Finally, if a specific handler stops working after a game update, check the handler’s GitHub or wiki page before assuming Nucleus itself is broken, most compatibility breaks come from a game patch changing executable behavior or DRM checks, not from the core Nucleus application, and handler maintainers typically push a fix within days of a widely-used title updating.
Building a Handler for an Unsupported Game
When a title isn’t on the 800+ game supported list, you have two options: wait for the community to build a handler, or build a basic one yourself and share it back. A handler at its core is a configuration file describing the executable path, launch arguments per instance, window sizing rules, and input mapping behavior. Start by identifying whether the game already supports any form of local multiplayer or split-screen through a controller (many games technically support two local gamepads even without split-screen, which simplifies the handler considerably since you’re only managing windows, not per-instance input isolation).
Test incrementally. Get a single instance launching cleanly through Nucleus with default settings before adding a second. Once two instances launch side by side without crashing, work on window positioning, then controller isolation, then any DRM or save-path quirks specific to that game. This staged approach turns what looks like an all-or-nothing black box into a series of small, debuggable steps, and it mirrors how most existing handlers in the community library were actually built, through iteration, not a single perfect configuration written from scratch.
If you get a working configuration, consider submitting it back through the project’s GitHub or wiki so the next person searching for that game doesn’t have to repeat the process. The 800-plus-game catalog didn’t appear from a single development team; it grew because individual players solved their own split-screen problem and then shared the fix.
Handling Network Play Alongside Split-Screen
A less obvious but genuinely useful configuration combines Nucleus Co-op’s local split-screen with the game’s own online multiplayer, so two people on one couch can join a larger online session together, effectively turning a 2-player local split into a combined local-plus-remote lobby with friends elsewhere. This works because Nucleus only manages the local instances; once each instance is running, it can join any multiplayer session the game itself supports, online or local, exactly as a single standalone copy could. The practical limitation is bandwidth and CPU: two local instances each maintaining their own network connection to an online match roughly doubles the upload requirement compared to a single player, which matters most on modest home internet connections during peak hours.
For games with strict matchmaking or anti-cheat in online modes, revisit the anti-cheat warning from Step 11 before attempting this combined setup, running two instances of the same game connecting to the same publisher’s online servers from one IP address is exactly the kind of pattern that can trigger automated flags, even in games where a single Nucleus instance would have been fine offline.
Troubleshooting Common Issues
- Second instance won’t launch (Steam error). Check the handler’s DRM/Steam settings; most rely on local API emulation to let each instance behave as an independent local player. Confirm only one Steam client is running in the background.
- All controllers control the same instance. Input locking wasn’t enabled, or a controller was connected after Nucleus started. Close the game, reconnect all controllers first, then relaunch with input locking turned on.
- Severe stutter with 3+ instances. Lower per-instance resolution and graphics preset, disable Windows Game Mode, and close background overlays (Discord, GeForce Experience) that hook the graphics pipeline.
- Game launches but window won’t resize or reposition. Some titles fight forced windowed/borderless mode. Check whether the handler specifies a required in-game display setting (borderless windowed vs. exclusive fullscreen) and match it manually in the game’s own options first.
- Audio only plays from one instance. Windows sometimes routes all game audio to a single default device. Check the game’s audio settings per instance, and consider using a virtual audio mixer if the handler doesn’t manage per-instance audio routing automatically.
- Handler exists but game isn’t in the dropdown list. Manually download the handler file from the supported games page or wiki rather than relying on in-app auto-detection, then import it through Nucleus’s manual handler option.
- Game runs solo but instances won’t connect to each other. Nucleus manages windows and input, not in-game networking. Use the game’s own “host local game” / “join LAN game” menu inside each instance to connect them into one session.
- Account flagged or banned after using Nucleus. This almost always means the game had active anti-cheat in a competitive/ranked mode. Stick strictly to offline or explicitly local modes going forward, and avoid using Nucleus with any title that has known kernel-level anti-cheat in online play.
- Shared save progress isn’t carrying over between sessions. Check whether the handler defaults to isolated per-instance saves; for games meant to share a single world or save file, the save path needs to be manually pointed at one shared directory.
- Nucleus itself won’t start or crashes immediately. Confirm you extracted the full ZIP (not just Nucleus.exe alone) into a folder with write permissions, and check that antivirus software hasn’t quarantined a required file.
Sample Output: A Working 4-Player Session
[Nucleus] Loading handler: deeprockgalactic_v3.hdl
[Nucleus] Players configured: 4
[Nucleus] Layout: grid_2x2 | Resolution per instance: 1280x720
[Nucleus] Launching instance 1... OK (PID 18452)
[Nucleus] Launching instance 2... OK (PID 18460)
[Nucleus] Launching instance 3... OK (PID 18471)
[Nucleus] Launching instance 4... OK (PID 18483)
[Nucleus] Controller 1 -> Instance 1 [locked]
[Nucleus] Controller 2 -> Instance 2 [locked]
[Nucleus] Controller 3 -> Instance 3 [locked]
[Nucleus] Controller 4 -> Instance 4 [locked]
[Nucleus] Window tiling applied: 4/4 instances positioned
[Nucleus] Session ready.Building a Complete Split-Screen Game Night Setup
Putting everything together, a full working setup looks like this: install Nucleus Co-op v2.4.2 from the official GitHub releases page, confirm your PC meets the 16 GB RAM / 6-core CPU floor for a 2-player split, add your game and verify it launches standalone, pull the matching handler from the 800+ title supported games list, configure player count and window layout, connect and lock every controller before launch, and test with a short session before committing to a full game night. For games with heavier anti-cheat, double-check the handler notes or default to offline modes only. Once the profile is saved, subsequent sessions take under a minute to get four players into a shared couch game that Steam’s store page never advertised as supporting split-screen at all.
This same workflow scales down cleanly too, a two-player setup with one keyboard/mouse player and one controller player is the most reliable configuration for troubleshooting a new handler for the first time, since it removes several points of failure (fewer devices to mis-map, less RAM pressure, simpler window layout) before you scale up to three or four players.
Real-World Example: Setting Up a 3-Player Deep Rock Galactic Night
To make the process concrete, here’s how a typical three-player session comes together for a cooperative shooter like Deep Rock Galactic, one of the “Easy” difficulty entries on the supported games list. After downloading and extracting Nucleus, you add the game from its Steam install folder, then pull the matching handler from the supported games page rather than writing one from scratch. The handler defaults to a 3-player horizontal split at 1280×720 per instance, which fits comfortably on a 1440p monitor without cropping the UI.
Before launch, you plug in two Xbox-style controllers for players two and three, leaving keyboard and mouse for player one, and confirm input locking is enabled so a stray controller signal doesn’t bleed into the wrong window. On the first launch, each instance can take 30-60 seconds to load, compile shaders, and position itself, in line with the October 2026 setup guide’s own estimate for instance launch and positioning time, though subsequent launches are faster since the cache persists per instance. Once all three windows are visible, player one hosts a local session from the in-game menu, and players two and three join it the same way they would over a LAN, at which point the trio drops into the same mission together, each with independent camera control and full-resolution rendering rather than a cramped shared viewport.
This specific combination, three players, one keyboard/mouse plus two controllers, horizontal split at reduced per-instance resolution, tends to be the most forgiving starting configuration for people testing Nucleus for the first time, since it balances hardware load against a genuinely social couch experience without immediately requiring a four-monitor array or a workstation-class CPU.
Frequently Asked Questions
Is Nucleus Co-op free?
Yes. It’s a free, open-source tool distributed through the official SplitScreen-Me GitHub repository, with no subscription or paid tier.
Does Nucleus Co-op work on Steam Deck or Linux?
Not natively. Nucleus is built for Windows; Steam Deck users typically need a Windows install (dual boot or a separate compatibility layer) to run it, since it relies on Windows-specific window and input hooking.
Can I get banned for using Nucleus Co-op?
In games with kernel-level anti-cheat active in online/ranked modes, yes, it’s possible, since the tool’s window and input hooking can be flagged as suspicious. Stick to offline or explicitly local multiplayer modes to avoid this risk entirely.
How many players can Nucleus Co-op support?
Most handlers support 2-4 players, matching what the source game’s local/LAN multiplayer mode allows. Nucleus can’t exceed the player cap the game itself supports.
What’s the difference between Nucleus Co-op and Steam Remote Play Together?
Nucleus adds local split-screen to games without native support, for players sharing one PC. Remote Play Together streams an already-local-multiplayer game over the internet to remote friends; it doesn’t add split-screen to games that lack it.
Do all players need to own the game separately?
Typically yes, since Nucleus launches separate instances of the same installed game rather than streaming one copy to multiple players the way Remote Play Together does.
My game isn’t on the supported list. Can I still use Nucleus?
Yes, but you’ll need to build a manual handler, which requires more trial and error than using one of the 800+ pre-built handlers already documented on the official supported games page.
Why does my 4-player session stutter even on a decent PC?
Four simultaneous instances multiply CPU, GPU, and RAM load almost linearly. Lower per-instance resolution and graphics settings, disable Windows Game Mode, and close background overlays before assuming your hardware is the bottleneck.
