noctra/Jackify
1
0
Fork 0
mirror of https://github.com/Omni-guides/Jackify.git synced 2026-01-17 19:47:00 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updating the Tuxborn guide ready for launch.

Omni-guides
2024-03-27 20:04:29 +00:00
parent de8940d188
commit 94a2ebf31e
1 changed files with 27 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
Skyrim:-Tuxborn.md

@@ -1,16 +1,26 @@
![Tuxborn Banner](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn_Banner.png)
[Tuxborn DESC](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/) _ToDo decription of modlist_
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._
[![ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/D1D8H8WBD)
**THIS GUIDE IS UNFINISHED AND COMING SOON**
---
## 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).
---
## Instructions
**The following has been tested on Tuxborn MODLIST VERSION**
**The following has been tested on Tuxborn 0.1.0**
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.1130), and have launched the vanilla Skyrim game at least once. I also assume that you have set a user password on the Steam Deck.
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.
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.
@@ -18,7 +28,7 @@ The steps below may seem wordy and plentiful, but they can be carried out relati
### 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 Konsole terminal and run **only one** of the following, depending on where you want to store the Modlist:
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:
Create Directory on **Internal Storage**:
```
@@ -82,7 +92,7 @@ Once added, edit the properties of the new ModOrganizer.exe entry. You can give
![IMAGE PropertiesNonSteamGame](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-PropertiesNonSteamGame.png)
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 8.0-4 which was the latest stable Proton version provided by Valve at time of writing.
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 current Proton 9 based version provided by Valve at time of writing.
![IMAGE ProtonNonSteamGame](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-ProtonNonSteamGame.png)
@@ -147,7 +157,7 @@ To fix this, we need to point MO2 to our new location. Click OK, and then Browse
Z:\home\deck\Games\Skyrim\Tuxborn\Game Root
```
If you installed vanilla Skyrim 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.
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.
![IMAGE BrowseLocalBlur](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-BrowseLocalBlur.png)
@@ -166,7 +176,7 @@ Getting close now. Next, we have to ensure that ModOrganizer2 is pointing to the
![IMAGE MO2ExecutableCog](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-MO2ExecutablesCog.png)
For the Tuxborn executable, we need to point MO2 at a file that may not actually exist yet (but it will exist, once Rootbuilder does it's thing when you click launch - and is then removed again when the game closes).
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:
@@ -176,7 +186,7 @@ Z:\home\deck\Games\Tuxborn\mods\Skyrim Script Extender\Root\skse64_loader.exe
![IMAGE MO2Executables](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-MO2Executables.png)
If you installed vanilla Skyrim to an SD Card, then you will have to replace with the above with the equivalent path in /run/media/mmcblk0p1.
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.
---
@@ -189,24 +199,14 @@ The easiest way to install what we need is to use ProtonTricks, which should be
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 xact xact_x64 d3dx11_43 d3dcompiler_47 d3dcompiler_43
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
```
Alternatively, **If you prefer to run this manually**, see an alternative step-by-step method in the **Additional Notes** section below.
---
### Step 6 - Install VCREDIST2022
Next up is the requirement of vcredist2022. Unfortunately this isn't available directly through protontricks as per xact, so we will have to install it semi-manually. The following one-liner should do everything you need (replace "Skyrim - Tuxborn" with the name of your Non-steam game entry, if you called it something else):
```
APPID=`protontricks -l | grep -i "Tuxborn" | awk {'print $NF'} | sed 's:^.\(.*\).$:\1:' | tail -1` ; wget https://aka.ms/vs/17/release/vc_redist.x64.exe -O '/home/deck/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' ; protontricks --no-bwrap -c 'wine /home/deck/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe /Q' $APPID
```
---
### Step 7 - Set Resolution
### 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 "SSE Display Tweaks", and double-click it:
@@ -220,7 +220,7 @@ Finally, click the Close button and select "Yes" to save the changes.
---
### Step 8 - Optional but Recommended
### Step 7 - Optional but Recommended
Increase Steam Deck Swap Space, Swappiness and adjust Steam Deck VRAM
@@ -234,17 +234,17 @@ 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! Click the Play button in Mod Organizer, and wait....
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....
![IMAGE MO2Play.png](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-MO2Play.png)
This takes quite a bit of time to start. Once it had loaded though, performance was 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.
This takes quite a bit of time to start. Once it had loaded though, performance was 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_. Subsequent launches should be fine.
![IMAGE CompilingShaders.png](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-CompilingShaders.png)
On Steam Deck, I limit FPS and Refresh rate to 40, and it does a pretty good job of maintaining that. If you want absolutely no fluctuations at all, you'd likely have to lock to 30fps, but I find sticking it at 40Hz/FPS, 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.
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.
As an addition to the disclaimer at the top of this guide, I have no visibility of longer term stability, so save often, and maybe even make backups of your save-games, just in case ;)
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, or better yet have another fix, tweak or workaround to help get these Modlists running on Linux, then please do stop by the #unofficial-linux-help channel on the Wabbajack Discord, I should be around so just @ me (@omni) on there!
@@ -326,7 +326,7 @@ Non-Steam shortcut: Skyrim - Tuxborn (3595949753)
With the AppID now known, install the required xact and xact_x64 packages into this Proton environment (use your own AppID from the command above):
```
protontricks --no-bwrap 3595949753 xact xact_x64 d3dx11_43 d3dcompiler_47 d3dcompiler_43
protontricks --no-bwrap 3595949753 xact xact_x64 d3dcompiler_47 d3dx11_43 d3dcompiler_43 vcrun2022 dotnet6 dotnet7
```
This may take a little time to complete, but just let it run the course. Your terminal may misbehave after running the protontricks/wine command - you can regain control by typing 'reset', even if you can't see the characters as you type.