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 Skyrim: Tuxborn (markdown)

Omni-guides
2024-04-04 10:03:32 +01:00
parent b0642e68b1
commit 0de3ef2b7b
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Skyrim:-Tuxborn.md

@@ -240,10 +240,12 @@ With NPC Voices fixed, and vcredist2022 installed, we should now be ready! Selec
![IMAGE MO2Play.png](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-MO2Play.png)
This takes quite a bit of time to start. Once it had loaded though, performance was as expected in the menus. On first launch, you will see a message about Shaders being compiled, this is normal and just allow it to finish before continuing. It is also very common for the modlist to _crash the first time you launch it_. Subsequent launches should be fine.
This takes quite a bit of time to start. Once it had loaded though, performance was as expected in the menus. On first launch, you will see a message about Shaders being compiled, this is normal and just allow it to finish before continuing. It is also very common for the modlist to _crash the first time you launch it_, especially with an error message regarding the "Blunt and Blade" mod. Relaunching the game should fix this and you'll not see the error, or a crash, again.
![IMAGE CompilingShaders.png](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/blob/main/images/Tuxborn/Tuxborn-CompilingShaders.png)
In some rare cases, I have seen the game not accept input when trying to press 'R' or the 'X' button when naming your character the first time you successfully launch the game. Again a restart of the game appears to fix this. If you get into this situation, save your generated character as a preset (from the Preset tab in the top right), exit and relaunch Tuxborn, then load your Character Preset (again using the Preset tab in the top right) - I haven't yet got to the bottom of why this happens as yet, but will try to figure it out.
On Steam Deck, use either the Tuxborn - Deck profile and lock the framerate at 40FPS, or the Tuxborn - Deck CS profile and lock the framerate at 30FPS. I find sticking it at 40 or 30 depending on the profile, and then turning off the FPS counter lets me just get on with the game, feeling fluid enough that I don't think about the FPS any more.
Keep in mind that you are running a collection of mods, through the Proton compatibility layer - so save often, and maybe even make backups of your save-games, just in case ;)