Awesome thanks!

I’ll play around with this idea on my tester laptop :)

Hmmm interesting.

What about the Mac version? And Mac software in general? I’m also new to Linux (and not a programmer), but wouldn’t that be easier to get running considering Mac OS is Unix based?

Sorry I kind of feel like I’m high-jacking your post, but it got me thinking and I’m probably too lazy to ever post about it myself.

Oh, one more thing regarding the ssh wizardry (lol!): It’s not that complicated. You can pass your command as last parameter. For example if you want to launch Dorfromantik (which you should btw), you could do it like this:

ssh me@mymachine "steam steam://rungameid/1455840"

That’s the whole magic. Like this it won’t start an interactive shell, but run the command and closes the connection once the command finishes.

If I remember correctly I had to give gamescope a flag to enable hdr at all. However there was an env too, to tell the windows games through proton, that the machine supports hdr. I’ll check my scripts later for you

Thanks to the community 🙏

If that’s the vkBasalt.conf file, sure, here it is, though I probably stole this from somewhere else online and most of it seems to be commented out:

#effects is a colon separated list of effect to use
#e.g.: effects = fxaa:cas
#effects will be run in order from left to right
#one effect can be run multiple times e.g. smaa:smaa:cas
#cas    - Contrast Adaptive Sharpening
#dls    - Denoised Luma Sharpening
#fxaa   - Fast Approximate Anti-Aliasing
#smaa   - Enhanced Subpixel Morphological Antialiasing
#lut    - Color LookUp Table
effects = cas:clarity:curves:multilut:dls:smaa:fxaa

clarity = "/opt/reshade/shaders/Clarity.fx"
curves = "/opt/reshade/shaders/Curves.fx"
multilut = "/opt/reshade/shaders/MultiLUT.fx"
bloom = "/opt/reshade/shaders/Bloom.fx"
 
reshadeTexturePath = "/opt/reshade/textures"
reshadeIncludePath = "/opt/reshade/shaders/"
depthCapture = off
 
#toggleKey toggles the effects on/off
toggleKey = Home
 
#Clarity.fx
ClarityBlendIfDark=50
ClarityBlendIfLight=205
ClarityBlendMode=2
ClarityDarkIntensity=0.400000
ClarityLightIntensity=0.000000
ClarityOffset=2.000000
ClarityRadius=3
ClarityStrength=0.600000
ClarityViewBlendIfMask=0
ClarityViewMask=0
 
#Curves.fx
Contrast=0.100000
Formula=4
Mode=0
 
#MultiLUT
fLUT_AmountChroma=0.750000
fLUT_AmountLuma=0.750000
fLUT_LutSelector=1
 
#casSharpness specifies the amount of sharpning in the CAS shader.
#0.0 less sharp, less artefacts, but not off
#1.0 maximum sharp more artefacts
#Everything in between is possible
#negative values sharpen even less, up to -1.0 make a visible difference
casSharpness = 0.8
 
#dlsSharpness specifies the amount of sharpening in the Denoised Luma Sharpening shader.
#Increase to sharpen details within the image.
#0.0 less sharp, less artefacts, but not off
#1.0 maximum sharp more artefacts
dlsSharpness = 1.0
 
#dlsDenoise specifies the amount of denoising in the Denoised Luma Sharpening shader.
#Increase to limit how intensely film grain within the image gets sharpened.
#0.0 min
#1.0 max
dlsDenoise = 0.17
 
#fxaaQualitySubpix can effect sharpness.
#1.00 - upper limit (softer)
#0.75 - default amount of filtering
#0.50 - lower limit (sharper, less sub-pixel aliasing removal)
#0.25 - almost off
#0.00 - completely off
fxaaQualitySubpix = 0.75
 
#fxaaQualityEdgeThreshold is the minimum amount of local contrast required to apply algorithm.
#0.333 - too little (faster)
#0.250 - low quality
#0.166 - default
#0.125 - high quality 
#0.063 - overkill (slower)
#fxaaQualityEdgeThreshold = 0.125
 
#fxaaQualityEdgeThresholdMin trims the algorithm from processing darks.
#0.0833 - upper limit (default, the start of visible unfiltered edges)
#0.0625 - high quality (faster)
#0.0312 - visible limit (slower)
#Special notes: due to the current implementation you
#Likely want to set this to zero.
#As colors that are mostly not-green
#will appear very dark in the green channel!
#Tune by looking at mostly non-green content,
#then start at zero and increase until aliasing is a problem.
#fxaaQualityEdgeThresholdMin = 0.0312
 
#smaaEdgeDetection changes the edge detection shader
#luma  - default
#color - might catch more edges, but is more expensive
#smaaEdgeDetection = luma
 
#smaaThreshold specifies the threshold or sensitivity to edges
#Lowering this value you will be able to detect more edges at the expense of performance.
#Range: [0, 0.5]
#0.1 is a reasonable value, and allows to catch most visible edges.
#0.05 is a rather overkill value, that allows to catch 'em all.
#smaaThreshold = 0.1
 
#smaaMaxSearchSteps specifies the maximum steps performed in the horizontal/vertical pattern searches
#Range: [0, 112]
#4  - low
#8  - medium
#16 - high
#32 - ultra
#smaaMaxSearchSteps = 32
 
#smaaMaxSearchStepsDiag specifies the maximum steps performed in the diagonal pattern searches
#Range: [0, 20]
#0  - low, medium
#8  - high
#16 - ultra
#smaaMaxSearchStepsDiag = 16
 
#smaaCornerRounding specifies how much sharp corners will be rounded
#Range: [0, 100]
#25 is a reasonable value
#smaaCornerRounding = 25

I’ve just done it yesterday for the Expedition 33 as well :D But I’ve used it for other games previously, it works surprisingly well on RDNA2.

LIMO would absolutely work to mod Skyrim from Linux.

It is universal, it will work with anything, you just may have to do a teensy bit more manualy configuration than some game specific mod tool.

It’s basically MO2, but linux native.

I’ve been using it for almost 2 years now, because I got tired of waiting for NexusMods to figure out how to make their own linux compatible modnmanager, and got very tired of having to do a custom MO2 install/container/whatever for every different game.

I’ve got my own 100+ mod sets working for Fallout New Vegas and CyberPunk 2077, via LIMO… on a Deck, on Bazzite.

LIMO supports FOMOD bundled mods, as well as more standard archives of files.

All you really have to do is construct a deployer, which is basically a pathway to the actual game directory, and then also set aside a directory for LIMO managed mods to live in.

It then does a virtual file structure that can be deployed/undeployed to/from the actual game directory, at whim.

You can manage load orders, it has mod/file conflict indicators, you can tag and group various kinds of mods by doing regex filters, you can have different mod profiles, one very neat thing it does is an automatic attempt at directory matching, ie, if somebody made a mod that didn’t properly replicate the game’s dir structure, it’ll indicate that and allow you to tweak it a bit… don’t think there is a super simple UI way to export and then share a modlist/profile yet, but presumably they just live in the var/apps/flatpak/whatever dir, somewhere.

… the only problems you may run into are things that:

Fully overwrite the actual game exe, like NVSE, but this can be worked around by maybe setting up a new profile for however you are launching the game, to point at that exe, or just manually going in and renaming the old exe to .exe.OLD or something like that, and then naming your mod exe to the same name as the original game exe, and turning off any auto updates.

You’ve well described a decent solution for handling SKSE, so good work!

Also problematic are things like… massive archive rectifiers, that are actually just exes or batch files or whatever, that go through and make a ton of edits to core game archive files.

Because these archive type files are basically compressed in their own way, you can’t just point by point overwrite them with minor loose files, you have to make the corrections and then basically recompress them, thats what these rectifier exes and batch files do.

Generally speaking, you can just run these rectifiers through the same proton config that you use successfully for the game itself, though you may have to use ProtonTricks to add in extra dependencies like vcrun20xx or whatever, also it can be worth it to throw in some stuff to help render fonts properly with the right antialiasing.

Just make sure you’ve put them in the equivalently correct dir in the game as you would for following windows based instructions for using them.

Any mod that ends up, in the course of being run with the game, actually creates/writes new files beyond what is just directly installed by LIMO.

When you undeploy mods via LIMO… well, LIMO doesn’t know that some advanced scripting mod writes its own config and ini files on the game executing with the mod for the first time, it doesn’t know those exist, so it doesn’t remove them.

For that, you again just kinda have to manually either just go in and remove them from the game dir, or, you could run those kinds of mods initially, then go into that directory where LIMO stores uncompressed mods, and add those files manually in there.

That way LIMO knows they exist, and deploys them with the mod, so your mod sees that those files already exist and thus isn’t trying to do what it thinks is an initial setup every time, potentially causing lots of silly shenanigans.

I’ve not heard of WinBoat… What I do is just use ProtonTricks to manage the Steam compat data/prefix data for the game I am modding, and if any mod needs some kind of Windows dependency to work properly, ProtonTricks can handle installing and managing that, albeit through a somewhat clumsy UI, it is at least less tedious than manually looking up Steam’s compat data/prefix locations that are all done by game id.

Just add in your dependency for that mod, to that game’s compat/Proton prefix.

Hah, if you think that’s bad, try fucking figuring out which steam workshop mod is which, they’re also all done by workshop mod ids for the folder names, so its fucking opaque… i think there are some websites that have searchable ways of solving that problem tho.