mirror of
https://github.com/Omni-guides/Jackify.git
synced 2026-01-17 19:47:00 +01:00
Updated Skyrim: Tuxborn (markdown)
Omni-guides
@@ -1,100 +1,182 @@
|
||||
|
||||
|
||||
Introducing [Tuxborn](https://www.nexusmods.com/skyrimspecialedition/mods/114206)_, the first Wabbajack Modlist specifically designed from the ground up with the Steam Deck in mind, and inspired by the likes of Septimus, Redoran and Eldryn._
|
||||
|
||||
[](https://ko-fi.com/D1D8H8WBD)
|
||||
|
||||
---
|
||||
|
||||
## Automated Configuration
|
||||
---
|
||||
|
||||
While this guide contains the step by step process to get the Modlist up and running, Tuxborn has been fully tested against my automation script successfully.
|
||||
|
||||
If you wish to carry out the steps manually because you want to learn the process, or simply enjoy tinkering, then absolutely feel free to follow the below steps. Otherwise, you can find the Automation Script and instructions for use here - [Using the Omni-Guides Automation Script](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/wiki/Using-the-omni%E2%80%90guides.sh-Automation-Script).
|
||||
## Full Tuxborn Install Guide (SteamDeck)
|
||||
|
||||
If you have enough disk space available on your Steam Deck, you can now carry out the entire download and installation of Tuxborn via Wabbajack entirely on the Steam Deck. The total space required for this would be ~344GB, though this is made up of both the Installation and the Downloads (which can be deleted once the install is complete and running successfully).
|
||||
|
||||
If you do not have enough disk space available, then you will need to run Wabbajack on another system, and then transfer the Installation directory from that other system to your Steam Deck. You can see details on transferring from a Windows system to the Steam Deck [here](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/wiki/SyncToDeck). Likewise, if you have already downloaded Tuxborn on another system and transferred it to the Deck, resume this guide from [Step 3](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/wiki/TuxbornSteamDeckFullInstall.md/#step-3---post-wabbajack-steps).
|
||||
|
||||
If Wabbajack is new to you, or you haven't tried to run a Wabbajack Modlist on the deck before, the below process may seem very complicated and a daunting process. Not going to lie, it isn't the easiest thing to do in life, but it is very rewarding once complete!
|
||||
|
||||
It is **STRONGLY RECOMMENDED** to have Nexus Premium for the install process.
|
||||
|
||||
The following should be carried out in Desktop mode.
|
||||
|
||||
There are two parts to getting Tuxborn running on Steam Deck - Firstly the Wabbajack application, which will download and install the modlist, and secondly the post-install requirements. I have done my best to automate as much as I can of both parts (yes, doing this all manually would be _even longer_!)
|
||||
|
||||
You will need to have Skyrim Special Edition Installed on your Deck, have started it once to main menu, and allow it to download all the CC Content when prompted.
|
||||
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Instructions
|
||||
### STEP 1 - Install Wabbajack via Steam/Proton
|
||||
|
||||
**The following has been tested on Tuxborn 0.4.0**
|
||||
#### 1.1 - Create a Wabbajack Directory and Download Wabbajack
|
||||
|
||||
This guide only covers getting the Modlist running. It does not cover downloading the Modlist via Wabbajack, or how to copy the Modlist to your Steam Deck/Linux system. Once you have the list downloaded and installed on a Windows system, and then copied to your Linux/Steam Deck system, these steps will need to be carried out in Desktop mode. Once complete, you will be able to launch the Modlist and play the game from Game Mode. For Tuxborn, you will need to have updated to the latest version of Skyrim (1.6.1170), have launched the vanilla Skyrim game at least once, and have downloaded all the Creation Club content. I also assume that you have set a user password on the Steam Deck.
|
||||
There are only a couple of steps that I can't automate for this - Downloading the Wabbajack installer, adding it to Steam, and running the initial launch.
|
||||
|
||||
While not specifically required, I strongly recommend you create a directory to use for Wabbajack, just to keep things in a sensible place and together. You can use a file browser or cli to create this new directory - for this guide I will use /home/deck/Wabbajack, but the commands shown will use the $HOME variable, which should apply the command to your user home directory on your system.
|
||||
|
||||
```
|
||||
mkdir -p $HOME/Wabbajack
|
||||
```
|
||||
|
||||
Next, download the Wabbajack Application into the Wabbajack directory we created:
|
||||
|
||||
```
|
||||
wget -O $HOME/Wabbajack/Wabbajack.exe https://github.com/wabbajack-tools/wabbajack/releases/latest/download/Wabbajack.exe
|
||||
```
|
||||
|
||||
Alternatively, just download it from [wabbajack.org](https://www.wabbajack.org/) via your browser and then copy or move it into the new Wabbajack directory. Either way, once you have a $HOME/Wabbajack/Wabbajack.exe in place, we're good to proceed.
|
||||
|
||||
|
||||
#### 1.2 - Add Wabbajack.exe to Steam
|
||||
|
||||
Add Wabbajack.exe to Steam by using the "Add a Non-Steam Game to My Library" function from Steam:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-AddNonSteamGame.png" width="600">
|
||||
|
||||
In the window that appears, click the "Browse" button at the bottom:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-BrowseNonSteamGame.png" width="600">
|
||||
|
||||
Browses to the path of your Wabbajack.exe, which if you are following these instructions exactly, will be /home/deck/Wabbajack/Wabbajack.exe:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_AddNonSteamGameWabbajack.exe.png" width="600">
|
||||
|
||||
Click "Add Selected Programs":
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_AddSelectedWabbajack.exe.png" width="600">
|
||||
|
||||
Once added, right click the new Wabbajack.exe entry in steam, and go to Properties. I recommend you change the name to simply "Wabbajack":
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/WabbajackProton/WabbajackProton_SteamProperties.png" width="600">
|
||||
|
||||
Next, click the Compatibility tab, and set it to use "Proton Experimental":
|
||||
|
||||
<<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/WabbajackProton/WabbajackProton_SteamCompatibility.png" width="600">
|
||||
|
||||
With that set, close the properties window and click Play for the Wabbajack entry in Steam. This will start Wabbajack for the first time, which is when the application properly downloads and installs the latest version of Wabbajack for you. It'll take a little time to download and install, just let it complete.
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/WabbajackProton/WabbajackProton_WabbajackInstalling.png" width="600">
|
||||
|
||||
Once done, the Wabbajack application itself should open up - **Close it down** before trying to use the application, and move on to the next step.
|
||||
|
||||
|
||||
#### 1.3 - Run the WabbajackProton Install script
|
||||
|
||||
I've written a bash script [(source)](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/binaries/WabbajackProton.sh) that will configure the Proton Prefix as required to run Wabbajack via Proton. Run the following in a terminal/konsole and follow the few steps when prompted:
|
||||
|
||||
```
|
||||
bash <(curl -s https://raw.githubusercontent.com/Omni-guides/Wabbajack-Modlist-Linux/refs/heads/main/binaries/WabbajackProton.sh)
|
||||
```
|
||||
|
||||
e.g:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_RunWabbajackProton.sh.png" width="600">
|
||||
|
||||
The steps below may seem wordy and plentiful, but they can be carried out relatively quickly - I just wanted to give context and description to each step.
|
||||
|
||||
---
|
||||
|
||||
### Step 1 - Create the directory
|
||||
|
||||
Once Wabbajack has successfully completed the download and installation of the Modlist on your Windows system, create a new directory on the Steam Deck to house the required files - this can either be on the internal storage, or with the use of a specific launch parameter described below, can live on the SD Card. Open up a Konsole terminal and run **only one** of the following, depending on where you want to store the Modlist:
|
||||
### STEP 2 - Run Wabbajack
|
||||
|
||||
#### 2.1 Nexusmods Login
|
||||
|
||||
All being well, that should really be all that is needed. Start Wabbajack from Steam again, and log in to Nexus using the little cog in the top right, followed by the Login button:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_WabbajackNexusLogin.png" width="600">
|
||||
|
||||
**Please Note:** The Nexus Login function is by far the most unreliable part about running Wabbajack on Deck/Linux. If the login screen remains black, then you may need to remove the Wabbajack entry from Steam, and then start again from [Step 1.2](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/wiki/#12---add-wabbajackexe-to-steam). If you continue to have issues, please reach out on Discord for assistance.
|
||||
|
||||
#### 2.2 Install from Disk (Once Tuxborn is available from the Wabbajack Gallery, this will be updated)
|
||||
|
||||
Until Tuxborn becomes available directly from the Wabbajack Modlist Gallery, you will need to manually download the Wabbajack file from here: [Tuxborn Nexus Mods](https://www.nexusmods.com/skyrimspecialedition/mods/114206?tab=files). This will download a .zip file, and you will need to extract the Tuxborn.wabbajack file from inside the zip file. This will be far easier once Tuxborn is on the Wabbajack Gallery, which should happen soon!
|
||||
|
||||
You will want to create a directory for Tuxborn (e.g. /home/deck/Games/Skyrim/Tuxborn) and optionally, a downloads directory outside of your Tuxborn directory (e.g. /home/deck/Games/WabbajackDownloads/Skyrim). You should do this outside of Wabbajack, so that these directories are select-able once inside Wabbajack (asjust to your desired path):
|
||||
|
||||
Create Directory on **Internal Storage**:
|
||||
```
|
||||
mkdir -p /home/deck/Games/Skyrim/Tuxborn
|
||||
mkdir -p $HOME/Games/Skyrim/Tuxborn
|
||||
```
|
||||
|
||||
OR
|
||||
and the downloads directory:
|
||||
|
||||
Create Directory on **SD Card**:
|
||||
```
|
||||
mkdir -p /run/media/mmcblk0p1/Games/Skyrim/Tuxborn
|
||||
mkdir -p $HOME/Games/WabbajackDownloads/Skyrim
|
||||
```
|
||||
|
||||
(Note: Valve plan to change the default mount point of SD Cards within SteamOS soon, I'll update this guide once that chance is in place)
|
||||
Back in Wabbajack, once the Nexus Login is done, use the "back" arrow in the top left to return to the main Wabbajack menu, and click "Install from disk":
|
||||
|
||||
Technically you can use any path or naming convention you like, but for simplicity of following this guide it may be best just to copy the paths I use. **I recommend not including any spaces in the Directory Name** - it does not play well with the Proton/MO2 combination even with the spaces being escaped, for whatever reason..
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_WabbajackProton_InstallFromDisk.png" width="600">
|
||||
|
||||
Copy the Modlist directory from Windows into this newly created directory. There are many ways to do this. I chose to enable ssh on my Deck, and then use rsync to transfer. There are too many options to discuss here, but it should be relatively easy to search for methods. I copied the Modlist Install directory contents from Windows to the newly created directory on the Deck: /home/deck/Games/Skyrim/Tuxborn/
|
||||
Click the three dots next to the "Target Modlist" line. A file browser window should appear - use it browse to the extracted Tuxborn.wabbajack file (NOTE. *Not* the .zip file, you must unzip this to access the Tuxborn.wabbajack file). Fill in the Install and Downloads directories using their Z:\ paths. I recommend following the paths as above:
|
||||
|
||||
Finally for this step, it's best to make sure that the newly copied files have sufficient permissions for your user. Run **only one** of the following for each action (owner and permissions), depending on where you want to store the Modlist:
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/WabbajackProton/WabbajackProton_WabbajackInstallPaths-Deck.png" width="600">
|
||||
|
||||
Change the owner and permissions of the directory on **Internal Storage**:
|
||||
```
|
||||
sudo chown -R deck:deck /home/deck/Games/Skyrim/Tuxborn
|
||||
```
|
||||
```
|
||||
sudo chmod -R 755 /home/deck/Games/Skyrim/Tuxborn
|
||||
```
|
||||
This will keep the Install directory and Downloads directory separate, which will be a benefit in future as the Downloads directory can be deleted once things are all up and running correctly, to free up some space.
|
||||
|
||||
OR
|
||||
#### 2.3 Additional Notes
|
||||
|
||||
Change the owner and permissions of the directory on **SD Card**:
|
||||
```
|
||||
sudo chown -R deck:deck /run/media/mmcblk0p1/Games/Skyrim/Tuxborn
|
||||
```
|
||||
```
|
||||
sudo chmod -R 755 /run/media/mmcblk0p1/Games/Skyrim/Tuxborn
|
||||
```
|
||||
Retaining this section for additional Notes that come up after 1.0 release.
|
||||
|
||||
---
|
||||
#### 2.4 Start the Wabbajack Install
|
||||
|
||||
### Step 2 - Add ModOrganizer.exe as a Non-Steam Game
|
||||
Once you are ready, click the Play button and the Wabbajack application should start to download all the mods needed for Tuxborn. This will likely take quite a long time - the downloads phase of the process is entirely dependant on your internet connection speed. As mentioned above, Nexus Premium is **strongly recommended**.
|
||||
|
||||
The next step is to add ModOrganizer.exe to Steam as a non-steam game. In Steam, click Games, then "Add a Non-Steam Game to My Library":
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_WabbajackClickPlay.png" width="600">
|
||||
|
||||
|
||||
As a reminder, running Wabbajack on Linux/SteamOS is not a supported method, but we've done what we can to make things work as smoothly as they can. You may encounter crashes, hanging, or need to restart or re-run the Wabbajack application and install process. It also may appear to have hung, but hasn't - This is especially true during the Building BSA's part of the Wabbjack process - please be extra patient here as it takes **a vary log time** on the Steam Deck hardware (See [Additional Notes](https://github.com/Omni-guides/Tuxborn/blob/main/TuxbornSteamDeckFullInstall.md#additionals-notes) for some indication of install times on Steam Deck.)
|
||||
|
||||
### STEP 3 - Post-Wabbajack Steps
|
||||
|
||||
Unlike on Windows, the Wabbajack Installation process is only part of what is needed on SteamDeck/Linux. There are a number of post-install steps that need to be carried out before the modlist is playable. Again, I've done my best to automate this, but there are still a few steps that must be done manually.
|
||||
|
||||
#### 3.1 Add Tuxborn's ModOrganizer.exe to Steam
|
||||
|
||||
**IMPORTANT FOR SD CARD USERS:** Use the `/run/media/mmcblk0p1` path to your SDCard Tuxborn directory in the steps below, and **not** the `/run/media/deck/<SDCARD_NAME>` path. They both point to the same place ultimately, but it makes managing the paths later easier.
|
||||
|
||||
Click the "Add a Non-Steam Game to My Library" option from the Games menu in Steam:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-AddNonSteamGame.png" width="600">
|
||||
|
||||
Click Browse:
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-BrowseNonSteamGame.png" width="600">
|
||||
|
||||
Browse to the path of your modlist. e.g. /home/deck/Games/Skyrim/Tuxborn, select ModOrganizer.exe, and click Open.
|
||||
Browse to the path for Tuxborn, which if you are following my recommendations, should be `/home/deck/Games/Skyrim/Tuxborn`. SDCard users should navigate to, for example `/run/media/mmcblk0p1/Games/Skyrim/Tuxborn`.
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-AddMO2NonSteamGame.png" width="600">
|
||||
|
||||
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
|
||||
Lastly for this step, click "Add Selected Program"
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-AddSelectedMO2NonSteamGame.png" width="600">
|
||||
|
||||
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Tuxborn":
|
||||
#### 3.2 Properties of Tuxborn Steam Entry
|
||||
|
||||
|
||||
When you add ModOrganizer.exe to Steam, it will be added with the name "ModOrganizer.exe" which is both not very helpful, and also won't be detected by my post-install automation script. Right click the "ModOrganizer.exe" entry, and click properties:
|
||||
|
||||
Then in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select the Proton version - I use Proton Experimental which is the current Proton 9 based version provided by Valve at time of writing.
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_WabbajackProton_AddNonSteamPropertiesClick.png" width="300">
|
||||
|
||||
|
||||
In the properties window, give it a more sensible name, I recommend "Skyrim - Tuxborn" - the "Skyrim - " part is particularly important to allow my Script to detect things correctly, so please just go with my recommendation unless you know what you are doing.
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-PropertiesNonSteamGame.png" width="600">
|
||||
|
||||
**IMPORTANT FOR SD CARD USERS** - You must add the following to the Launch Options for the ModOrganizer.exe Non-Steam game, otherwise the Proton environment won't have access to your SD Card contents:
|
||||
|
||||
@@ -103,171 +185,149 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
|
||||
```
|
||||
Like so:
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-STEAM_COMPAT_MOUNTS.png" width="600">
|
||||
|
||||
|
||||
Switch to the Compatibility tab, tick the box for "Force the use of a specific Steam Play compatibility tool", and select "Proton Experimental":
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-ProtonNonSteamGame.png" width="600">
|
||||
|
||||
#### 3.3 Run once and reboot
|
||||
|
||||
To create the Proton Prefix and register Tuxborn with Steam so that this all works, you need to click Play on your Tuxborn entry in Steam, and **whether it loads Mod Organizer 2 successfully or not**, you _must close it down and move on to the next steps_, it will not work if you jump ahead and try to play the game at this stage.
|
||||
|
||||
#### 3.4 Automated Install Script
|
||||
|
||||
To run the required post-install steps automatically, you can run my automation script directly from GitHub [https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/binaries/omni-guides.sh](source) by pasting the following command in a konsole window and following the on-screen instructions:
|
||||
|
||||
`bash <(curl -s https://raw.githubusercontent.com/Omni-guides/Wabbajack-Modlist-Linux/main/binaries/omni-guides.sh)`
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_RunScript.png" width="600">
|
||||
|
||||
A banner and a short note will be displayed, and a request to press any key to continue:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_BannerContinue.png" width="600">
|
||||
|
||||
The script will then attempt to detect any Wabbajack Modlists you have installed and added to Steam - in this case, Tuxborn. Type the corresponding number next to Tuxborn (e.g. 1) and hit enter:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_SelectModlist.png" width="600">
|
||||
|
||||
You will be asked to confirm you want to continue, and the script will move on to detecting the Modlist Install directory - if you are using my recommended directory names and paths, this should be detected automatically. However, if you have called the directory something else, or if multiple possible directories are found, you'll be asked to select the right one. If nothing can be found automatically, you'll be asked to manually input the path to the Modlist directory.
|
||||
|
||||
You will be prompted for your *sudo* password so that various permissions can be set correctly, and the script will continue through more automated tasks:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_SudoPassword.png" width="600">
|
||||
|
||||
Lastly, you will be asked if you want to set the resolution. This is optional but I'm trying to reduce the manual steps as much as I can. If you're running this on a Steam Deck, it will assume the desired resolution is 1280x800 (If you are going to be playing while docked, you will have to manually alter the resolution via MO2 in the "Tuxborn - Settings" -> INI Files -> SSEDisplayTweaks.ini file. See [Additional Notes](https://github.com/Omni-guides/Tuxborn/blob/main/TuxbornSteamDeckFullInstall.md#additionals-notes) below for more information). If you are not running this script on a Steam Deck, you will be asked to input your desired resolution, in the format 1920x1080.
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_SetResolution.png" width="600">
|
||||
|
||||
#### 3.5 With the post-install automation script complete, you now need to REBOOT YOUR STEAM DECK, and then switch back to Desktop Mode for the final part.
|
||||
|
||||
---
|
||||
|
||||
### Step 3 - Install Protontricks
|
||||
### STEP 4 - Profiles, Known Crashes and Launching the game
|
||||
|
||||
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak:
|
||||
#### 4.1 BFCO Gamepad Controls Fix, and Profile selection
|
||||
|
||||
|
||||
Finally, everything should be in place.
|
||||
|
||||
|
||||
If you are not playing the BFCO profiles, you can skip the following step, but if you do plan to use one of the BFCO profiles, due to a clash between RaceMenu, Steam Input and Bethesda "helping", you will need to add `steamdeck=0` to the launch options in Steam:
|
||||
|
||||
To enable the use of protontricks via the command line, open a Konsole terminal and run the following command to add an alias:
|
||||
<img src="https://github.com/Omni-guides/Tuxborn/blob/main/images/Tuxborn_SteamDeck0.png" width="600">
|
||||
|
||||
You should also temporarily map the 'R' key so that you can initiate the Character Naming pop-up during character creation. You could for example map it to one of the back buttons. This is only needed for Character Creation. You can thank Todd for this requirement.
|
||||
|
||||
With that done (or not if you are playing a non-BFCO profile), Start Tuxborn from Steam, and ModOrganizer2 should open.
|
||||
|
||||
Select your desired profile in the top-left of MO2 - as a reminder there are 6 profiles in total, with 4 of them being targeted at the Steam Deck. They are:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Tuxborn/blob/main/images/Tuxborn_SelectProfile.png" width="600">
|
||||
|
||||
**Tuxborn – Deck:** This profile aims for a locked 40FPS experience on the Steam Deck.
|
||||
**Tuxborn - Handheld:** This profile aims for additional visual quality, at the cost of more ram/vram usage. It will work on the Steam Deck, but you will sometimes run into some performance issues. Systems with 24/32GB should be fine.
|
||||
**Tuxborn – Desktop:** This profile is for slightly more powerful PCs, has an expanded Community Shaders suite and higher INI settings. Performance of this profile will depend on your system specs.
|
||||
|
||||
**Tuxborn – Deck BFCO:** This profile aims for a locked 40FPS experience on the Steam Deck, and includes the BFCO Combat Animation Framework.
|
||||
**Tuxborn - Handheld:** This profile aims for additional visual quality, at the cost of more ram/vram usage. It will work on the Steam Deck, but you will sometimes run into some performance issues. Systems with 24/32GB should be fine. Includes the BFCO Combat Animation Framework.
|
||||
**Tuxborn – Desktop BFCO:** This profile is for slightly more powerful PCs, has a full Community Shaders suite, higher INI settings, and includes the BFCO Combat Animation Framework. Performance of this profile will depend on your system specs.
|
||||
|
||||
Once you have made your choice, select it in the Profiles drop down.
|
||||
|
||||
#### 4.2 Launching the game
|
||||
|
||||
Regardless of which profile you want to use you should now, finally, be ready to click play. Unfortunately, there are a couple of 'initial launch' issues that you will need to go through, but once these are out the way, they should never re-appear.
|
||||
|
||||
First point to note is the 'Unlock' button that will appear shortly after you click Play. Never, ever (ever) click the Unlock button.
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_UnlockButton.png" width="600">
|
||||
|
||||
⚠️ ❗ UNDER NO CIRCUMSTANCES PRESS THE “UNLOCK” BUTTON WHEN YOU HAVE LOADED SOMETHING THROUGH MOD-ORGANIZER.
|
||||
YOU WILL BREAK MANY MANY THINGS. DO NOT PRESS THE BUTTON! ⚠️ ❗
|
||||
|
||||
Second thing to note, is the time it takes to boot the game. It takes a long, long (long) time to boot the game on Steam Deck. This has only been made worse with some recent changes to SteamOS. It can literally take 7-8 minutes for the game to fully launch on Steam Deck (See [Additional Notes](https://github.com/Omni-guides/Tuxborn/blob/main/TuxbornSteamDeckFullInstall.md#additionals-notes) for some examples of timings). Rest assured we are looking into any possible way we can reduce this because it's a massive pain in the... Anyway, as soon as we have anything that will help reduce this loading time, we will implement it. Running Tuxborn from SDCard will only make this initial load time worse, but it _will get there_, and regardless of internal storage or SD Card, once it's loaded, it will be fine.
|
||||
|
||||
Thirdly, there are a series of crashes the first few times you launch the game. This is something to do with running Tuxborn via Proton. Again, we are actively looking into anything we can do to reduce or remove the couple of crashes the first few times you launch Tuxborn.
|
||||
|
||||
The very first launch will likely crash fairly early, during the shader compilation. The second launch will take care of the initial Shader Cache building, and will again **take a very long time**. This should be a one-off though, so just let it complete. It will likely crash again at the end of that process.
|
||||
|
||||
Finally, though, things will start to smooth out. However, while the game is loading, the main menu background may be incredibly weird colours, e.g:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_MainMenuCorruptColours.png" width="600">
|
||||
|
||||
This is caused by a different shader building process, and it will sort itself out when the game fully launches, and hopefully will stop happening after the first few launches.
|
||||
|
||||
I recommend that the first time you make it to character generation, you check if you can name your character (but don't accept it) if you cannot type in the Name Character box, then restart one last time (even use this as a chance to switch back to Game Mode)
|
||||
|
||||
Finally (finally), Tuxborn should now boot to the main menu options, no more crashes, no more nonsense. Once you reach this stage where things are settled, exit the game and switch back to Game Mode on the deck, and get playing!
|
||||
|
||||
### Additional Notes
|
||||
|
||||
#### Install times with various storage combinations
|
||||
I did some testing on my LCD Steam Deck to see how long a full Tuxborn install took to complete. This **doesn't** include the time to download all mods, because that is entirely dependant on your internet speed.
|
||||
|
||||
Tuxborn Wabbajack Deck Install times:
|
||||
|
||||
```
|
||||
echo "alias protontricks='flatpak run com.github.Matoking.protontricks'" >> ~/.bashrc
|
||||
Internal Storage Install Diretory AND Downloads Directory: 4 Hours 6 Minutes
|
||||
Internal Storage Install Directory and SDCard Downloads Directory: 2 Hours 26 Minutes
|
||||
Internal Storage Downloads Directory and SDCard Install Directory: 8 Hours 10 Minutes
|
||||
SDCard Install Directory and Downloads Directory: 10 Hours 31 minutes
|
||||
```
|
||||
|
||||
then close and reopen Konsole. We can now invoke protontricks from the command line. Next, we need to allow protontricks access to the filesystem location (adjust as needed if you used a different path):
|
||||
As you can see, it can take a long time to complete the install using the Deck hardware alone, with the fastest options being having the Install Directory on Internal Storage, and Downloads on SDCard, or both Install Directory and Downloads Directory being on the Internal Storage.
|
||||
|
||||
#### Tuxborn Launch times with different Profiles
|
||||
|
||||
**These numbers need updated for 1.0**
|
||||
|
||||
As mentioned in the main body of this guide, it can take a long time for Tuxborn to fully load on the Steam Deck hardware. To give you an idea of differences between the profiles and storage, I ran some tests:
|
||||
|
||||
```
|
||||
sudo flatpak override com.github.Matoking.protontricks --filesystem=/home/deck/Games
|
||||
Tuxborn Deck boot NVMe: 9m32s
|
||||
Tuxborn Deck CS boot NVMe: 10m54s
|
||||
|
||||
TuxBFCO Deck boot NVMe: 9m45s
|
||||
TuxBFCO Deck CS boot NVMe: 10m58s
|
||||
```
|
||||
|
||||
That should be protontricks installed and ready to use later in the guide.
|
||||
It would be interesting to see if anyone has vastly different timings from the above.
|
||||
|
||||
#### Changing Resolution or removing the 82FPS hard cap
|
||||
|
||||
---
|
||||
If you are not playing on Steam Deck and wish to change the configured resolution, you can do this from MO2. Filter for the entry for "Tuxborn - Settings", and double-click it:
|
||||
|
||||
### Step 4 - Start and Configure ModOrganizer2
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-SSEDisplayTweaks.png" width="600">
|
||||
|
||||
Click play on this new entry "Skyrim - Tuxborn" (or whatever you renamed it to) in Steam - Depending on the path on Windows that you copied the Modlist files from, you may see an error pop-up about your account lacking permission:
|
||||
Switch to the INI Tab, highlight the "SSEDisplayTweaks.ini" file on the left, and then scroll down on the right side of the window until you see the line that reads something like "Resolution=1280x800". Remove the # at the start of the line if one exists, and then set the resolution to be your desired resolution, e.g. "Resolution=1920x1080":
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-SetResolution.png" width="600">
|
||||
|
||||
|
||||
|
||||
To fix this, we just need to strip the now incorrect download directory from the ModOrganizer.ini file. in Konsole terminal, run:
|
||||
Similarly, the FrameLimit (FPS limit) can be adjusted by editing the line:
|
||||
|
||||
```
|
||||
sed -i "/download_directory/c\download_directory =" /home/deck/Games/Skyrim/Tuxborn/ModOrganizer.ini
|
||||
FramerateLimit = 82
|
||||
```
|
||||
|
||||
then re-run "Skyrim - Tuxborn" from Steam.
|
||||
Once configured how you want, click the Close button and select "Yes" to save the changes.
|
||||
|
||||
Another error box will appear, complaining that it "Cannot open instance 'Portable'. This is because we copied the Modlist directory (inclusive of the built-in MO2) from Windows, so the path has changed:
|
||||
|
||||
|
||||
|
||||
To fix this, we need to point MO2 to our new location. Click OK, and then Browse. The path we are looking for is:
|
||||
|
||||
```
|
||||
Z:\home\deck\Games\Skyrim\Tuxborn\Game Root
|
||||
```
|
||||
|
||||
If you installed Tuxborn to an SD Card or a different Library location, then you will have to browse to that location, or the equivalent SD Card path in /run/media/mmcblk0p1, which will be mounted inside Proton as the E: Drive.
|
||||
|
||||
|
||||
|
||||
The splash screen for Tuxborn should hopefully now appear:
|
||||
|
||||
|
||||
|
||||
You may also get a pop-up asking if you want to Register for handling nxm links, like so:
|
||||
|
||||
|
||||
|
||||
I usually just hit "Yes" and move on with my life.
|
||||
|
||||
Getting close now. Next, we have to ensure that ModOrganizer2 is pointing to the correct location for the required executable. In MO2, click the little two-cog icon at the top, which will bring up the Modify Executables window (please note that this icon may differ for some Modlists that use custom icon sets):
|
||||
|
||||
|
||||
|
||||
|
||||
For the Tuxborn executable, we need to point MO2 to the skse64_loader.exe file contained within the Tuxborn Modlist directory.
|
||||
|
||||
The path you need for the Tuxborn application will be:
|
||||
|
||||
```
|
||||
Z:\home\deck\Games\Skyrim\Tuxborn\mods\Skyrim Script Extender\Root\skse64_loader.exe
|
||||
```
|
||||
|
||||
|
||||
|
||||
If you installed Tuxborn to an SD Card, then you will have to replace with the above with the equivalent path in /run/media/mmcblk0p1.
|
||||
|
||||
---
|
||||
|
||||
### Step 5 - Install Required Wine Additions
|
||||
|
||||
There is an issue with missing NPC Voices - apparently this is an issue with Proton, so it may ultimately be resolved in time with a newer version of Proton without needing these steps. For now though, we need to install xact and xact_x64 to the Wine/Proton environment Steam created for our "Skyrim - Tuxborn" entry, and a few others for the use of Community Shaders. Tuxborn also requires Microsoft Visual C++ Redistributable 2022 for some of it's mods.
|
||||
|
||||
The easiest way to install what we need is to use ProtonTricks, which should be installed already from Step 3 earlier in this guide.
|
||||
|
||||
Adding the required packages can be done via the ProtonTricks gui, but perhaps the easiest way is via command line. You can run the following one-liner to do it for you, or if you prefer, you can manually run the individual steps noted below (replace "Skyrim - Tuxborn" with the name of your Non-steam game entry, if you called it something else):
|
||||
|
||||
```
|
||||
APPID=`protontricks -l | grep -i "Skyrim - Tuxborn" | awk {'print $NF'} | sed 's:^.\(.*\).$:\1:'` ; protontricks --no-bwrap $APPID -q xact xact_x64 d3dcompiler_47 d3dx11_43 d3dcompiler_43 vcrun2022 dotnet6 dotnet7
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### Step 6 - Set Resolution
|
||||
|
||||
Next, we should set the resolution so that the deck isn't doing more work than it needs to. There's no point in asking Skyrim to render at 1440p, and then have the game squeezed into an 800p screen on the deck. To do this in MO2, filter for the entry for "Tuxborn - Settings", and double-click it:
|
||||
|
||||
|
||||
|
||||
Switch to the INI Tab, highlight the "SSEDisplayTweaks.ini" file on the left, and then scroll down on the right side of the window until you see the line that reads "#Resolution=1920x1080". Remove the # at the start of the line, and then set the resolution to be 1280x800:
|
||||
|
||||
|
||||
|
||||
Finally, click the Close button and select "Yes" to save the changes.
|
||||
|
||||
---
|
||||
|
||||
### Step 7 - Direct Launch from Steam (Optional)
|
||||
|
||||
If you are not planning to make any further changes to the modlist via MO2, you can add the following to the launch options in steam for Tuxborn, so that the modlist will launch directly, skipping MO2 when you click play in Steam:
|
||||
|
||||
|
||||
```
|
||||
'moshortcut://Tuxborn'
|
||||
```
|
||||
e.g.
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_MO2DirectLaunch.png" width="600">
|
||||
|
||||
If you then in future need to make any changes to the modlist via MO2, just remove the launch options again.
|
||||
|
||||
---
|
||||
|
||||
### Step 8 - CryoUtilities changes (Steam Deck only, Required!)
|
||||
|
||||
Increase Steam Deck Swap Space, Swappiness and adjust Steam Deck VRAM
|
||||
|
||||
Due to the number and complexity of mods in this modlist, Staam Deck users *must* apply the CryoUtilites recommended changes to VRAM, Swap Space, and swappiness. How to do so is outside the scope of this guide, but there is plenty of information available elsewhere on how to do it - [CryoByte33](https://github.com/CryoByte33/steam-deck-utilities) has an excellent set of utilities available on github that can take care of this, and more!
|
||||
|
||||
Personally I have increased the VRAM in the deck bios to 4GB (see [here](https://www.youtube.com/watch?v=od9_a1QQQns&t=1377s) for details), 16GB Swap space, and a Swappiness of 1 - the recommended settings when you run Cryobyte33's Steam Deck Utilities. In fact, the [full video](https://www.youtube.com/watch?v=od9_a1QQQns) of Cryobyte33 explaining what this all means, is definitely worth a watch!
|
||||
|
||||
---
|
||||
|
||||
### Conclusion
|
||||
|
||||
At last!
|
||||
|
||||
If you've read this far, then well done! I'd very much appreciate a Star for this guide, just to show if I'm on the right track. I'm also open to any feedback, positive or negative.
|
||||
|
||||
With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Select your desired profile in MO2, then Click the Play button in Mod Organizer, and wait....
|
||||
|
||||
|
||||
|
||||
This takes quite a bit of time to start. Once it has loaded though, performance should be as expected in the menus. On first launch, you will see a message about Shaders being compiled, this is normal and just allow it to finish before continuing. It is also very common for the modlist to _crash the first time you launch it_, especially with an error message regarding the "Blunt and Blade" mod. Relaunching the game should fix this and you'll not see the error, or a crash, again.
|
||||
|
||||
|
||||
|
||||
In some rare cases, I have seen the game not accept input when trying to press 'R' or the 'X' button when naming your character the first time you successfully launch the game. Again a restart of the game appears to fix this. If you get into this situation, save your generated character as a preset (from the Preset tab in the top right), exit and relaunch Tuxborn, then load your Character Preset (again using the Preset tab in the top right) - I haven't yet got to the bottom of why this happens as yet, but will try to figure it out.
|
||||
|
||||
On Steam Deck, use either the Tuxborn - Deck profile and lock the framerate at 40FPS, or the Tuxborn - Deck CS profile and lock the framerate at 30FPS. I find sticking it at 40 or 30 depending on the profile, and then turning off the FPS counter lets me just get on with the game, feeling fluid enough that I don't think about the FPS any more.
|
||||
|
||||
Keep in mind that you are running a collection of mods, through the Proton compatibility layer - so save often, and maybe even make backups of your save-games, just in case ;)
|
||||
|
||||
If you need help with any of the above, you can seek support from the #txbn-support channel of the [Aetherius Modding Discord](https://discord.gg/xRrHRsb5e9).
|
||||
|
||||
Enjoy!
|
||||
|
||||
[](https://ko-fi.com/D1D8H8WBD)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user