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

Updated Troubleshooting (markdown)

Omni-guides
2024-04-30 09:23:51 +01:00
parent 8328591600
commit 1e30d2f34a
2 changed files with 24 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
Troubleshooting-and-FAQ.md Normal file

@@ -0,0 +1,24 @@
#### Help! I relaunched the game and my game save is gone!
Occasionally I see this, but haven't pinned down why as yet. It seems that on first successful launch, the game sometimes continues to use the save game location inside the prefix directory (compatdata) rather than the modlist savegame directory (usually in the profiles directory). It seems this is a one-off, and the game will always use the Modlist Save Game directory from now on.
So to fix, you can just copy the save games from the compatdata directory, for example:
```
/home/<USER>/.local/share/Steam/steamapps/compatdata/<APPID>/pfx/drive_c/users/steamuser/My\ Documents/My\ Games/Skyrim\ Special\ Edition/Saves/
```
Where <USER> should be replaced with your Linux user ('deck' if you are on Steam Deck) and <APPID> should be replaced with the appid number for your modlist entry in steam (can be listed with protontricks -l in a terminal/konsole)
Copy the save game files to the modlist save game directory, e.g.
```
/home/deck/Games/Skyrim/Tuxborn/profiles/Tuxborn\ -\ Deck\ CS/saves)
```
Again you will have to adjust the path to match your environment - user, path, and modlist.
---

73
Troubleshooting.md

@@ -1,73 +0,0 @@
The following are some tips for regularly reported issues.
---
**The mo-redirect.exe terminal window flicks up for a second, then vanishes!**
This is usually caused by either incorrect paths in the instance_path.txt and instance_download_path.txt files, or by the path to the Modlist containing a space. For example '/home/deck/Games/Skyrim/LostLegacy' is fine, but '/home/deck/Games/Skyrim/Lost Legacy' is not, even if you escape the space with a backslash.
---
**Skyrim crashes on startup after a short black flicker on the screen!**
Make sure you definitely disabled ENB - either by renaming the d3d11.dll file, or by disabling the mods, depending on your Modlist.
---
**My shell is messed up after using protontricks and I cant see anything I type!**
This is just something that happens when dealing with wine prefixes in a terminal. You can regain control of your terminal by typing 'reset' end hitting return, even if you can't see the characters you type.
---
**My ModList requires a vc_redist dependency**
VC Redist versions up to 2019 can be installed easily with protontricks, e.g. protontricks <APPID> vcredist2019
However, some newer lists also now require VC Redist 2022 and that has to be manually installed into the Proton prefix.
You can find it here for a manual download : https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
At the time of writing this, the latest redistributable bundles all versions from 2015 up to 2022. You can run the following one-liner to install vcredist2022, or follow the steps below it to do so manually:
```
APPID': APPID=`protontricks -l | grep "Journey" | awk {'print $6'} | sed 's:^.\(.*\).$:\1:' | tail -1` ; wget https://aka.ms/vs/17/release/vc_redist.x86.exe -O '/home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/dosdevices/c:/vc_redist.x86.exe' ; protontricks -c 'wine /home/omni/.local/share/Steam/steamapps/compatdata/'"$APPID"'/pfx/dosdevices/c:/vc_redist.x86.exe' $APPID
```
To install it manually, download the vc_redist.x64.exe file to your linux system, then jump into a protontricks shell and run `wine vc_redist.x64.exe` at the file's location to install it. Replace the APPID 3595949753 below with your APPID from protontricks -l
```
wget https://aka.ms/vs/17/release/vc_redist.x64.exe -O /home/omni/.local/share/Steam/steamapps/compatdata/3595949753/pfx/drive_c/vc_redist.x64.exe
```
If running it directly via terminal, run:
```
protontricks -c 'wine /home/omni/.local/share/Steam/steamapps/compatdata/3595949753/pfx/dosdevices/c:/VC_redist.x64.exe'
```
If you are running it via ssh, you will have to run it 'headless':
```
protontricks -c 'wine /home/omni/.local/share/Steam/steamapps/compatdata/3595949753/pfx/dosdevices/c:/VC_redist.x64.exe -q -norestart'
```
---
**binkw64.dll error when clicking play in MO2**
This is a known issue and happens on both Windows and Linux. Apparently it can be safely ignored. So far I can only attribute it to something in the 'Game Root' mechanism, but I do not yet have a way to fix or suppress the error, you can just close the window.
![image](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Septimus4-binkError.png)
---
**My Modlist uses 'Game Root' and keeps crashing**
I have seen instances of Game Root being built when starting the game, but it doesn't get 'unbuilt' if the game crashes. This can range from an error about not being able to find SkyrimSE.exe, all the way to continually loading the ENB binary even if you have disabled it in MO2.
To clean things up, you can go to the Tools menu in MO2, then Tool Plugins -> Root Builder -> clear
Than launch the game again, and it should rebuild the Game Root cleanly.
![image](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Septimus4CleanGameRoot.png)