this post was submitted on 24 Aug 2023
24 points (90.0% liked)

Steam Deck

14523 readers
24 users here now

A place to discuss and support all things Steam Deck.

Replacement for r/steamdeck_linux.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.

These are not enforced, but they are encouraged.

Rules:

Link to our Matrix Space

founded 3 years ago
MODERATORS
 

I got my Steam Deck 3 days ago and I just started exploring it. Given that I already have a large library of games on Epic Games, one of the first thing I did was installing the Heroic launcher. It worked well for some of the games (and not for others... like Hyper Light Drifter ;_; if someone knows how to configure it please help me). What I'm not understanding is: why do I need to have different proton versions installed for each game? Eg: one game requires GE 7.32 (what's GE by the way???), another game version 7.45, another one 7.20 etc etc etc... Why? I already had the latest version (8.0) of proton installed on my Steam Deck, shouldn't it be enough to run all other games being the latest version? 🫤

you are viewing a single comment's thread
view the rest of the comments
[–] conciselyverbose@kbin.social 13 points 1 year ago

Ideally, any change to any codebase would be a strict upgrade that's always better for everything.

But in practice, it just doesn't work that way. There's a lot of software out there that needs specific versions of specific libraries in order to not break, because even a straight bug fix can break software that was built and tested while that bug existed, if it was touched by that bugged behavior and the developers didn't know it was a bug. There are a lot of code bases that just rely on way too many dependencies to be able to actually read and comprehend the specification for every dependency they have. In theory that's not ideal, and leaning on a lot of external dependencies can break stuff in a lot of ways as they change, but it's how it is.

It's worse in some ways for games, because they take more shortcuts in the name of optimization, and in a lot of times are helped by graphics drivers to avoid breaking. Nvidia game ready drivers are a good example. There are games that have serious issues if you use a driver earlier than that, because nvidia will do hacky shit to fix the hacky shit the devs did and make it work.