+
+
Next, start Enderal and from the Launcher, load into the Main Menu of the game, and then exit.
@@ -83,9 +83,9 @@ sudo chmod -R 755 /run/media/mmcblk0p1/Games/Enderal/EmissariesOfTux
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak:
-
+
-
+
To enable the use of protontricks via the command line, open a Konsole terminal and run the following command to add an alias:
@@ -109,15 +109,15 @@ That should be protontricks installed and ready to use later in the guide.
This method of running an Enderal modlist uses steamtinkerlaunch. To get steamtinkerlaunch installed and available in Steam, we can use a program called ProtonUp-QT. If you don't already have this installed, you can install it via the Discover store on Steam Deck, or likely from your package manager on general Linux systems.
-
+
Once installed, open up ProtonUp-QT from the applications menu, ensure Steam is selected at the top, and then click Add Version:
-
+
In the "Compatibility tool" drop down, select steamtinkerlaunch if you are on Steam Deck, or steamtinkerlaunch-git if you are on a general Linux system, and then click Install:
-
+
Once the download completes, you can close ProtonUp-QT.
@@ -159,46 +159,46 @@ protontricks --no-bwrap 976620 -q xact xact_x64 d3dcompiler_47 d3dx11_43 d3dcomp
With the above component install complete, we can now switch Enderal to use steamtinkerlaunch instead of Proton Experimental, in the properties of the game in Steam:
-
+
Close the properties window and launch the game from steam. However, instead of loading Enderal, this will load a SteamTinkerLaunch window, and you'll have to **quickly** click on "Main Menu" down the bottom:
-
+
On the next screen, click "Game Menu":
-
+
There are only a few changes needed to get things working. Firstly, ensure 'custom commands' is ticked, and then click the executable to change it, bringing up a file Browser:
-
+
Browse to your Emissaries of Tux modlist directory, and select ModOrganizer.exe:
-
+
Additionally, tick the checkbox next to "Only custom command". The window should now look like this:
-
+
Lastly, scroll down in the Steam Tinker Launch window until you see 'Proton Version', and change it to be "Proton Experimental":
-
+
Click Save and Play, and all being well, you should see the Emissaries of Tux splash screen, and then MO2 will be displayed:
-
+
### Step 8 - Launch MO2 and configure the instance.
As MO2 starts to launch for the first time, you may see an error regarding being unable to open the instance:
-
+
Click OK, and then click "Browse":
-
+
Navigate to the path for the vanilla Enderal directory - On Steam Deck, for **Internal Storage** this will be:
@@ -220,7 +220,7 @@ sed -i "/download_directory/c\download_directory =" /home/deck/Games/Enderal/Emi
At this stage, finally, ModOrganizer2 should now be loaded successfully. We need to check the executable path is correct for the Emissaries entry in MO2. To do so, click the "Configure Executables" button:
-
+
Ensure that the executable paths for the "Enderal Special Edition (SKSE)" entry to match the following. If you are on a general Linux system, adjust the paths as necessary to your Steam Library location.
@@ -236,7 +236,7 @@ with a "Start in" path:
Z:\home\deck\.local\share\Steam\steamapps\common\Enderal Special Edition
```
-
+
If Enderal is installed on the SDCard, the Binary Path should be:
@@ -252,7 +252,7 @@ with a "Start in" path:
D:\SteamLibrary\steamapps\common\Enderal Special Edition\
```
-
+
Lastly for this step, click the Apply button, followed by OK.
@@ -264,7 +264,7 @@ Lastly for this step, click the Apply button, followed by OK.
It's finally time to play! Set the Launch option in MO2 back to Enderal Special Edition (SKSE), and click Play:
-
+
If you're not playing on Steam Deck, that should be things complete, and you can move to the Conclusion section.
@@ -302,4 +302,4 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
diff --git a/FNVTemp.md b/FNVTemp.md
index 28f11e6..719e231 100644
--- a/FNVTemp.md
+++ b/FNVTemp.md
@@ -1,4 +1,4 @@
-
+
# Begin Again
@@ -28,19 +28,19 @@ With Fallout New Vegas installed on your system, and the whole Wabbajack and TTW
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":
-
+
Click Browse:
-
+
Browse to the path of your modlist. e.g. /home/deck/Games/Fallout/BeginAgain, select ModOrganizer.exe, and click Open.
-
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
---
@@ -50,11 +50,11 @@ Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Progr
Once added, edit the properties of the new ModOrganizer.exe entry. Rename the new Steam entry to be "FNV - Begin Again" (for my automated post-install script that you will use later to function, the Steam entry must start "FNV - " to be picked up correctly):
-
+
Then, in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select "Proton - Experimental".
-
+
**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:
@@ -64,7 +64,7 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
Like so:
-
+
Close the properties window, and click play on FNV - Begin Again entry in Steam. This should start Mod Organizer. Once it opens, CLOSE IT DOWN AGAIN. This step is critical as it creates the prefix for the modlist entry, but we're not ready to play the modlist just yet.
@@ -126,7 +126,7 @@ cd "/home/deck/.local/share/Steam/steamapps/common/Fallout New Vegas"
It should output that the file was patched successfully.
-
+
---
@@ -154,7 +154,7 @@ STEAM_COMPAT_DATA_PATH="/run/media/mmcblk0p1/steamapps/compatdata/22380" STEAM_C
It should look something like so:
-
+
## Step 6 - Click Play!
@@ -182,4 +182,4 @@ If you need help with any of the above, or better yet have another fix, tweak or
**Enjoy!**
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/Fallout-4:-Welcome-to-Paradise.md b/Fallout-4:-Welcome-to-Paradise.md
index 84fd5ef..0f7175a 100644
--- a/Fallout-4:-Welcome-to-Paradise.md
+++ b/Fallout-4:-Welcome-to-Paradise.md
@@ -1,4 +1,4 @@
-
+
[Welcome To Paradise](https://thephoenixflavour.com/fo4/wtp/introduction/) _is a lightweight, performance-friendly Wabbajack list offering improved graphics and gameplay mechanics without drastically changing the feel of the game. Originally published in 2020, WTP is a polished experience with many custom modifications including hand-picked texture packs and my own sorting overhaul._
@@ -78,27 +78,27 @@ sudo chmod -R 755 /run/media/mmcblk0p1/Games/Fallout/WelcomeToParadise
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":
-
+
Click Browse:
-
+
Browse to the path of your modlist. e.g. /home/deck/Games/Fallout/WelcomeToParadise, select ModOrganizer.exe, and click Open.
-
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Fallout - Welcome to Paradise":
-
+
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.
-
+
**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:
@@ -107,7 +107,7 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
```
Like so:
-
+
---
@@ -115,9 +115,9 @@ Like so:
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak:
-
+
-
+
To enable the use of protontricks via the command line, open a Konsole terminal and run the following command to add an alias:
@@ -147,7 +147,7 @@ With this setting now in place, MO2 will have visibility of the required .local
Click play on this new entry "Fallout - Welcome to Paradise" (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:
-
+
To fix this, we just need to strip the now incorrect download directory from the ModOrganizer.ini file. in a Konsole terminal, run:
@@ -159,7 +159,7 @@ then re-run "Fallout - Welcome to Paradise" from Steam.
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:
@@ -169,21 +169,21 @@ Z:\home\deck\.local\share\Steam\steamapps\common\Fallout 4
If you installed vanilla Fallout 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 Welcome to Paradise 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 Welcome to Paradise 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).
@@ -193,7 +193,7 @@ The path you need for the Welcome to Paradise application will be:
Z:\home\deck\.local\share\Steam\steamapps\common\Fallout 4\f4se_loader.exe
```
-
+
If you installed vanilla Fallout to an SD Card, then you will have to replace with the above with the equivalent path in /run/media/mmcblk0p1.
@@ -229,11 +229,11 @@ APPID=`protontricks -l | grep -i "Fallout - Welcome to Paradise" | awk {'print $
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 Fallout 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 "High FPS Physics Fix - WTP Settings", and double-click it:
-
+
Switch to the INI Tab, highlight the INI File on the left, and then add a line that reads "Resolution=1280x800":
-
+
Finally, click the Close button and select "Yes" to save the changes.
@@ -245,11 +245,11 @@ While ENB can work under Linux, it is likely going to badly impact performance o
To disable ENB for Welcome to Paradise, we just need to disable "ENBSeries - Binaries" mod entry under the "Root Folder" category in MO2:
-
+
It's also a good plan to make sure that there are no Game Root leftovers. Click the Tools menu at the top of MO2, then select Tool Plugins, Root Builder, then Clear:
-
+
---
@@ -257,7 +257,7 @@ It's also a good plan to make sure that there are no Game Root leftovers. Click
The MCM Booster mod causes a full game crash when entering MCM via the in-game menu. Given that this is just there to try and speed up the loading of MCM menus, it should be safe to disable without impacting gameplay. Search for it in MO2, and then simply uncheck the box:
-
+
---
@@ -277,7 +277,7 @@ If you've read this far, then well done! I'd very much appreciate a Star for thi
With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Click the Play button in Mod Organizer, and wait....
-
+
This takes quite a bit of time to start. Once it had loaded though, performance was as expected in the menus.
@@ -291,7 +291,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
@@ -312,11 +312,11 @@ If you prefer to install vcredist manually instead of using my one-liner, you ca
APPID=`protontricks -l | grep -i "Fallout - Welcome to Paradise" | 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' $APPID
```
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
Alternatively, **If you prefer to run this manually, step-by-step**, you can do the following. Firstly, we need to download the vc_redist.x64.exe installer inside the Proton prefix. Run the following command, replacing my Game ID (3595949753) with your own which you can get by running protontricks -l in Konsole:
@@ -338,13 +338,13 @@ Finally, run the installer:
wine vc_redist.x64.exe
```
-
+
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
When running wine commands in Konsole, it usually mangles the terminal a bit - text you type wont be shown (though it technically is still being printed in the terminal) - to get out of that state, either close and reopen Konsole, or just type 'reset' and hit enter, even if you can't see the characters.
diff --git a/Fallout-NV:-Begin-Again.md b/Fallout-NV:-Begin-Again.md
index 28f11e6..214768c 100644
--- a/Fallout-NV:-Begin-Again.md
+++ b/Fallout-NV:-Begin-Again.md
@@ -1,4 +1,4 @@
-
+
# Begin Again
@@ -28,19 +28,19 @@ With Fallout New Vegas installed on your system, and the whole Wabbajack and TTW
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":
-
+
Click Browse:
-
+
Browse to the path of your modlist. e.g. /home/deck/Games/Fallout/BeginAgain, select ModOrganizer.exe, and click Open.
-
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
---
@@ -50,11 +50,11 @@ Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Progr
Once added, edit the properties of the new ModOrganizer.exe entry. Rename the new Steam entry to be "FNV - Begin Again" (for my automated post-install script that you will use later to function, the Steam entry must start "FNV - " to be picked up correctly):
-
+
Then, in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select "Proton - Experimental".
-
+
**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:
@@ -64,7 +64,7 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
Like so:
-
+
Close the properties window, and click play on FNV - Begin Again entry in Steam. This should start Mod Organizer. Once it opens, CLOSE IT DOWN AGAIN. This step is critical as it creates the prefix for the modlist entry, but we're not ready to play the modlist just yet.
@@ -126,7 +126,7 @@ cd "/home/deck/.local/share/Steam/steamapps/common/Fallout New Vegas"
It should output that the file was patched successfully.
-
+
---
@@ -154,7 +154,7 @@ STEAM_COMPAT_DATA_PATH="/run/media/mmcblk0p1/steamapps/compatdata/22380" STEAM_C
It should look something like so:
-
+
## Step 6 - Click Play!
@@ -182,4 +182,4 @@ If you need help with any of the above, or better yet have another fix, tweak or
**Enjoy!**
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/Fallout-NV:-Capital-Punishment.md b/Fallout-NV:-Capital-Punishment.md
index f20d7e2..ddeb13b 100644
--- a/Fallout-NV:-Capital-Punishment.md
+++ b/Fallout-NV:-Capital-Punishment.md
@@ -1,5 +1,5 @@
-
+
+
Next, start Fallout New Vegas and from Steam, click Play in the Launcher to load into the Main Menu of the game, and then exit. This is required to generate some necessary files in the background.
@@ -87,9 +87,9 @@ sudo chmod -R 755 /run/media/mmcblk0p1/Games/Fallout/CapitalPunishment
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak:
-
+
-
+
If this is the first time you have used protontricks or installed a Wabbajack Modlist, you may need to enable the use of protontricks via the command line. Open a Konsole terminal and run the following command to add an alias:
@@ -113,15 +113,15 @@ That should be protontricks installed and ready to use later in the guide.
This method of running a Fallout New Vegas modlist uses steamtinkerlaunch. To get steamtinkerlaunch installed and available in Steam, we can use a program called ProtonUp-QT. If you don't already have this installed, you can install it via the Discover store on Steam Deck, or likely from your package manager on general Linux systems.
-
+
Once installed, open up ProtonUp-QT from the applications menu, ensure Steam is selected at the top, and then click Add Version:
-
+
In the "Compatibility tool" drop down, select steamtinkerlaunch if you are on Steam Deck, or steamtinkerlaunch-git if you are on a general Linux system, and then click Install:
-
+
Once the download completes, you can close ProtonUp-QT.
@@ -188,7 +188,7 @@ cd /home/deck/.local/share/Steam/steamapps/common/Fallout\ New\ Vegas\ ; ./Fallo
```
It should output that the file was patched successfully:
-
+
---
@@ -197,35 +197,35 @@ It should output that the file was patched successfully:
With the above component install complete, we can now switch Fallout: New Vegas to use steamtinkerlaunch instead of Proton Experimental, in the properties of the game in Steam:
-
+
Close the properties window and launch the game from steam. However, instead of loading Fallout: New Vegas, this will load a SteamTinkerLaunch window, and you'll have to **quickly** click on "Main Menu" down the bottom:
-
+
On the next screen, click "Game Menu":
-
+
There are only a few changes needed to get things working. Firstly, ensure 'custom commands' is ticked, and then click the executable to change it, bringing up a file Browser:
-
+
Browse to your Capital Punishment modlist directory, and select ModOrganizer.exe:
-
+
Additionally, tick the checkbox next to "Only custom command". The window should now look like this:
-
+
Lastly, scroll down in the Steam Tinker Launch window until you see 'Proton Version', and change it to be "Proton Experimental":
-
+
Click Save and Play, and all being well, you should see the Capital Punishment splash screen, and then MO2 will be displayed:
-
+
---
@@ -241,7 +241,7 @@ sed -i "/download_directory/c\download_directory =" /home/deck/Games/Fallout/Cap
At this stage, finally, ModOrganizer2 should now be loaded successfully. We need to check the executable path is correct for the Capital Punishment entry in MO2. To do so, click the "Configure Executables" button:
-
+
Ensure that the executable paths for the "Capital Punishment"" entry to match the following. If you are on a general Linux system, adjust the paths as necessary to your Steam Library location.
@@ -257,7 +257,7 @@ with a "Start in" path:
Z:\home\deck\.local\share\Steam\steamapps\common\Fallout New Vegas
```
-
+
If Fallout New Vegas is installed on the SDCard, the Binary Path should be:
@@ -272,7 +272,7 @@ with a "Start in" path:
D:\SteamLibrary\steamapps\common\Fallout New Vegas\
```
-
+
Lastly for this step, click the Apply button, followed by OK.
@@ -284,13 +284,13 @@ Lastly for this step, click the Apply button, followed by OK.
You may get a warning about some missing ini files:
-
+
This is expected and you can just click OK.
You **must also disable** the 'dxvk' mod in MO2 otherwise the game will crash when you try to launch it:
-
+
Lastly, copy the supplied save games into the right place, as detailed in the Capital Punishment installation guide. You may need to adjust the paths shown if you used something different, and remember to copy the right save games for your preference of Casual or Hardcore:
@@ -303,7 +303,7 @@ cp -r /home/deck/Games/Fallout/CapitalPunishment/Game\ Folder\ Files/2.\)\ Casua
It's finally time to play! Set the Launch option in MO2 back to Capital Punishment, and click Play:
-
+
If you're not playing on Steam Deck, that should be things complete, and you can move to the Conclusion section.
@@ -341,4 +341,4 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
diff --git a/General-Linux-Guide-(Anvil).md b/General-Linux-Guide-(Anvil).md
index 286bf07..5584801 100644
--- a/General-Linux-Guide-(Anvil).md
+++ b/General-Linux-Guide-(Anvil).md
@@ -1,5 +1,5 @@
-
+
+
Click Browse:
-
+
Browse to the path of your modlist. e.g. /home/omni/Games/Skyrim/Anvil, select ModOrganizer.exe, and click Open.
-
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Anvil":
-
+
Then in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select the Proton version - It's important to pick Proton Experimental here so that it uses Proton 9.
-
+
---
@@ -105,11 +105,11 @@ Then in the Compatibility tab tick the box for 'Force the use of a specific Stea
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak, and is likely also available from your distribution's package manager. Personally I use the version from flatpak/Discover Store:
-
+
Click the Protontricks entry, and then click the Install button in the top right.
-
+
To enable the use of protontricks via the command line, open a Konsole terminal and run the following command to add an alias(If you use a shell other than bash, you will have to adapt the following for your own login script location):
@@ -133,7 +133,7 @@ That should be protontricks installed and ready to use later in the guide.
Click play on this new entry "Skyrim - Anvil" (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:
-
+
To fix this, we just need to strip the now incorrect download directory from the ModOrganizer.ini file. in Konsole terminal, run:
@@ -145,7 +145,7 @@ then re-run "Skyrim - Anvil" from Steam.
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:
@@ -154,21 +154,21 @@ Z:\home\omni\Games\Skyrim\Anvil\Game Root
```
-
+
The splash screen for Anvil 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:
-
+
For the Anvil 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).
@@ -178,7 +178,7 @@ The path you need for the Anvil executable will be:
Z:\home\omni\Games\Skyrim\Anvil\mods\Skyrim Script Extender (SKSE64)\Root\skse64_loader.exe
```
-
+
---
@@ -206,11 +206,11 @@ Alternatively, **If you prefer to run this manually**, see an alternative step-b
Next, we should set the resolution to match your monitor resolution. To do this in MO2, filter for the entry for "Display Tweaks - ANVIL Tweaks", and double-click it:
-
+
Switch to the INI Tab, highlight the INI File on the left, and then scroll down until you see the line that reads "#Resolution=1920x1080". Remove the # at the start of the line, and then set the resolution to be what you need:
-
+
Finally, click the Close button and select "Yes" to save the changes. Optionally, you can also set an FPS limit by editing the FramerateLimit line, e.g "FramerateLimit = 60", or whatever your target FPS is.
@@ -226,7 +226,7 @@ If you've read this far, then well done! I'd very much appreciate a Star for thi
With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Click the Play button in Mod Organizer, and wait.... This takes quite a bit of time to start. Once it had loaded though, performance should be as expected once you're in the menus.
-
+
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 ;)
@@ -236,7 +236,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
---
@@ -254,11 +254,11 @@ If you prefer to install vcredist manually instead of using my one-liner, you ca
APPID=`protontricks -l | grep -i "Skyrim - Anvil" | awk {'print $NF'} | sed 's:^.\(.*\).$:\1:' | tail -1` ; wget https://aka.ms/vs/17/release/vc_redist.x64.exe -O '/home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' ; protontricks --no-bwrap -c 'wine /home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' $APPID
```
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
Alternatively, **If you prefer to run this manually, step-by-step**, you can do the following. Firstly, we need to download the vc_redist.x64.exe installer inside the Proton prefix. Run the following command, replacing my Game ID (3595949753) with your own which you can get by running protontricks -l in Konsole:
@@ -280,13 +280,13 @@ Finally, run the installer:
wine vc_redist.x64.exe
```
-
+
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
When running wine commands in Konsole, it usually mangles the terminal a bit - text you type wont be shown (though it technically is still being printed in the terminal) - to get out of that state, either close and reopen Konsole, or just type 'reset' and hit enter, even if you can't see the characters.
diff --git a/Legacy-Wiki-Home.md b/Legacy-Wiki-Home.md
index 3051a79..5f509b3 100644
--- a/Legacy-Wiki-Home.md
+++ b/Legacy-Wiki-Home.md
@@ -1,4 +1,4 @@
-[](https://github.com/Omni-guides/Wabbajack-Modlist-Linux)
+[](https://github.com/Omni-guides/Wabbajack-Modlist-Linux)
+
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Keizaal":
-
+
Then in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select the Proton version - It's important to pick Proton Experimental here so that it uses Proton 9. If for whatever reason Proton Experimental is still utilising Proton 8 for you, you should also have an entry for Proton 9 (Beta) that you can select.
-
+
---
@@ -96,11 +96,11 @@ Then in the Compatibility tab tick the box for 'Force the use of a specific Stea
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak, and is likely also available from your distribution's package manager. Personally I use the version from flatpak/Discover Store:
-
+
The splash screen for Keizaal should hopefully now appear:
-
+
You may also get a pop-up asking if you want to Register for handling nxm links, like so:
-
+
For the Keizaal 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).
@@ -169,7 +169,7 @@ The path you need for the Keizaal executable will be:
Z:\home\omni\Games\Skyrim\Keizaal\mods\Skyrim Script Extender (SKSE64)\Root\skse64_loader.exe
```
-
+
---
@@ -197,11 +197,11 @@ Alternatively, **If you prefer to run this manually**, see an alternative step-b
Next, we should set the resolution to match your monitor resolution. To do this in MO2, filter for the entry for "SSE Display Tweaks", and double-click it:
-
+
Switch to the INI Tab, highlight the INI File on the left, and then scroll down until you see the line that reads "#Resolution=1920x1080". Remove the # at the start of the line, and then set the resolution to be what you need:
-
+
Finally, click the Close button and select "Yes" to save the changes. Optionally, you can also set an FPS limit by editing the FramerateLimit line, e.g "FramerateLimit = 60", or whatever your target FPS is.
@@ -217,7 +217,7 @@ If you've read this far, then well done! I'd very much appreciate a Star for thi
With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Click the Play button in Mod Organizer, and wait.... This takes quite a bit of time to start. Once it had loaded though, performance should be as expected once you're in the menus.
-
+
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 ;)
@@ -227,7 +227,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
---
@@ -245,11 +245,11 @@ If you prefer to install vcredist manually instead of using my one-liner, you ca
APPID=`protontricks -l | grep -i "Skyrim - Keizaal" | awk {'print $NF'} | sed 's:^.\(.*\).$:\1:' | tail -1` ; wget https://aka.ms/vs/17/release/vc_redist.x64.exe -O '/home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' ; protontricks --no-bwrap -c 'wine /home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' $APPID
```
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
Alternatively, **If you prefer to run this manually, step-by-step**, you can do the following. Firstly, we need to download the vc_redist.x64.exe installer inside the Proton prefix. Run the following command, replacing my Game ID (3595949753) with your own which you can get by running protontricks -l in Konsole:
@@ -271,13 +271,13 @@ Finally, run the installer:
wine vc_redist.x64.exe
```
-
+
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
When running wine commands in Konsole, it usually mangles the terminal a bit - text you type wont be shown (though it technically is still being printed in the terminal) - to get out of that state, either close and reopen Konsole, or just type 'reset' and hit enter, even if you can't see the characters.
diff --git a/Skyrim:-Legends-of-the-Frost.md b/Skyrim:-Legends-of-the-Frost.md
index e49ede1..736de75 100644
--- a/Skyrim:-Legends-of-the-Frost.md
+++ b/Skyrim:-Legends-of-the-Frost.md
@@ -1,4 +1,4 @@
-
+
**From the Author**: _[Legends of the Frost](https://thephoenixflavour.com/skyrim-se/lotf/introduction/) is a Wabbajack list for Skyrim SE. It is the lightest list I could conceive of, designed to be as close to vanilla as possible while bringing some much needed improvements to texture sharpness, distant terrain, and certain gameplay mechanics. I created it because for all my years of playing modding Skyrim SE I never finished the main quest once. With any other setup, I get caught in the same loop as most people: Updating, rebuilding, starting over again. LOTF is my attempt to fix that._
@@ -78,27 +78,27 @@ sudo chmod -R 755 /run/media/mmcblk0p1/Games/Skyrim/LegendsOfTheFrost
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":
-
+
Click Browse:
-
+
Browse to the path of your modlist. e.g. /home/deck/Games/Skyrim/LegendsOfTheFrost, select ModOrganizer.exe, and click Open.
-
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Legends of the Frost":
-
+
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.
-
+
**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:
@@ -107,7 +107,7 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
```
Like so:
-
+
---
@@ -115,9 +115,9 @@ Like so:
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak:
-
+
-
+
To enable the use of protontricks via the command line, open a Konsole terminal and run the following command to add an alias:
@@ -141,7 +141,7 @@ That should be protontricks installed and ready to use later in the guide.
Click play on this new entry "Skyrim - LegendsOfTheFrost" (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:
-
+
To fix this, we just need to strip the now incorrect download directory from the ModOrganizer.ini file. in Konsole terminal, run:
@@ -153,7 +153,7 @@ then re-run "Skyrim - LegendsOfTheFrost" from Steam.
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:
@@ -163,22 +163,22 @@ Z:\home\deck\Games\Skyrim\LegendsOfTheFrost\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.
-
+
The splash screen for LegendsOfTheFrost 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 LegendsOfTheFrost 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).
@@ -188,7 +188,7 @@ The path you need for the LegendsOfTheFrost application will be:
Z:\home\deck\Games\LegendsOfTheFrost\mods\Skyrim Script Extender\Root\skse64_loader.exe
```
-
+
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.
@@ -224,11 +224,11 @@ APPID=`protontricks -l | grep -i "Skyrim - Legends of the Frost" | awk {'print $
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 Settings", and double-click it:
-
+
Switch to the INI Tab, highlight the INI File on the left, and then add a line that reads "Resolution=1280x800":
-
+
Finally, click the Close button and select "Yes" to save the changes.
@@ -250,7 +250,7 @@ If you've read this far, then well done! I'd very much appreciate a Star for thi
With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Click the Play button in Mod Organizer, and wait....
-
+
This takes quite a bit of time to start. Once it had loaded though, performance was as expected in the menus.
@@ -264,7 +264,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
@@ -285,11 +285,11 @@ If you prefer to install vcredist manually instead of using my one-liner, you ca
APPID=`protontricks -l | grep -i "Skyrim - Legends of the Frost" | 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' $APPID
```
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
Alternatively, **If you prefer to run this manually, step-by-step**, you can do the following. Firstly, we need to download the vc_redist.x64.exe installer inside the Proton prefix. Run the following command, replacing my Game ID (3595949753) with your own which you can get by running protontricks -l in Konsole:
@@ -311,13 +311,13 @@ Finally, run the installer:
wine vc_redist.x64.exe
```
-
+
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
When running wine commands in Konsole, it usually mangles the terminal a bit - text you type wont be shown (though it technically is still being printed in the terminal) - to get out of that state, either close and reopen Konsole, or just type 'reset' and hit enter, even if you can't see the characters.
diff --git a/Skyrim:-Licentia-DECK.md b/Skyrim:-Licentia-DECK.md
index d79f468..48b8785 100644
--- a/Skyrim:-Licentia-DECK.md
+++ b/Skyrim:-Licentia-DECK.md
@@ -1,4 +1,4 @@
-
+
From the Author: [Licentia DECK](https://github.com/cacophony-wj/licentia_black/blob/main/README.md) _is the FIRST Wabbajack modlist designed to run NATIVELY on the Steam Deck as its primary platform. Solid 40 - 50 FPS is possible in all exteriors at the Deck's native resolution of 1280x800, unfortunately I have had to sacrifice a lot graphically (including ENB, SSS, and the complex lighting and weather mods), but the list still looks pretty good and all the Licentia gameplay goodness is here -- Vokriinator, CGO, TUDM, all that rot._
@@ -81,15 +81,15 @@ sudo chmod -R 755 /run/media/mmcblk0p1/Games/Skyrim/Licentia
The stable version of Proton provided by Steam tends to end up in some random crashes when running Licentia DECK. To increase stability, it is recommended to switch to Proton-GE. You can acquire this using an application from the Discover store called ProtonUp-Qt.
-
+
Once installed, run ProtonUp-Qt, ensure that Stem is selected at the top, and then click the "Add version" button:
-
+
Keep the defaults for Compatibility Tool and Version (Currently GE-Proton8-25 is the latest version), and click Install:
-
+
Once complete, fully exit and restart Steam, so that ProtonGE will become an option later in the guide.
@@ -100,27 +100,27 @@ Once complete, fully exit and restart Steam, so that ProtonGE will become an opt
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". The latest version of Steam should use the regular File Browser from your system, older versions of Steam had a built-in file browser.
-
+
Click Browse:
-
+
Browse to the path of your modlist. e.g. /home/deck/Games/Skyrim/Licentia, select ModOrganizer.exe, and click Open.
-
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
Once added, search for the new ModOrganizer.exe entry in your Steam Library and edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Licentia":
-
+
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.. IF you have crashing issues with some animations, it has been suggested that switching from Proton 8 from Valve to Proton-GE can help. Proton-GE can be acquired by using the ProtonUp-QT application available in the Discover store on deck. Some more information and steps can be found [here](https://www.rockpapershotgun.com/how-to-install-proton-ge-on-the-steam-deck).
-
+
**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:
@@ -129,7 +129,7 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
```
Like so:
-
+
---
@@ -137,9 +137,9 @@ Like so:
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak:
-
+
-
+
To enable the use of protontricks via the command line, open a Konsole terminal and run the following command to add an alias:
@@ -163,7 +163,7 @@ That should be protontricks installed and ready to use later in the guide.
Click play on this new entry "Skyrim - Licentia" (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:
-
+
To fix this, we just need to strip the now incorrect download directory from the ModOrganizer.ini file. in Konsole terminal, run:
@@ -175,7 +175,7 @@ then re-run "Skyrim - Licentia" from Steam.
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:
@@ -183,25 +183,25 @@ To fix this, we need to point MO2 to our new location. Click OK, and then Browse
Z:\home\deck\Games\Skyrim\Licentia\Stock Game
```
-
+
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.
Click Open, and the splash screen for Licentia 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 Arrow icon at the top, which will bring up the Modify Executables window:
-
+
For the SKSE executable, we need to point MO2 to the skse64_loader.exe file contained within the Stock Game folder. The path you need will be:
@@ -209,7 +209,7 @@ For the SKSE executable, we need to point MO2 to the skse64_loader.exe file cont
Z:\home\deck\Games\Skyrim\Licentia\Stock Game\skse64_loader.exe
```
-
+
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.
@@ -245,11 +245,11 @@ APPID=`protontricks -l | grep -i "Skyrim - Licentia" | awk {'print $NF'} | sed '
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:
-
+
Switch to the INI Tab, highlight the INI File on the left, and then scroll down 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.
@@ -271,7 +271,7 @@ If you've read this far, then well done! I'd very much appreciate a Star for thi
With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Click the Run button in Mod Organizer, and wait....
-
+
This takes quite a bit of time to start. Once it had loaded though, performance was as expected in the menus.
@@ -287,7 +287,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
@@ -307,11 +307,11 @@ If you prefer to install vcredist manually instead of using my one-liner, you ca
APPID=`protontricks -l | grep -i "Skyrim - Licentia" | 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' $APPID
```
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
Alternatively, **If you prefer to run this manually, step-by-step**, you can do the following. Firstly, we need to download the vc_redist.x64.exe installer inside the Proton prefix. Run the following command, replacing my Game ID (3595949753) with your own which you can get by running protontricks -l in Konsole:
@@ -333,13 +333,13 @@ Finally, run the installer:
wine vc_redist.x64.exe
```
-
+
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
When running wine commands in Konsole, it usually mangles the terminal a bit - text you type wont be shown (though it technically is still being printed in the terminal) - to get out of that state, either close and reopen Konsole, or just type 'reset' and hit enter, even if you can't see the characters.
diff --git a/Skyrim:-Living-Skyrim-4.md b/Skyrim:-Living-Skyrim-4.md
index 088887e..6244d72 100644
--- a/Skyrim:-Living-Skyrim-4.md
+++ b/Skyrim:-Living-Skyrim-4.md
@@ -1,5 +1,5 @@
+
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Living Skyrim 4":
-
+
Then in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select the Proton version - It's important to pick Proton Experimental here so that it uses Proton 9. If for whatever reason Proton Experimental is still utilising Proton 8 for you, you should also have an entry for Proton 9 (Beta) that you can select.
-
+
---
@@ -96,11 +96,11 @@ Then in the Compatibility tab tick the box for 'Force the use of a specific Stea
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak, and is likely also available from your distribution's package manager. Personally I use the version from flatpak/Discover Store:
-
+
The splash screen for Living Skyrim 4 should hopefully now appear:
-
+
You may also get a pop-up asking if you want to Register for handling nxm links, like so:
-
+
For the LivingSkyrim4 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).
@@ -169,7 +169,7 @@ The path you need for the Living Skyrim 4 executable will be:
Z:\home\omni\Games\LivingSkyrim4\Stock Game\skse64_loader.exe
```
-
+
---
@@ -197,11 +197,11 @@ Alternatively, **If you prefer to run this manually**, see an alternative step-b
Next, we should set the resolution to match your monitor resolution. To do this in MO2, filter for the entry for "SSE Display Tweaks", and double-click it:
-
+
Switch to the INI Tab, highlight the INI File on the left, and then scroll down until you see the line that reads "#Resolution=1920x1080". Remove the # at the start of the line, and then set the resolution to be what you need:
-
+
Finally, click the Close button and select "Yes" to save the changes. Optionally, you can also set an FPS limit by editing the FramerateLimit line, e.g "FramerateLimit = 60", or whatever your target FPS is.
@@ -217,7 +217,7 @@ If you've read this far, then well done! I'd very much appreciate a Star for thi
With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Click the Play button in Mod Organizer, and wait.... This takes quite a bit of time to start. Once it had loaded though, performance was as expected once you're in the menus.
-
+
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 ;)
@@ -227,7 +227,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
---
@@ -245,11 +245,11 @@ If you prefer to install vcredist manually instead of using my one-liner, you ca
APPID=`protontricks -l | grep -i "Skyrim - Living Skyrim 4" | awk {'print $NF'} | sed 's:^.\(.*\).$:\1:' | tail -1` ; wget https://aka.ms/vs/17/release/vc_redist.x64.exe -O '/home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' ; protontricks --no-bwrap -c 'wine /home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' $APPID
```
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
Alternatively, **If you prefer to run this manually, step-by-step**, you can do the following. Firstly, we need to download the vc_redist.x64.exe installer inside the Proton prefix. Run the following command, replacing my Game ID (3595949753) with your own which you can get by running protontricks -l in Konsole:
@@ -271,13 +271,13 @@ Finally, run the installer:
wine vc_redist.x64.exe
```
-
+
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
When running wine commands in Konsole, it usually mangles the terminal a bit - text you type wont be shown (though it technically is still being printed in the terminal) - to get out of that state, either close and reopen Konsole, or just type 'reset' and hit enter, even if you can't see the characters.
diff --git a/Skyrim:-Nordic-Souls.md b/Skyrim:-Nordic-Souls.md
index 4f5f695..64f44e6 100644
--- a/Skyrim:-Nordic-Souls.md
+++ b/Skyrim:-Nordic-Souls.md
@@ -1,5 +1,5 @@
+
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Nordic Souls":
-
+
Then in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select the Proton version - It's important to pick Proton Experimental here so that it uses Proton 9. If for whatever reason Proton Experimental is still utilising Proton 8 for you, you should also have an entry for Proton 9 (Beta) that you can select.
-
+
---
@@ -104,11 +104,11 @@ Then in the Compatibility tab tick the box for 'Force the use of a specific Stea
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak, and is likely also available from your distribution's package manager. Personally I use the version from flatpak/Discover Store:
-
+
The splash screen for Nordic Souls should hopefully now appear:
-
+
You may also get a pop-up asking if you want to Register for handling nxm links, like so:
-
+
For the NordicSouls 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).
@@ -177,7 +177,7 @@ The path you need for the Nordic Souls executable will be:
Z:\home\omni\Games\Skyrim\NordicSouls\mods\Skyrim Script Extender (SKSE64)\Root\skse64_loader.exe
```
-
+
---
@@ -205,11 +205,11 @@ Alternatively, **If you prefer to run this manually**, see an alternative step-b
Next, we should set the resolution to match your monitor resolution. To do this in MO2, filter for the entry for "SSE Display Tweaks", and double-click it:
-
+
Switch to the INI Tab, highlight the INI File on the left, and then scroll down until you see the line that reads "#Resolution=1920x1080". Remove the # at the start of the line, and then set the resolution to be what you need:
-
+
Finally, click the Close button and select "Yes" to save the changes. Optionally, you can also set an FPS limit by editing the FramerateLimit line, e.g "FramerateLimit = 60", or whatever your target FPS is.
@@ -225,7 +225,7 @@ If you've read this far, then well done! I'd very much appreciate a Star for thi
With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Click the Play button in Mod Organizer, and wait.... This takes quite a bit of time to start. Once it had loaded though, performance was as expected once you're in the menus.
-
+
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 ;)
@@ -235,7 +235,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
---
@@ -253,11 +253,11 @@ If you prefer to install vcredist manually instead of using my one-liner, you ca
APPID=`protontricks -l | grep -i "Skyrim - Nordic Souls" | awk {'print $NF'} | sed 's:^.\(.*\).$:\1:' | tail -1` ; wget https://aka.ms/vs/17/release/vc_redist.x64.exe -O '/home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' ; protontricks --no-bwrap -c 'wine /home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/drive_c/vc_redist.x64.exe' $APPID
```
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
Alternatively, **If you prefer to run this manually, step-by-step**, you can do the following. Firstly, we need to download the vc_redist.x64.exe installer inside the Proton prefix. Run the following command, replacing my Game ID (3595949753) with your own which you can get by running protontricks -l in Konsole:
@@ -279,13 +279,13 @@ Finally, run the installer:
wine vc_redist.x64.exe
```
-
+
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
When running wine commands in Konsole, it usually mangles the terminal a bit - text you type wont be shown (though it technically is still being printed in the terminal) - to get out of that state, either close and reopen Konsole, or just type 'reset' and hit enter, even if you can't see the characters.
diff --git a/Skyrim:-Tuxborn.md b/Skyrim:-Tuxborn.md
index 22464e6..b1714b2 100644
--- a/Skyrim:-Tuxborn.md
+++ b/Skyrim:-Tuxborn.md
@@ -1,4 +1,4 @@
-
+
[](https://ko-fi.com/D1D8H8WBD)
@@ -61,31 +61,31 @@ Alternatively, just download it from [wabbajack.org](https://www.wabbajack.org/)
Add Wabbajack.exe to Steam by using the "Add a Non-Steam Game to My Library" function from Steam:
-
+
Click "Add Selected Programs":
-
+
Once added, right click the new Wabbajack.exe entry in steam, and go to Properties. I recommend you change the name to simply "Wabbajack":
-
+
Next, click the Compatibility tab, and set it to use "Proton 9.0-4" (Do not use Proton 10, or Proton Experimental as in the screenshots below - it recently also updated to Proton 10, which breaks the current process needed to get Wabbajack to run successfully. Stick with Proton 9 for now):
-
+
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.
-
+
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.
@@ -100,7 +100,7 @@ bash <(curl -s https://raw.githubusercontent.com/Omni-guides/Wabbajack-Modlist-L
e.g:
-
+
---
@@ -112,7 +112,7 @@ e.g:
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:
-
+
**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/Skyrim:-Tuxborn#12---add-wabbajackexe-to-steam). If you continue to have issues, please reach out on Discord for assistance.
@@ -134,11 +134,11 @@ mkdir -p $HOME/Games/WabbajackDownloads/Skyrim
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":
-
+
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:
-
+
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.
@@ -150,7 +150,7 @@ Retaining this section for additional Notes that come up after 1.0 release.
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**.
-
+
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/Wabbajack-Modlist-Linux/wiki/Skyrim:-Tuxborn#additional-notes) for some indication of install times on Steam Deck.)
@@ -164,29 +164,29 @@ Unlike on Windows, the Wabbajack Installation process is only part of what is ne
Click the "Add a Non-Steam Game to My Library" option from the Games menu in Steam:
-
+
Lastly for this step, click "Add Selected Program"
-
+
#### 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:
-
+
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.
-
+
**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:
@@ -195,12 +195,12 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
```
Like so:
-
+
Switch to the Compatibility tab, tick the box for "Force the use of a specific Steam Play compatibility tool", and select "Proton Experimental":
-
+
#### 3.3 Run once and close MO2
@@ -216,25 +216,25 @@ bash <(curl -s https://raw.githubusercontent.com/Omni-guides/Wabbajack-Modlist-L
(**Screenshots may differ slightly as the install script continues to be developed**)
-
+
A banner and a short note will be displayed, and a request to press any key to continue:
-
+
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:
-
+
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:
-
+
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/Wabbajack-Modlist-Linux/wiki/Skyrim:-Tuxborn#additional-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.
-
+
#### 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.
@@ -276,7 +276,7 @@ Regardless of which profile you want to use you should now, finally, be ready to
First point to note is the 'Unlock' button that will appear shortly after you click Play. Never, ever (ever) click the Unlock button.
-
+
โ ๏ธ โ 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! โ ๏ธ โ
@@ -289,7 +289,7 @@ The very first launch will likely crash fairly early, during the shader compilat
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:
-
+
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.
@@ -333,11 +333,11 @@ It would be interesting to see if anyone has vastly different timings from the a
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:
-
+
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":
-
+
Similarly, the FrameLimit (FPS limit) can be adjusted by editing the line:
diff --git a/SyncToDeck.md b/SyncToDeck.md
index e7d6faa..1b94833 100644
--- a/SyncToDeck.md
+++ b/SyncToDeck.md
@@ -1,4 +1,4 @@
-
+
# How to transfer files to Steam Deck (New Install & Modlist Update)
@@ -10,7 +10,7 @@ _**PLEASE NOTE:** I cannot be held responsible for anything negative that happen
For all methods described here, you will need to have already set a password for the deck user on your Steam Deck. If you haven't already done so, you can follow Valve's guidance:
-
+
### Enable SSH on the Steam Deck
@@ -22,7 +22,7 @@ sudo systemctl enable --now sshd
You will be prompted to enter you 'deck' user password.
-
+
## Option 1 (Recommended): WinSCP - a free file manager for Windows supporting FTP, SFTP, S3 and WebDAV.
@@ -30,7 +30,7 @@ Download WinSCP from [here](https://winscp.net/eng/download.php) on your Windows
Once downloaded, install it, then open WinSCP, you will be presented with a Login Configuration window.
-
+
Keep "SFTP" selected as the File protocol, enter the IP Address of your Steam Deck in the "Host name" text box. Keep the port as 22, and enter "deck" as the User name. You can leave the password box blank for now.
@@ -40,11 +40,11 @@ Once your Login details match the screenshot (your IP Address will be different)
The first connection from WinSCP to you Deck will likely prompt you to accept the host key - simply click the "Accept" button:
-
+
The SFTP connection from your Windows system to your Deck will be initiated, and you will be prompted to enter the password for the "deck" user on your Steam Deck:
-
+
Enter the password and click OK. All being well, you should be presented with a "Dual Browser" window, which displays your Windows filesystem on the left, and your Steam Deck filesystem on the right.
@@ -66,31 +66,31 @@ And on the Steam Deck side (right hand side), I navigate to:
/home/deck/Games/Skyrim/Tuxborn
```
-
+
Once you have the two Tuxborn directories open on Windows and Deck, click the "Synchronize" button in the top right:
-
+
Given that the Tuxborn directory on the Deck is empty, you can leave the most of the default settings as they are, just make sure that "Remote" is selected for the "Direction/Target directory":
-
+
Once you have these settings in place, click OK to start the comparison phase. You may get a popup regarding opening a separate shell session.
-
+
This is fine to accept, so click OK. WinSCP will begin comparing the source and target directories:
-
+
After a few minutes, a report will be displayed listing the changes that WinSCP will carry out if you proceed:
-
+
For a new Tuxborn install, this is going to essentially report that it will be copying everything from the Windows system, to the Deck. Click OK in the top right to accept these actions and start the transfer process:
-
+
How long this process takes will depend on how much data needs to be synchronised, and how fast your connection between Windows system and Steam Deck is. Eventually it will finish. Once it has, you will need to return to the main Tuxborn Install guide, for the next steps - rejoin it [here](https://github.com/Omni-guides/Tuxborn/blob/main/TuxbornSteamDeckFullInstall.md#step-3---post-wabbajack-steps) and complete all of the remaining steps. After that, you should be able to start Tuxborn from steam, and get back to playing!
@@ -118,15 +118,15 @@ And on the Steam Deck side (right hand side), I navigate to:
/home/deck/Games/Skyrim/Tuxborn
```
-
+
Once you have the two Tuxborn directories open on Windows and Deck, click the "Synchronize" button in the top right:
-
+
The important settings to use here are:
@@ -142,21 +142,21 @@ Comparison criteria: Checksum - While this is a slower method of comparing the W
Once you have these settings in place, click OK to start the comparison phase. You may get a popup regarding opening a separate shell session.
-
+
In terms of the actual rsync command, these are the flags I use. _Please be very careful with this command_, using the `--delete` flag with rsync can be dangerous if you get the paths wrong - see below the command for a brief description of what each flag is applying here. The rsync command I use is (using Tuxborn as an example):
@@ -183,7 +183,7 @@ In terms of the actual rsync command, these are the flags I use. _Please be very
rsync -arvP --delete /drives/c/Wabbajack/Skyrim/Tuxborn/* deck@steamdeck:/home/deck/Games/Skyrim/Tuxborn/.
```
-
+
* You will need to adjust the path in `/drives/c/../..` to match where the Modlist Install directory you set in Wabbajack exists on your Windows system. For example a Wabbajack Install path of `D:\Wabbajack\Tuxborn` would be referenced as `/drives/d/Wabbajack/Tuxborn` for the rsync command.
diff --git a/Troubleshooting-and-FAQ.md b/Troubleshooting-and-FAQ.md
index 618bae7..f426fc4 100644
--- a/Troubleshooting-and-FAQ.md
+++ b/Troubleshooting-and-FAQ.md
@@ -1,4 +1,4 @@
-
+
Here, I will try to document issues that regularly come up from users getting support, in case they help others in future.
diff --git a/TuxbornSteamDeckFullInstall.md.md b/TuxbornSteamDeckFullInstall.md.md
index 3c6949a..442085f 100644
--- a/TuxbornSteamDeckFullInstall.md.md
+++ b/TuxbornSteamDeckFullInstall.md.md
@@ -1,4 +1,4 @@
-
+
[](https://ko-fi.com/D1D8H8WBD)
@@ -51,31 +51,31 @@ Alternatively, just download it from [wabbajack.org](https://www.wabbajack.org/)
Add Wabbajack.exe to Steam by using the "Add a Non-Steam Game to My Library" function from Steam:
-
Click "Add Selected Programs":
-
Once added, right click the new Wabbajack.exe entry in steam, and go to Properties. You can change the name to simply "Wabbajack" if you wish:
-
+
Once done, the Wabbajack application itself should open up - **Close it down** before trying to use the application, and move on to Step 4.
@@ -90,7 +90,7 @@ bash <(curl -s https://raw.githubusercontent.com/Omni-guides/Wabbajack-Modlist-L
e.g:
-
---
@@ -102,7 +102,7 @@ e.g:
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:
-
**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.
@@ -112,11 +112,11 @@ Until Tuxborn becomes available directly from the Wabbajack Modlist Gallery, you
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":
-
+
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 below:
-
+
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.
@@ -132,7 +132,7 @@ There are a couple of larger mods that sometimes fail to download when using Wab
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 above, Nexus Premium is **strongly recommended**.
-
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, or hanging - if this happens you can just restart Wabbajack, Click Install from disk, and click Play again - it should have re-populated your previous paths etc. 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.)
@@ -146,29 +146,29 @@ Unlike on Windows, the Wabbajack Installation process is only part of what is ne
Click the "Add a Non-Steam Game to My Library" option from the Games menu in Steam:
-
Lastly for this step, click "Add Selected Program"
-
#### 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:
-
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.
-
**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:
@@ -177,12 +177,12 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
```
Like so:
-
#### 3.3 Run once and reboot
@@ -194,25 +194,25 @@ To run the required post-install steps automatically, you can run my automation
`bash <(curl -s https://raw.githubusercontent.com/Omni-guides/Wabbajack-Modlist-Linux/main/binaries/omni-guides.sh)`
-
A banner and a short note will be displayed, and a request to press any key to continue:
-
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:
-
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:
-
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.
-
#### 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.
@@ -252,7 +252,7 @@ Regardless of which profile you want to use you should now, finally, be ready to
First point to note is the 'Unlock' button that will appear shortly after you click Play. Never, ever (ever) click the Unlock button.
-
โ ๏ธ โ 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! โ ๏ธ โ
@@ -265,7 +265,7 @@ The very first launch will likely crash fairly early, during the shader compilat
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:
-
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.
@@ -305,11 +305,11 @@ It would be interesting to see if anyone has vastly different timings from the a
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:
-
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":
-
Similarly, the FrameLimit (FPS limit) can be adjusted by editing the line:
diff --git a/Using-the-omniโguides.sh-Automation-Script.md b/Using-the-omniโguides.sh-Automation-Script.md
index 9e0ed30..97cac16 100644
--- a/Using-the-omniโguides.sh-Automation-Script.md
+++ b/Using-the-omniโguides.sh-Automation-Script.md
@@ -1,4 +1,4 @@
-
+
DISCLAIMER - I am not affiliated with the Wabbajack group in any way, just a gamer trying to help other gamers. You may be able to get assistance with this guide from the #unofficial-linux-help channel of the main [Official Wabbajack Discord](https://discord.gg/wabbajack), but it may be best to @ me on Discord (@omni). Due to this being an unofficial guide, assistance on this from Wabbajack support directly, or the Modlist developers, is highly unlikely.
@@ -61,27 +61,27 @@ I will use Anvil as an example Modlist for this guide. **Please change the comma
Once Wabbajack has successfully completed the download and installation of the Modlist, or you have transferred the modlist from your Windows system, 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":
-
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
Once added, edit the properties of the new ModOrganizer.exe entry. The script expects the Shortcut Name to contain either "Skyrim" for Skyrim modlists, or "Fallout" for Fallout based modlists - for example "Skyrim - Tuxborn", "Skyrim - Anvil" or "Fallout - Life in the Ruins". Adjust to match the modlist you are trying to run. This is required because _not_ limiting the search for game entries the script will find to only Skyrim or Fallout, would mean listing literally all games you have installed and would be messy to deal with.
-
Switch to the Compatibility tab and tick the box for 'Force the use of a specific Steam Play compatibility tool', then select the Proton version "Proton Experimental".
-
+
**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 (you may need to adjust the path of your SD Card in /run/media as necessary on your system):
@@ -90,7 +90,7 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
```
Like so:
-
+
A banner and a short note will be displayed, and a request to press any key to continue:
-
+
The script will then attempt to detect all the Wabbajack Modlists you have installed and added to Steam. Press the corresponding number for the Modlist you with to configure:
-
+
You will be asked to confirm you want to continue, and the script will move on to detecting the Modlist Install directory - if multiple possibilities 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 protontricks permissions can be set correctly, and the script will continue through more automated tasks:
-
+
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 for skyrimprefs.ini/fallou4prefs and SSEDisplayTweaks). If you are not running this script on a Steam Deck, you will be asked to input your desired resolution, in the format 1920x1080.
-
+
---
@@ -152,7 +152,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
diff --git a/WIP-Skyrim:-AVO-(Deck).md b/WIP-Skyrim:-AVO-(Deck).md
index c21de7e..b53e14a 100644
--- a/WIP-Skyrim:-AVO-(Deck).md
+++ b/WIP-Skyrim:-AVO-(Deck).md
@@ -1,4 +1,4 @@
-
+
_Althro's Visual Overhaul ([AVO](https://github.com/Althro/AVO) ) is designed as a "true to vanilla list" to build your own list upon. It has been installed over 12 thousand times and garnered a reputation for being incredibly stable and is, as the quote says, "the best way to make your own list."_
@@ -68,27 +68,27 @@ sudo chmod -R 755 /run/media/mmcblk0p1/Games/Skyrim/AVO
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". The latest version of Steam should use the regular File Browser from your system, older versions of Steam had a built-in file browser.
-
+
Click Browse:
-
+
Browse to the path of your modlist. e.g. /home/deck/Games/Skyrim/AVO, select ModOrganizer.exe, and click Open.
-
+
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
-
+
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - AVO":
-
+
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..
-
+
**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:
@@ -98,7 +98,7 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
Like so:
-
+
---
@@ -106,9 +106,9 @@ Like so:
If you don't already have it installed, ProtonTricks can be installed via the Discover store as a flatpak:
-
+
-
+
To enable the use of protontricks via the command line, open a Konsole terminal and run the following command to add an alias:
@@ -131,7 +131,7 @@ That should be protontricks installed and ready to use later in the guide.
Click play on this new entry "Skyrim - AVO" (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:
-
+
To fix this, we just need to strip the now incorrect download directory from the ModOrganizer.ini file. in Konsole terminal, run:
@@ -143,7 +143,7 @@ then re-run "Skyrim - AVO" from Steam.
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:
@@ -153,22 +153,22 @@ Z:\home\deck\Games\Skyrim\AVO\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.
-
+
The splash screen for AVO 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 AVO executable, we need to point MO2 at a file that may not actually exist yet (but it will exist, once GameRoot does it's thing when you click launch - and is then removed again when the game closes).
@@ -178,7 +178,7 @@ The path you need for the AVO application will be:
Z:\home\deck\Games\AVO\mods\Skyrim Script Extender\Root\skse64_loader.exe
```
-
+
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.
@@ -214,11 +214,11 @@ APPID=`protontricks -l | grep -i "Skyrim - AVO" | awk {'print $NF'} | sed 's:^.\
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:
-
+
Switch to the INI Tab, highlight the INI File on the left, and then scroll down 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.
@@ -250,7 +250,7 @@ Enjoy!
[](https://ko-fi.com/D1D8H8WBD)
-
+
@@ -271,11 +271,11 @@ If you prefer to install vcredist manually instead of using my one-liner, you ca
APPID=`protontricks -l | grep -i "Skyrim - AVO" | 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' $APPID
```
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
Alternatively, **If you prefer to run this manually, step-by-step**, you can do the following. Firstly, we need to download the vc_redist.x64.exe installer inside the Proton prefix. Run the following command, replacing my Game ID (3595949753) with your own which you can get by running protontricks -l in Konsole:
@@ -297,13 +297,13 @@ Finally, run the installer:
wine vc_redist.x64.exe
```
-
+
-
+
Check the box to agree, and then click install. It should complete quickly.
-
+
When running wine commands in Konsole, it usually mangles the terminal a bit - text you type wont be shown (though it technically is still being printed in the terminal) - to get out of that state, either close and reopen Konsole, or just type 'reset' and hit enter, even if you can't see the characters.
diff --git a/Wabbajack-on-Linux-via-Wine.md b/Wabbajack-on-Linux-via-Wine.md
index ef59ba1..7207ead 100644
--- a/Wabbajack-on-Linux-via-Wine.md
+++ b/Wabbajack-on-Linux-via-Wine.md
@@ -1,4 +1,4 @@
-
+
or by running `winetricks` in a terminal:
-
+
Once winetricks has opened, ensure "Select the default wineprefix" is selected, or select it, and then click OK.
-
+
On the next window, highlight "Delete ALL DATA AND APPLICATIONS INSIDE THIS WINEPREFIX" - you may have to scroll the window down a little:
-
+
A warning will pop up needing you to confirm the deletion of the prefix and contents:
-
+
Click continue, and winetricks will close, deleting the prefix in the background. The prefix has now been removed.
@@ -152,11 +152,11 @@ wineboot
Alternatively, to do so using the winetricks GUI, re-run winetricks, either from the Applications menu, or terminal, as above. This time it will notify you that the Wine environment in `/home/
+
It will also likely prompt you to install Wine-Mono, which you can confirm.
-
+
### Step 6 - Change the default renderer used
@@ -170,15 +170,15 @@ winetricks renderer=vulkan
Alternatively via the GUI, start winetricks as above, and then again, with "Select the default wineprefix" highlighted, click OK.
-
+
Scroll down the list of settings shown, until you see "renderer=vulkan", highlight it, and click OK.
-
+
This should return you to the previous options menu, don't close winetricks just yet.
@@ -196,15 +196,15 @@ wine $HOME/Wabbajack/MicrosoftEdgeWebView2RuntimeInstallerX64.exe
To do so via the GUI, start winetricks as above if it's not still open, select the Default Prefix option if needed, and then highlight "Run an arbitrary executable (.exe/.msi/.msu)" and click OK. This should bring up a file browser of your system, and will allow us to locate and run any .exe we want - in this case, the Edge Webview installer that we downloaded in Step 3.
-
+
Using the file browser, locate the installer for Webview - this should be in `/home/
+
After a few second, the WebView2 installer window will appear, and run through the install process, and then it will close without any message. Keep winetricks open for the next step.
-
+
---
@@ -220,11 +220,11 @@ winecfg -v win7
Alternatively via the winetricks GUI, highlight "Run winecfg" and click OK. This will open up a new small window labelled "Wine configuration".
-
+
Staying on the Applications tab which should be selected by default, change the "Windows Version" at the bottom to be "Windows 7" instead of the default of Windows 10 or 11.
-
+
Do not close this window yet.
@@ -253,15 +253,15 @@ wine regedit $HOME/Wabbajack/WJApplication.reg
Alternatively, to do this from the winetricks GUI, ensure you are still on the Applications tab from Step 8, click the "Add application" button near the bottom:
-
+
This will open up a Windows-style file browser. Navigate to your Wabbajack.exe file, which will be in `Z:\home\
+
Highlight Wabbajack.exe, and click Open, and you should now see Wabbajack.exe listed in the list of applications. Select Wabbajack.exe in the list, and change the "Windows Version" from "Use global settings" to "Windows 10", and then click apply:
-
+
You can now close winetricks by clicking the Cancel button a few times.
@@ -315,7 +315,7 @@ The Steam Library check is only done when Wabbajack starts, so if you have jumpe
That should be it as far as configuration is concerned. We can now run Wabbajack. You can do this by double-clicking the Wabbajack.exe file in your file browser:
-
+
or by running your equivalent of:
@@ -325,11 +325,11 @@ cd $HOME/Wabbajack ; wine $HOME/Wabbajack/Wabbajack.exe
And all being well, this will start Wabbajack, and it will run through the usual install:
-
+
Log into Nexus using the GUI options, just like you would on Windows.
-
+
At this stage, you should be good to just Wabbajack in the normal way. Either install a modlist from file, or browse the gallery to select one. There is currently a bug with some of the images not loading correctly, but that should be fixed in an upcoming update to Wabbajack.
diff --git a/Wabbajack-via-Proton.md b/Wabbajack-via-Proton.md
index 711d848..7e100bb 100644
--- a/Wabbajack-via-Proton.md
+++ b/Wabbajack-via-Proton.md
@@ -1,4 +1,4 @@
-
+
---
@@ -87,7 +87,7 @@ e.g:
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. Once ready, browse the gallery or add a .wabbajack file manually, as you would do even on Windows. Fill in the Install and Downloads directories using their Z:\ paths. For example:
-