Updated My Wabbajack VM Setup (markdown)

Omni-guides
2025-02-11 21:01:52 +00:00
parent 874815c7c5
commit 64717493af

@@ -2,9 +2,9 @@
## Introduction
This is a first draft of this guide, I'll tighten it up as time allows, but hopefully it provides a starting state.
⚠️ ❗ This method is now no longer recommended. We are now able to run [Wabbajack via Proton](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/wiki/Wabbajack-via-Proton) directly from Steam (on both Deck and PC). No more messing with Virtual Machines! I will leave this here for information purposes only. ⚠️ ❗
Quite a few people have asked, so here's a quick rundown of my method for running Wabbajack in a Windows VM. This is needed because Wabbajack does not work via Wine/Proton at all. Using the below steps, only Steam and Wabbajack (+dependencies) are installed inside the Windows VM, nothing else. Steam is configured to detect the Steam Library from the Linux Filesystem, and Wabbajack is able to download mods and install Wabbajack Modlists directly to the Linux Filesystem. Using this method, the games such as Skyrim, Fallout etc _do not need_ to be installed inside the VM as well as on Linux, and it also avoids the need for copying the modlist from Windows to Linux after the installation is complete.
Quite a few people have asked, so here's a quick rundown of my method for running Wabbajack in a Windows Virtual Machine (VM). This is needed because Wabbajack does not work via Wine/Proton at all. Using the below steps, only Steam and Wabbajack (+dependencies) are installed inside the Windows VM, nothing else. Steam is configured to detect the Steam Library from the Linux Filesystem, and Wabbajack is able to download mods and install Wabbajack Modlists directly to the Linux Filesystem. Using this method, the games such as Skyrim, Fallout etc _do not need_ to be installed inside the VM as well as on Linux, and it also avoids the need for copying the modlist from Windows to Linux after the installation is complete.
I was hesitant to create a guide for this because there are so many possibilities of how to achieve similar, but enough people have asked - so here it is. The method essentially boils down to installing a Windows 10 VM and sharing the Linux Filesystem to it via Samba. Yes, there are other, technically better options for filesharing between a VM and the host, but out of NFS, SSHFS, VirtIOFS, VirtualBox Folder Sharing and so on, Samba was the only one that didn't prove unstable with either Steam detecting the Games Library, Wabbajack detecting the game as being installed, or hangs and crashes while downloading and extracting the modlist via Wabbajack.