Thread 724614763

Why are developers pretending to care about the steam deck now?

>>724614763 (OP)
Covering their own asses in case people flee Windows 11.

>>724614763 (OP)
>game went from 3GBs to over 15GBs
What the actual fuck happened? I played it like around two years ago and game was 4 gigabytes but now it wants 15 lol.

>>724614847
The 20th anniversary update is practically a remaster of the game.

wow a game from 2005 is now verified

>>724614931
Only took them 20 years

>>724614912
>have to download over 10gbs of jeet upscale texture bloat
No thank you very much. I will not play this game then.

they dont its just easy puublicity

>>724615684
i boughted it

>>724615684
for some reason I read that as they don’t eat ass publicly

>>724614763 (OP)
Basically bragging that they can actually optimize their game to run on one of the most outdated pieces of shit ever
Which is a pretty good flex these days

>>724614763 (OP)
croteam has been bleeding money and talent for a decade now, this is just their latest attempt at an easy cash boost
see also: doing a bundle with onirism, adding steam cards to the game, or adding some SS4-inspired features to it
SS2 must be the easiest of them to work on

>>724614763 (OP)
It's a good minimum set of specs to target, and also in case you failed to notice Windows has been sucking the big fucking donkey cock lately.

>>724614763 (OP)
Thanks just downloaded it to my steam deck

>>724614763 (OP)
>muh Steam Deck verified
These fuckers had beta version of native Linux build that you can play even today (although not without tinkering). Yet they decided not to revive it...

>>724618602
Proton compatibility is good enough nowadays.

>>724615119
your fault for using steamt

>>724616521
The less reddit you act the better, anon.
>inb4 how do you know
Because redditors act like faggots and this is faggot behavior.

>>724618602
proton is better because of linux shitty package design without backwards compatibility that is an ever changing target

>>724618946
>linux shitty package design without backwards compatibility that is an ever changing target
1. There's a single target system called Steam Linux Runtime which developers could use
2. Only shitty games are affected that because they're linked against the libraries they have reason to link. That said there aren't many shitty games out there. I can play 25 years old native Linux games on my current Arch Linux system with no runtimes relying on system libraries only. They only game I've encountered so far that is completely broken is BioShock infinite.

>>724619873
>1. There's a single target system called Steam Linux Runtime which developers could use
hard dependency on steam is a worse alternative>>724619873
>Only shitty games are affected that because they're linked against the libraries they have reason to link
they are often dependent even on specific compiler versions

>>724621979
This is why you ship potentially problematic LGPL libraries with your application and statically link against musl and anything MIT/zlib/whatever licensed

>>724622216
Doesnt solve the issue, it's not about licences

>>724622376
Did you even read the second half of my sentence, retard?
Use musl instead of glibc and statically link everything you're legally permitted to.

>>724614763 (OP)
deck owners are high end users with money to spend that are also likely indie friendly, because it's a machine that can't play many new AAAs.

Indies also need all the help they can get to boost themselves in the algo. for AA devs like OP it's not as important.

>>724614763 (OP)
guess i'll check it out

>>724621979
>hard dependency on steam is a worse alternative
Steam runtime doesn't impose hard dependency on Steam, it's a free software that anyone can use without Steam, that's how umu-launcher
>they are often dependent even on specific compiler versions
Wtf are you talking about? What does the compiler have to do with compiled binary ready for shipping? You can run any executables without any compiler installed in the system. Compiler is only needed when you're compiling from the source and guess what it's a common problem on any system: project that was made in one version of visual studio might not compile in the future versions of it.

>>724624154
Actually, he's not wrong.
Most stuff ends up linked against libgcc (so if your game is linked to libgcc from GCC15, it won't work for GCC14's libgcc) and anything written in C++ is extremely ABI sensitive, so if the default C++ standard is changed in a new GCC version sometimes it can break everything and necessitate a full rebuild of everything.