mirror of
https://github.com/Omni-guides/Jackify.git
synced 2026-01-17 19:47:00 +01:00
Minor update and resize images.
Omni-guides
@@ -20,6 +20,8 @@ The script also assumes that you have *sudo* access for your user. There are onl
|
||||
|
||||
I will use Anvil as an example Modlist for this guide.
|
||||
|
||||
** IMPORTANT **: Once you have added the Non-Steam Game entry, click Play on it in Steam at least once, even if it fails or gives an error. This is required to register the Game Entry so that Protontricks can manage it.
|
||||
|
||||
---
|
||||
|
||||
### Step 1 - Create the directory
|
||||
@@ -70,27 +72,27 @@ sudo chmod -R 755 /run/media/mmcblk0p1/Games/Skyrim/Anvil
|
||||
|
||||
The next step is to add ModOrganizer.exe to Steam as a non-steam game. In Steam, click Games, then "Add a Non-Steam Game to My Library":
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-AddNonSteamGame.png" width="400">
|
||||
|
||||
Click Browse:
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-BrowseNonSteamGame.png" width="400">
|
||||
|
||||
Browse to the path of your Modlist. e.g. /home/deck/Games/Skyrim/Anvil, select ModOrganizer.exe, and click Open.
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Anvil/Anvil-AddMO2NonSteamGame.png" width="400">
|
||||
|
||||
Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Anvil/Anvil-AddSelectedNonSteamGame.png" width="400">
|
||||
|
||||
Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Anvil":
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Anvil/Anvil-PropertiesNonSteamGame.png" width="800">
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Anvil/Anvil-PropertiesNonSteamGame.png" width="400">
|
||||
|
||||
Then in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select the Proton version - Personally I now use Proton 9.0 Beta which has recently been introduced by Valve. This some very useful fixes for Wabbajack Modlists and Bethesda game mods in general. The script will automatically handle any additional tasks required if you select Proton 8 for whatever reason.
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_proton9.png" width="800">
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_proton9.png" width="400">
|
||||
|
||||
**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:
|
||||
|
||||
@@ -99,7 +101,9 @@ STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
|
||||
```
|
||||
Like so:
|
||||
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/shared/Shared-STEAM_COMPAT_MOUNTS.png" width="400">
|
||||
|
||||
** IMPORTANT **: As a reminder - Once you have added the Non-Steam Game entry, click Play on it in Steam at least once, even if it fails or gives an error. This is required to register the Game Entry so that Protontricks can manage it.
|
||||
|
||||
---
|
||||
|
||||
@@ -111,25 +115,25 @@ You can run the script directly from GitHub - this will ensure you are using the
|
||||
bash <(curl -s https://raw.githubusercontent.com/Omni-guides/Wabbajack-Modlist-Linux/main/binaries/omni-guides.sh)
|
||||
```
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_RunScript.png" width="800">
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_RunScript.png" width="600">
|
||||
|
||||
A banner and a short note will be displayed, and a request to press any key to continue:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_BannerContinue.png" width="800">
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_BannerContinue.png" width="600">
|
||||
|
||||
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:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_SelectModlist.png" width="800">
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_SelectModlist.png" width="600">
|
||||
|
||||
You will be asked to confirm you want to continue, and the script will move on to detecting the Modlist Install directory - if 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.
|
||||
|
||||
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:
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_SudoPassword.png" width="800">
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_SudoPassword.png" width="600">
|
||||
|
||||
Lastly, you will be asked if you want to set the resolution. This is optional but I'm trying to reduce the manual steps as much as I can. If you're running this on a Steam Deck, it will assume the desired resolution is 1280x800 (If you are going to be played while docked, you will have to manually alter the resolution via MO2 for skyrimprefs.ini/fallou4prefs and SSEDisplayTweaks). Not on a Steam Deck, you will be asked to input your desired resolution.
|
||||
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_SetResolution.png" width="800">
|
||||
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/omni-guides.sh/Omni-Guides-sh_SetResolution.png" width="600">
|
||||
|
||||
---
|
||||
|
||||
@@ -137,7 +141,9 @@ Lastly, you will be asked if you want to set the resolution. This is optional bu
|
||||
|
||||
And that's it! You should now be able to click Play on the Modlist entry in Steam. MO2 should start and now be pre-configured correctly. You may still have to/want to disable any features or mods you don't want or aren't compatible - things such as ENB. For the most part, any Modlist-specific steps will still be listed in my manual guide for that Modlist, but I will also soon be attempting to add Modlist-specific steps to the automation script, where required.
|
||||
|
||||
**PLEASE NOTE** - I have also seen a number of Modlists hang on first launch - either before displaying the Main Menu options (New Game etc), or after clicking New Game. This only seems to happen the first time, and is fine every subsequent time - I believe at this time that it is related to Shader Cache building, but I haven't been able to pin it down or resolve it. This is not unique to this automation script, and is a minor annoyance more than anything.
|
||||
**PLEASE NOTE** - I have also seen a number of Modlists hang on first launch - either before displaying the Main Menu options (New Game etc), or after clicking New Game. This only seems to happen the first time, and is fine every subsequent time - I believe at this time that it is related to Shader Cache building, but I haven't been able to pin it down or resolve it. There are also some odd cases when on first launch, some mods may fail to load - again this is usually only for the first launch, but there have been times when a restart of Steam has been required (or just a reboot of the deck) - I haven't been able to find out why.. at least it is only a minor annoyance and subsequent launches are fine.
|
||||
|
||||
This is not unique to this automation script, and is a minor annoyance more than anything.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user