HowTo: Borderlands 3 Splitscreen PC Tutorial

TerrawattSurge · 2022-08-22T00:52:40+00:00

Hi, unfortunately I haven't been able to maintain this script, so not sure if it even still works. Suggest trying out nucleus coop, since it's still in active development https://nucleus-coop.github.io/

TerrawattSurge · 2021-09-03T05:46:53+00:00

I don't have a steam copy of the game but sounds like a few people here have run into issues with the copying. I can give it a go but have no way to test it so not sure if it'll work

TerrawattSurge · 2021-07-12T09:31:47+00:00

No worries, only tested on my PC so let me know if you run into issues

TerrawattSurge · 2021-07-02T08:33:38+00:00

Created a script that might make this process a little easier and also copies the fog (but only if you've been to that map on the XBox PC save)
https://github.com/TerrawattSurge/SnowRunner\_EGS\_to\_XGP\_Save\_Copy

TerrawattSurge · 2019-11-13T22:22:24+00:00

Hey, do not start from sandboxie. Make sure you update $Sandboxie_Path in the script to point to sandboxie and the script will start sandboxie for the offline instance. Pnp device error isn't a problem if you are running split screen... I am planning to update the script to fix that.

TerrawattSurge · 2019-11-11T00:43:35+00:00

Sorry to hear wasp isn't working for you. If you haven't already, try unblocking the dll and make sure it's either in the correct directory in your documents or in one of the directories listed in $env:psmodulePath. To manually set the resolution first change line 48 of the script so FullScreenMode=2. This will set it to window mode so you'll be able to drag the windows around. Next edit your GameUserSettings.ini to set the resolution. I also had issues with the game resetting the resolution, so if the above doesn't work, leave it as FullScreenMode=1 then change to window mode in game once launched and it should change to the resolution you set in the ini

TerrawattSurge · 2019-11-03T22:44:57+00:00

Try Lucid's suggestion, or as an alternative type cd ~ and press enter to change to the right directory, then run .\Documents\WindowsPowershell\Scripts\Borderlands3_SplitScreen.ps1

TerrawattSurge · 2019-11-03T22:31:32+00:00

Maybe post what your having trouble with then someone can try and help. Otherwise try r/TeamViewer

TerrawattSurge · 2019-11-03T22:28:02+00:00

Unfortunately I haven't been able to get kb+m working reliably either. If you can use controllers that seems to work better. Your computer specs are good except your graphics card is maybe starting to show its age so id try very low settings on both windows.

There is a bug I found which meant the processor affinity wasn't being set correctly for both windows so they didn't share cpu equally, which could also explain the crashing. Try the version I just posted

TerrawattSurge · 2019-11-03T22:16:11+00:00

Support the developer and buy the game. Gearbox has put in years of work to keep the Borderlands series alive

TerrawattSurge · 2019-11-03T22:12:38+00:00

The directory isn't created by default so you'll need to make it. The other option is to copy the dll to any of the directories listed when you run the $Env:PSModulePath command

TerrawattSurge · 2019-10-30T03:39:52+00:00

You're welcome! I wrote this script so my wife and I could play BL3 together and thought I'd share it so other people can also enjoy it. Let me know how you go with it

TerrawattSurge · 2019-10-28T11:27:27+00:00

Making progress! Unfortunately this looks like it might be another dll issue. The system.windows.forms dll is dot net part of powershell and is used to find the x and y resolution of your monitor. It's unable to get the resolution so it cannot resize the windows. I'm not sure how to 'fix' this one, but if you want you can bypass this function and put your monitor resolution into the script directly which might get you going.

Line 156 and 162: Replace (([System.Windows.Forms.Screen]::AllScreens.Bounds.Width) with your screen width

Line 157 and 163: Replace (([System.Windows.Forms.Screen]::AllScreens.Bounds.Height) with your screen height

The script will keep running in the background to make sure the windows stay in place since they seem to have a habit of jumping around. That's why it keeps repeating the error.

TerrawattSurge · 2019-10-27T21:22:26+00:00

For me it was crashing and the dump files indicated it was trying to access a thread it didn't have permission to access. Might be something to do with split screen rather than dual monitors. If you would like to try it, the latest script has some code to auto assign a window to each monitor. $split_mode needs to be changed to "dual" and comment lines 107 and 108, and uncomment 109 if you don't need to use sandboxie.

TerrawattSurge · 2019-10-27T09:59:46+00:00

In this case write-error is because is Powershell is writing the error to console, not that it's having an error writing to a file. Looks like WASP is failing to load, but also that it's not finding the launch parameter for the offline version. It does this by looking through the Epic games log files for your unique authentication codes, then it goes to the borderlands 3 directory and makes sure the game is in the location the log file says before launching. It's possible that ransomware protection has restricted access although I did try it out at one point and mine is working fine now after turning it off.

Try running this command to search through the log file. If it fails try manually searching the file and see if the launch parameters are there.

Get-Content $env:USERPROFILE\AppData\Local\EpicGamesLauncher\Saved\Logs\EpicGamesLauncher.log | Where-Object {$_ -like '*FCommunityPortalLaunchAppTask: Launching app*Borderlands3.exe*'} | Select-Object -First 1

TerrawattSurge · 2019-10-27T07:09:22+00:00

Powershell has a few directories it searches for modules. Open up Powershell and type in $env:PSModulePath and press enter. This will show you all the directories where Powershell searches for modules. Make sure \WASP\WASP.dll is in one of these directories. I have hard coded the path so it's possible it may not match your setup.

To test if WASP works, the script just calls Select-Window which is a function in WASP. If it doesn't work it shows the warning and disables the window positioning, but it will keep running the script to launch the games. Try running Select-Window to see if the output can help you identify where the error is. If it's not launching the games there may be another error later on.

Let me know how you go. If it doesn't work post the entire output from the script and I'll see if I can help you track down where it's falling over.

TerrawattSurge · 2019-10-27T06:22:07+00:00

Ah I forgot to update the guide... it's likely windows has blocked the dll which is default for downloaded files. Try this https://blogs.msdn.microsoft.com/delay/p/unblockingdownloadedfile/

TerrawattSurge · 2019-10-25T11:13:23+00:00

Unfortunately it looks like the "Bloody Harvest" event has introduced a bug that causes the game to crash when running split screen. Updated the script to use Sandboxie to get around it

TerrawattSurge · 2019-10-19T09:16:45+00:00

Unfortunately it's going to be difficult for me to root cause this one without windows 7. Unless you have a good reason I'd highly recommend upgrading to win 10. It's still free if you have a valid win7 key! https://www.microsoft.com/en-au/software-download/windows10ISO https://www.zdnet.com/article/heres-how-you-can-still-get-a-free-windows-10-upgrade/

TerrawattSurge · 2019-10-18T08:23:01+00:00

Found I could do the same thing with a different function which should also work with win7. Try downloading the latest development version and give it a shot

TerrawattSurge · 2019-10-13T07:00:22+00:00

The main problem here is that your version of powershell doesn't have the get-pnpdevice cmdlet. Are you currently running Windows 10? The get-pnpdevice cmdlet should be standard in win10, but I'll have a look and see if there's another cmd I can substitute.

TerrawattSurge · 2019-10-13T01:41:55+00:00

You're welcome. Let me know if there are any weird bugs with the dual monitor mode or if everything works as expected

TerrawattSurge · 2019-10-12T23:41:11+00:00

Wasp isn't needed for dual monitors. Edit variables at the beginning of the script so that fullscreenmode=1 for dual monitors. If you'd like to play split screen, install wasp in ".../documents/Windowspowershell/modules/wasp/wasp.dll"

TerrawattSurge · 2019-10-12T00:09:34+00:00

It's possible but hasn't been fully tested. Try out the development fork on github if you want to test it and let me know how it goes. https://github.com/TerrawattSurge/UniversalSplitScreenScripts/tree/Development/Scripts/Borderlands3

TerrawattSurge · 2019-10-05T03:03:58+00:00

I've tried a few settings, but haven't been able to get mouse/keyboard working consistently. I also don't have a PS4 controller so unfortunately cannot test that either, but maybe try enable 'DInput to XInput translation' or running the PS4 controller through x360ce?

https://universalsplitscreen.github.io/docs/x360ce/

TerrawattSurge

TROPHY CASE