Valve claims it's monthly but my previous survey was October last year so I doubt that. I don't believe it was related to the article in the OP. They seem to just randomly pop up after an update. A surprise to be sure but a welcome one.
grimaferve
joined 1 year ago
I did my first Linux Steam hardware survey yesterday so I'm doing my part!
'Smashing!'
Nigel looks adorable. Sending virtual headscratches his way.
There's this aptly-named utility that I'm currently using:
https://github.com/nvbn/thefuck
I do think GUI is the way to go for "typical" usage, but if you wanted to set up a faster way to run a command you use often, you would create an alias to handle a complex command or something you do often.
For example, I have 'updateall' as my command to run 'sudo apt update && sudo apt upgrade && flatpak update'. Why not GUI for this? I like to see what's going on during my updates. It's also kind of satisfying for some reason.
Anyway, I suspect your problem then would end up being not running a syntax, assuming it even exists, but the correct syntax, which I often encounter, but that's what 'history | grep' is for.
Sorry if there's a lot of technical terms.
My anecdotal experience is that Skyrim modding under Linux worked surprisingly well. Despite that I think I would still say "YMMV". I have it running under Lutris-GE-Proton8-13.
I used the GOG release because having local access to the installer is a major win. Note that even if you don't install the AE upgrade it's the same version number, 1.6.659 so bear this in mind when installing SKSE64 and mods. I think there's a specific release of SKSE64 for GOG. Many mods label that version as AE only, which isn't true of the GOG release.
I chose to install in Lutris because of how easy it is to manipulate prefixes. I had issues with the automated scripts, which I expected. So I did it myself.
I downloaded Skyrim from GOG and installed Skyrim using the "Install a Windows game from media" option, then run once from the launcher to ensure everything was initialised before modding.
Inside this prefix I installed MO2 using "Run EXE inside WINE prefix".
I chose that mod manager because I used it on Windows and it worked just fine. I don't know a lot about Vortex. There's a DLL to add support for Epic and GOG installs of Skyrim. I duplicated the Skyrim SE runner and changed the target to ModOrganizer dot exe. There's a UI bug that makes reordering mods act weird, just click another mod entry if it gets stuck.
The Nemesis issue I had, which appears to be a Linux/WINE problem - the solution given (Extract it to the Data folder then run the executable from MO2 with VFS) worked for me.
TBH my modlist is pretty tame compared to most that I've come across so I didn't expect many problems. LOOT worked as expected so I just let LOOT handle my load order.
There's probably more to it but this is what I remember. Happy modding!
Modlist
Nemesis issue
Mod Organizer 2
Super useful tool to help manage proton versions