0% found this document useful (0 votes)
1K views4 pages

Black Ops 3 PC 2-4 Player Splitscreen

This document provides an unofficial guide for setting up 2-4 player splitscreen in Call of Duty: Black Ops III using Nucleus Co-op. It details the necessary equipment, the process for configuring controllers, and troubleshooting tips for maintaining the setup during gameplay. The guide emphasizes the importance of managing controller inputs to ensure all instances function correctly and offers alternative configurations for fewer players.

Uploaded by

Kevin Lunar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1K views4 pages

Black Ops 3 PC 2-4 Player Splitscreen

This document provides an unofficial guide for setting up 2-4 player splitscreen in Call of Duty: Black Ops III using Nucleus Co-op. It details the necessary equipment, the process for configuring controllers, and troubleshooting tips for maintaining the setup during gameplay. The guide emphasizes the importance of managing controller inputs to ensure all instances function correctly and offers alternative configurations for fewer players.

Uploaded by

Kevin Lunar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Black Ops 3 PC - 2-4 Player Splitscreen

Using Nucleus Co-op (Unofficial Guide)


Preface:

For this I am assuming individuals already know how to use Nucleus and add handlers.
Information comes from testing that was done using 4 Xbox controllers, a keyboard and
mouse, and the latest steam version of the game.

You need: 2+ controllers and a keyboard and mouse

In this post I'll be referring to Controllers as C (C1,C2,C3,C4) and Instances as inst


(inst1, inst2, etc...)

Background:

Call of Duty Black Ops III handler v26072024.rar can be found in Discord/Nucleus
Co-op/wip-handlers&testing/Call of Duty Black Ops 3. Check the pined messages for
this handler or latest WIP.

v26072024 handler has problems with proto-input because of B03. However, we can
"fake" out B03 and get inputs to work.

It's simple once you understand what's going on. Each instance of B03 sees turned on
controllers but defaults its input to 2 controllers only: C1 or C2. However we can change
which input B03 defaults to by turning off the controllers it PRESENTLY defaults to, and
if need be, selecting 1 of the 2 new controllers it sees as defaults as a "Split Screen"
input. Thus allowing us to choose which of the 2 controllers B03 is defaulting to that we
want to use. Importantly once an instance of B03 has been given an input it will stick
with it, until it's changed or until that input is no longer available (like if the controller
turns off).

It'll make more sense once you see it in action.

Steps:
1. Use Nucleus normally to start B03 handler: connect your 4 controllers, choose
your settings, and start. Wait for all instances to load completely into the login
screen. No need to lock inputs.

2. Press A on C1 or alt-tab and use the mouse individually to log into B03 on all
instances.

3. In the main menu press start button on C1 to bring up the menus. C1 should be
controlling all instances so all instances should be seeing "MENU" now.

4. Turn off C1 and C2. you get rid of "controller disconnected" msg use the
bumpers on C3 to move around a bit.

5. In Inst3 and Inst4, navigate to menus>options>controls>gamepad>Split Screen

6. Now we get an instance of B03 to default to either C3 or C4 by simply putting the


controller we DON'T want to use into "Player 2 Input Device". For example, at
this point likely C3 will be controlling, at least, inst3 and inst4. So if we want inst3
to use C3 we don't have to change anything, it's already got the input we want. If
we want inst4 to use C4 though we need to put C3 into the "Player 2 Input
Device" so B03(with C3 and C4 available) will default to using C4. Once you do
this you'll notice that inst4 and C4 are hooked up and working independently.

7. Now we just need inst1 and inst2 working. Turn back on C1 and C2. If you are
not seeing C1 and C2 in the available "Split Screen" input devices simply go to
the left in the menus(like to "interact" or something) then go back to the
"gamepad" section to reload the page.

8. B03 is now defaulting again to C1 and C2. So if we want inst2 to use C2, go
ahead and put into "Player 2 Input Device" the controller/s that are currently
controlling the instance that you DON'T want to be controlling the instance. For
example, right now inst2 is likely being controlled by C3, put C3 into the "Player
2 Input Device". Depending on the order you turned back on C1 and C2, it may
now default to C1. So now put C1 into the "Player 2 Input Device", and since it's
only defaulting to C1 and C2, boom inst2 is now using C2. Use this same
process for inst1. Make the controller you don't want to use your split screen
input, and get inst1 to default to C1 for input(possibly select C3, then Select C2
and you should be good).

10.Hard parts over. Let's play. Inst1 needs to start a multiplayer or zombies game.
Then once fully loaded in, alt-tab and use the mouse to select anything(another
instance, the desktop, doesn't matter) that isn't inst1/the host. Your computer just
can't be focusing inst1.

11. Hold F2 for a few seconds, until all instances that AREN'T the host freeze/turn
black. Now all instances should be joining the host.

Notes:

-Important- Because of the way B03 defaults to 2 controllers, if C3 or C4 turns off


you'll have to do the input process all over again. This is because B03 inst3,4 or
whatever, will default back to using C1(or C2 if C1 is selected as the Split Screen input).

-Only the host has to load mods when playing locally.

-If the host ends the game it ends for all players. If an inst, not inst1, leaves the game,
the game session becomes unstable and all instances, except for inst1, will be kicked
after a couple minutes. They can all rejoin, but give them all a couple minutes before
holding F2 again.

Other Split Screen configurations:

Once you have used 4 instances you can always go down from there, 3, 2 it all works.
The input process is also of course easier and simpler the less controllers/inputs you
have. Keep in mind if you are using 2 instances, B03 having 2 inputs as default is all
you need. So if a controller disconnects it's not a big input problem unlike if you have 3-
4 players.

Now if you'd like, you can also use B03 native split-screen in the 1st/host instance(no
other instances can use it). and then you can have 1 less instance to fuddle around with
and still achieve 3 and 4 player split-screen. It is slightly less risk for a controller to turn
off(or no risk if using 3 players) and a little less hassle in the setup process too. For
example, if you were doing 3 player zombies, anyone's controller can turn off and the
inputs WONT break(assuming inst1 and inst2 are using C1 and C2, and your split-
screen in inst1 is using C3) However this would be in exchange for those eye-sore
native split-screen black bars that B03 has. It's your call.

Credits:

Nucleus Team at SplitScreen.Me

Call of Duty Black Ops III handler v26072024.rar created by Perseveruz

You might also like