I spent three hours last weekend trying to get It Takes Two running with a friend on my rig, only to realize the “official” forums were basically just a collection of people shouting into the void. It’s infuriating. You see these massive, polished guides online that act like you need a degree in systems engineering just to figure out how to play split screen on pc, when in reality, most of the time you’re just fighting with Steam Input or a driver that refuses to recognize a second XInput device. We’ve been conditioned to think PC gaming has to be this unnecessarily complicated ritual of tweaking registry files and praying to the hardware gods, but that’s usually just a sign of bad software design or a guide written by someone who’s never actually sat on a couch with a controller in their hand.
I’m not here to give you a thirty-page dissertation on operating system architecture. I’ve spent enough time rebuilding botched gaming rigs to know that if a solution takes more than five minutes, it’s probably broken. I’m going to show you the actual ways to get local co-op running—from the controller settings that actually stick to the specific launch options that stop your game from crashing the second player two joins. No fluff, no paid sponsorships, just the settings that work so you can actually get to the gameplay.
Table of Contents
Connecting Multiple Gamepads to Windows Without the Headache
The biggest hurdle isn’t the game itself; it’s Windows deciding your second controller is actually a mouse or a weirdly specific MIDI keyboard. If you’re connecting multiple gamepads to Windows, stop assuming everything is plug-and-play. If you’re using Xbox controllers, you’re usually fine, but the second you throw a PlayStation DualSense or a generic third-party pad into the mix, things get messy. I’ve spent way too many Friday nights troubleshooting driver conflicts instead of actually playing. My rule of thumb: if the device isn’t showing up, check your Bluetooth stack or stop relying on cheap dongles that drop connection the moment you hit a heavy combat sequence.
If you’re a Steam user, you basically have a cheat code. Skip the manual driver hunting and go straight to your Steam controller configuration settings. Steam’s input wrapper is honestly the only reason I haven’t thrown my PC out a window when trying to get non-standard gear to work. It forces Windows to see everything as a standardized XInput device, which is the only way to ensure your pc local multiplayer games actually recognize player two without a fight. If you’re trying to play with a friend who isn’t even in the room, look into Steam Remote Play Together—it’s a lifesaver for local-only titles.
Pc Gaming With Two Controllers Avoiding the Input Mess
The biggest headache isn’t the hardware; it’s the software deciding that your second controller is actually just a very confused keyboard. I’ve spent way too many Friday nights staring at a menu where Player 2 is stuck navigating with an arrow key because the game doesn’t recognize the input. When you’re setting up pc gaming with two controllers, the first thing you need to do is check if the game actually supports native local multiplayer. If it doesn’t, you aren’t going to find a magic setting in Windows to fix it; you’re going to be fighting the engine itself.
If you are playing through Steam, stop trying to manually map every single button in the Windows Control Panel and just use Steam Controller Configuration instead. It’s much cleaner. Steam acts as a translation layer that makes even a weird third-party knockoff controller look like an official Xbox pad to the game. This is especially vital for older pc local multiplayer games that were built before the era of standardized XInput. If the game sees your controllers as separate, conflicting devices, you’ll end up with both players controlling the same character, and that’s a fast track to a wasted evening.
Five Ways to Stop Your Local Co-op from Turning into a Tech Nightmare
- Check the Steam Input settings before you start. If you’re using a mix of Xbox and PlayStation controllers, Steam’s controller configuration is usually the only thing keeping your inputs from overlapping and making both players move at once.
- Don’t rely on a single USB hub for everything. I’ve seen too many people plug in four wireless dongles and two wired pads into one cheap hub, only to watch the frame time spike and the inputs lag. Plug your controllers directly into the motherboard or use a high-quality powered hub if you want consistent response times.
- Verify the game actually supports local multiplayer. It sounds obvious, but half the “co-op” games on sale right now are online-only. Check the “Multiplayer” tag on the store page specifically for “Local Co-op” or “Shared/Split Screen” before you drop your money.
- Use Steam Remote Play Together if the game doesn’t have native split-screen. If you’re playing with someone in the next room but the game only allows one player, you can trick it into thinking you’ve got a second controller via the cloud, though expect a bit of latency if your home network is struggling.
- Watch your CPU usage. Running a game at 144Hz is one thing, but when you’re rendering two different viewpoints for split-screen, your CPU is working twice as hard to manage the logic for both players. If your frame rate drops from 120 to 55, it’s probably not the GPU—it’s the processor choking on the extra draw calls.
The TL;DR for Local Co-op
Stop trying to share a keyboard; plug in two dedicated controllers (Xbox or PlayStation) and let Windows handle the drivers so you don’t spend an hour in the settings menu.
Check your game’s Steam or Epic store page first—if it doesn’t explicitly list “Local Co-op” or “Shared/Split Screen,” no amount of hardware tinkering is going to fix it.
If you’re using older or non-standard gear, grab a tool like DS4Windows or X360CE to trick the game into seeing your controllers as standard Xbox inputs, or prepare for a headache.
## The Real Cost of Local Co-op
“Don’t let the ‘supports controllers’ tag on Steam fool you into thinking it’s plug-and-play magic; if you aren’t checking the specific input compatibility before you drop fifty bucks on a game, you’re just buying a very expensive single-player experience that’s going to fight your second gamepad every single time you try to start a match.”
Denny Kowalczyk
Don't Let the Hardware Win
Look, getting local co-op running on a PC isn’t as complicated as some of these bloated forum threads make it sound, but it isn’t exactly “plug and play” either. You’ve got to handle your controller mapping, make sure Windows isn’t treating your second gamepad like a rogue keyboard, and—most importantly—check if the game even actually supports split-screen natively. If you’ve sorted your inputs and you aren’t fighting with ghosting or dead zones, you’re 90% of the way there. Just remember that if you’re pushing a heavy title like Baldur’s Gate 3 or a demanding shooter, that extra overhead of rendering two viewpoints is going to eat your frames. Keep an eye on your performance overhead and don’t be afraid to drop a few settings to keep that framerate stable for both players.
At the end of the day, the reason we bother with all this setup is because there is nothing quite like sitting on the same couch with a friend, even if the “couch” is just two chairs facing a monitor. The tech is just a means to an end. Whether you’re sweating through a co-op run or just messing around in a sandbox, the goal is to stop troubleshooting and start actually playing. So, plug in the sticks, fix the mapping, and get the game running. Life is too short to spend it staring at a settings menu when there are worlds to explore.
Frequently Asked Questions
Will playing split screen tank my frame rate or cause stuttering if I'm already pushing my GPU?
Short answer: Yes, it will. You aren’t just playing one game; you’re asking your GPU to render two separate viewports simultaneously. If you’re already hovering at 60 FPS on Ultra settings, expect that to dip into the 40s once the second player joins. I tested this on a 3070 with Baldur’s Gate 3—splitting the screen at 1440p tanked my 1% lows significantly. If your headroom is thin, drop your shadow quality or resolution scale immediately.
Can I use a mix of controllers, like one Xbox pad and one PlayStation DualSense, without the game getting confused?
You can, but don’t expect it to work perfectly out of the box. Windows loves Xbox controllers because they use XInput, which is basically the native language for most PC games. If you plug in a DualSense, the game might treat it like a generic device or ignore it entirely. Use DS4Windows or Steam Input to force that PlayStation pad to mimic an Xbox controller. It stops the “input mess” and keeps the game from tripping over itself.
Is there a way to play split screen if the game doesn't natively support it, or am I stuck?
You aren’t necessarily stuck, but you’re moving from “plug and play” into “software workaround” territory. If the game doesn’t have a built-in local co-op mode, your best bet is Nucleus Co-op. It basically launches multiple instances of the game and hooks them together to simulate split-screen. It’s a bit of a setup headache and can tank your FPS since you’re running two processes at once, but it’s the only real way to force it.
