1.3.0 broke mods again! Use these scripts to get them working again! Read further below to see more details about this update
So you’ve probably heard that I’ve recently started using an HTC Vive I acquired (or you’re somebody I’ve never met…) and I also love rhythm games, so you see where this is going.
Beat Saber works great on it’s own with my new PC (details in a previous post: Triangulum) but I needed more out of the game, since I’m used to the custom community, songs, skins, etc from OSU (Lazer!).
It’s not too hard to get everything working, just needs some extra tweaks here and there.
For quick reference, the programs I will be using are:
- Protontricks: github.com/Sirmentio/protontricks
- BeatDrop: github.com/StarGazer1258/BeatDrop
- Steam Proton v4.11-2
That’s all you’ll need! Now let’s get started!
Step 1: Install and run Beat Saber once
Before doing anything, run the game normally at least once. Simple, I know, but I’ve had to reinstall a few times when I messed up.
Step 2: Use Protontricks to install BeatDrop
- Launch protontricks via
- Select Beat Saber,
- Select default wine prefix
- Open a terminal for debugging
wine /tmp/beatdrop-setup-*.exeReplace with path to the beatdrop installer you downloaded.
- Install BeatDrop for the system (not user)
- Don’t run beatdrop.
Step 3: Apply fixes to the wine prefix
- Use the same protontricks gui as before, but this time open RegEdit.
- Get this file: github.com/Vash63/bsmodinstaller.py: winhttp.reg
- Import that file via the RegEdit menu.
Next, if you want to use SongCore, (in most cases you do) you need to do an additional step:
cd "~/.local/share/Steam/steamapps/compatdata/620980/pfx/drive_c/users/steamuser/Local Settings" mkdir -p "LocalLow/Hyperbolic Magnetism/Beat Saber"
Replace the ~/.local with your Steam library install location you used for Beat Saber.
This should fix SongCore not allowing you to play custom songs.
Step 4: Open BeatDrop and install mods
Using the same debugging terminal we opened via protontricks, launching BeatDrop can be done with
wine Program\ Files/beatdrop/beatdrop.exe
Then simply install mods as usual, starting with BSIPA. You should see the green ‘patched successfully’ notification.
Step 5: Don’t run BeatDrop and Beat Saber at the same time
Before trying to launch Beat Saber, make sure you close out any programs running in the protontricks session we started, otherwise there could be conflicts with Steam’s usage of the wine prefix at the same time.
BeatSaber 1.3 Update
Alright, this latest update requires even more workarounds this time, but luckily someone’s already published a script to modify the proton instance:
bs-linux-modfix.sh script to fix it up, it’ll handle the weird library / winhttp workarounds required now.
Also, the same guy made a fork of BeatDrop with native Linux releases! Check it out!