Updated Enderal: Emissaries of Tux (markdown)

Omni-guides
2024-09-27 10:35:55 +01:00
parent d39e1e9674
commit e6873db899

@@ -132,7 +132,7 @@ Once the download completes, you can close ProtonUp-QT.
Because this modlist utilises the vanilla Enderal game directory, we need to enable the visibility of hidden files on the filesystem (on Linux these are known as dotfiles). This is because by default Steam will create it's game library in a ~/.local or ~/.steam directory, that is hidden by default. The setting can be changed via the protontricks GUI, or just by running the following command in a konsole/terminal window:
```
protontricks --no-bwrap -c 'WINEDEBUG=-all wine reg add "HKEY_CURRENT_USER\Software\Wine" /v ShowDotFiles /d Y /f' 22380
protontricks --no-bwrap -c 'WINEDEBUG=-all wine reg add "HKEY_CURRENT_USER\Software\Wine" /v ShowDotFiles /d Y /f' 976620
```
@@ -148,7 +148,7 @@ The easiest way to install what we need is to use ProtonTricks, which should be
Adding the required packages can be done via the ProtonTricks gui, but perhaps the easiest way is via command line. You can run the following one-liner to do it for you:
```
protontricks --no-bwrap 976620 -q xact xact_x64 d3dcompiler_47 d3dx11_43 d3dcompiler_43 vcrun2022
protontricks --no-bwrap 976620 -q xact xact_x64 d3dcompiler_47 d3dx11_43 d3dcompiler_43 vcrun2022 fontsmooth=rgb
```
@@ -157,7 +157,7 @@ protontricks --no-bwrap 976620 -q xact xact_x64 d3dcompiler_47 d3dx11_43 d3dcomp
### Step 7 - Switch to steamtinkerlaunch and configure it
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:
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:
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/EmissariesOfTux/EmissariesOfTux_ProtonSTL.png" width="600">
@@ -188,17 +188,37 @@ Click Save and Play, and all being well, you should see the Emissaries of Tux sp
### 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:
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/EmissariesOfTux/EmissariesOfTux_MO2InstanceError.png" width="400">
Click OK, and then click "Browse":
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/EmissariesOfTux/EmissariesOfTux_MO2InstanceBrowse.png" width="400">
Navigate to the path for the vanilla Enderal directory - On Steam Deck, for **Internal Storage** this will be:
```
Z:\home\deck\.local\share\Steam\steamapps\common\Enderal Special Edition
```
and for **SDCard**:
```
D:\SteamLibrary\steamapps\common\Enderal Special Edition\
```
In some cases, you may see an error regarding a downloads directory when MO2 is starting. To work around this you may need to blank out the path in ModOrganizer.ini, you can use the following command to do so, and then restart the game from Steam:
```
sed -i "/download_directory/c\download_directory =" /home/deck/Games/Enderal/EmissariesOfTux/modorganizer2/ModOrganizer.ini
```
At this stage, 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:
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:
<img src="https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/EmissariesOfTux/EmissariesOfTux_MO2ExecutablesCog.png" width="400">
Ensure that the executable paths for the "Enderal Special Edition (SKSE)" entry to match the following:
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.
If Enderal is install on **internal storage**, the Binary Path should be: