Linux Gaming Thread

>engine: id Tech 5
Huh, neat. If it's got megatextures, it has to be good.

>The madman actually managed to end his career without making a single bad game.
Code Veronica and RE Zero happened.
TEW1-2 are also pretty shit.

Well most complaints have heard is about apex legends which I don't play. But I'm sure that you could get the shader cache the same way you get the game when you buy it on steam.

Well that because free alternative exist. For game you rarely have a comparable free alternative.

They also likely wanted to avoid heat from people in forums, youtube comments, and streams asking "Do I need to buy BF3 for this?" and morons replying "Just pirate it lol"

I don't care to dispute that. I heard the Blade Runner remaster was worthless. (On that note, the image in

>it's proprietary software either way
I don't care about proprietary. I just feel like I'm being cucked when I have to run a compatibility layer for the operating system I ditched, even if it works well enough that I don't notice the cost of that API translation.
>a not insignificant amount of native linux ports are done poorly enough that the proton experience actually is kind of better in those cases.
I understand that, but if you look up "Papers, Please" on ProtonDB, you'll see
>"Runs perfect with native version"
>"Native game and it works fantastic"
>"Native and runs perfect."
>"Runs perfectly well, no settings need to be changed."
so this developer obviously knows how to do a Linux port.
>I just don't understand what changes unless the game is buggy in proton, is all.
In the case of Obra Dinn, I don't actually care, because it's rated Platinum on ProtonDB and was officially verified for Steam Deck. I assume it works just fine. But it still hurts a little to see a developer abandon native Linux development for Proton, because there are developers who did exactly that but DIDN'T go on to release perfectly Proton-compatible games. Remember when Nightdive did native Linux ports? The Linux version of their Turok remaster works just fine for me. But then at some point they stopped doing Linux ports, and then you get shit like [...] [...], and unfortunately "dude just use Proton" doesn't sound quite as nice when you have to follow it up with "oh by the way you have to supply your own DLL file or it won't work correctly". Given that Nightdive was capable of non-broken Linux ports, a native Linux port of Blood: Fresh Supply presumably would have worked better out of the box than the Windows version running through Proton. I wouldn't have expected the Doom 64 port and Quake remaster to have Linux versions (because Bethesda is a subsidiary of Microsoft) but I wish they had kept making Linux ports for non-Bethesda games.

is outdated; add a crossed-out Tux for that game too. Blade Runner being Windows-only is especially shit, because the version that was already available on GOG was powered by ScummVM and thus ran natively on Linux.)

>spoiler
Yeah I get that. Sure, it can be satisfying to take something deliberately made only for Windows and use it on Linux anyway. But I think I can only get that satisfaction when the developer was actively against releasing on Linux, either because of Microsoft money or because they drank some kind of anti-Linux Kool-Aid. But when a developer isn't overtly anti-Linux, but rather pretends to support Linux by saying "umm just use Proton lol" without actually optimizing for Proton, then accepting that just feels kinda gross.

>I'm just in the camp of "if it works it works, I don't give a shit"
Also valid. I didn't mean to shit up the thread with complaints. Thank you for reading my blog or whatever the meme is

don't know much about scripting myself but the way i'd do it is i'd make a for loop for all the items in the folder and the switch-case based on file suffixes.

#/bin/sh

for i in $(ls ~/Downloads); do
case ${i##*.} in
png | jpg)
cp $i /path/to/reactions/dir;;
pdf)
you-get-the-point;;
esac
done

${i##*.} just means it takes the variable $i and removes from the string that's in it everything up to the file extension, and that is used to tell the script where to send the file.
granted i'm typing this on a phone and it's 2:30 AM so i can't exactly test this, but as you can see it's really not that hard. the best way to learn bash scripting is to just make scripts. if you don't know how to do something, read the manual or look it up.

Not him.
It definitely can, but I don't quite remember the best way to do it. I think you can read the standard input into a variable?
bash is kinda ugly and janky, but it really isn't that complicated. Just learn the syntax and don't create anything too big in it.
Or alternatively, just use fricking Python. GDScript is pretty much a python clone, I think, and it makes for perfectly fine scripts. It doesn't really matter what you use as long as it works fine, scripts are supposed to be slapped together in half an hour.

Look up Python, it's a scripting and programming language, really popular.
I don't think you can use Godot to rearrange your folders, and even if you can you really shouldn't, it's a waste of processing power and prone to errors.
But this scripting language you used to program Godot? It's based on a real general-purpose programming and scripting language with some changes. If you're familiar with GDScript, you can just use Python to exploit that, Python is also known as easy to learn. You'll have to install the python interpreter (it's usually just called "python" in repositories) and write a text file with the script inside, and that's about it.
Or learn bash instead. That's an option too. bash is useful on Linux.

I'm going to be honest I barely understand what any of that means, and I've only coded in GDscript to make a 3D platformer where you play as a cube
Can this shit ask me where I want to run it?

>${i##*.}
bash has a pretty useful feature called pattern expansion, it allows you to take variables and manipulate them without using external commands like cut or sed or whatever. like i said this particular string manipulation just removes the "*." pattern from the string in $i, which means everything up until the last dot. so if the file is a tar archive like "autoconf-2.71.tar.gz", doing this will leave you with "gz".
there's plenty more ways to manipulate strings like this, one i use a lot in my package scripts is ${var//./ }, this replaces all dots in a variable with spaces.
anyway, the rest is pretty self explanatory, if the file ends with png or jpg it gets copied to your meme folder, does something else for pdfs.
BY THE WAY, i used cp here on purpose, because it's better to use cp when you want to move files across different drives.
i hope this was coherent in any way.

cool

>#/bin/sh
this notes which shell should run this script. typically /bin/sh on linux is a symlink to bash but i just realized some systems have it set to a POSIX compliant shell like dash so that ${i##*.} won't necessarily work i think? i dunno
>for i in $(ls ~/Downloads)
for loops in bash work like this:

for var in 1 2 3 4; do
echo $var
done

it goes through a list of variables and does things with them. in this case it goes through the numbers 1-4 and prints each one to the console. "var" and "i" are just arbitrary names. $var is the way you call variables. you can also add curly braces when you call a variable, like ${var}, and this is really useful for pattern expansion which i'll get to.
now, you can run subcommands inside shell commands by using $(command). note the parenthesis here instead of the curly braces. so in this case, we want to start a for loop, and before we do that the shell executes a subcommand, "ls ~/Downloads", which lists all items in the Downloads folder. so imagine the entire list of items is then inserted into the for loop's definition.

for i in $(ls ~/Downloads) --> for i in file1 file2 file3...

>case ${i##*.} in
ok, so 2 things. first, the case statement syntax:

case [PATTERN] in
pattern1)
commands;;
pattern2 | pattern3)
commands;;
*)
commands;;
esac

[PATTERN] is just some text, numbers, whatever. if it matches one of the cases, commands are executed. the pipe character | allows you to specify multiple patterns for the same case. the * case is kind of like the default case, it's optional. double semicolons ;; are used to break the case statement.

case "red" in
red)
echo "the color is red";;
*)
echo "the color is not red";;

this prints "the color is red" and nothing else, because the statement stopped checking for cases after the double semis.
i ran out of space for this post, give me a minute.
[...]
if it works...

i forgot an esac in the 2nd case example :~~*

yeah