• bitwolf@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    6 hours ago

    Wouldn’t flatpak insulate the problem? You can already get mesa through it.

    I’m sure 32bit shared object files are also free game.

    • imecth@fedia.io
      link
      fedilink
      arrow-up
      6
      ·
      6 hours ago

      Apparently there’s a few problems with the flatpak version, like you can’t run gamescope or start a steam big picture session.

      • bitwolf@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 hours ago

        Is that an nvidia only thing because both of those worked when I tried them. Although when using gamescope I couldn’t figure out how to get the steam overlay.

        I use big picture often though with NO man sky

  • 反いじめ戦隊@ani.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    7 hours ago

    I want everyone ITT🧵 & others to experiment setting your devices to year 2038, and report back what you need fixed.

    Let’s end obsolescence before that date.

  • Snot Flickerman@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    4
    ·
    edit-2
    12 hours ago

    Steam just needs to move to x64 and work on some way to port/emulate 32-bit for older games.

    Honestly this is on Valve imho, moreso than Redhat or Ubuntu or any distro providers.

    32-bit is dead and it’s somewhat absurd that Steam is still 32-bit.


    I just checked, and while I usually shit on Epic game launcher, theirs is 64-bit by default, they don’t even offer a 32-bit version of the store. This is squarely on Valve.

    • warm@kbin.earth
      link
      fedilink
      arrow-up
      4
      ·
      8 hours ago

      Bit of a weird comparison between EGL and Steam… Epic Games Launcher has been around for a fraction of the time Steam has.

      Steam hosts thousands of legacy titles and it’s great that most of them are still playable. Epic hosts only newer games.

    • CountVon@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      12 hours ago

      The Steam client is just a launcher. Why is it Valve’s job to make sure that legacy 32-bit games continue to run? They’re not the vendor of the game, and they’re not the vendor of the OS. They’re just a middleman. If the game vendor doesn’t want to patch it to 64-bit, and the OS vendor doesn’t want to maintain 32-bit compatibility, then there’s simply no more support for that combination of OS and game. Valve isn’t required to step in there.

      It may surprise you to learn that Valve already switched the client to 64-bit… for Mac. OSX hasn’t had 32-bit support since 2019, but it still has a Steam client! Valve didn’t do anything for 32-bit-only Mac titles, except drop the “Mac OS compatible” tag once Apple had dropped 32-bit support. That’s all they’re ever going to do for 32-bit-only PC titles, when/if OS vendors completely drop 32-bit support.

      32-bit is dead and it’s somewhat absurd that Steam is still 32-bit.

      Tell that to anyone who bought a legacy title on Steam and now wants to run it on modern hardware. Leaving the Steam client at 32-bit is simply a low-effort way to ensure that the OS has the 32-bit libraries that will be required by any 32-bit title the user happens to launch.

      • imecth@fedia.io
        link
        fedilink
        arrow-up
        2
        ·
        6 hours ago

        low-effort

        People always underestimate the work that goes into making sure stuff works. These packages need to be built so they add a lot of compile time to the pipeline, these packages have limitations inherent to 32 bits so they also add troubleshooting and bugs. This is time and resources that could be spent elsewhere.

      • sugar_in_your_tea@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        19
        arrow-down
        2
        ·
        11 hours ago

        Why is it Valve’s job to make sure that legacy 32-bit games continue to run? They’re not the vendor of the game, and they’re not the vendor of the OS.

        They have a responsibility to ensure that games they sell continue to work. They ship libraries on Linux so there’s a common base, and they should also do so for 32-bit games. GOG does this for older games using things like dosbox or whatever, and Steam should follow suit.

        Why would I use a launcher if it doesn’t launch games?

    • misk@sopuli.xyzOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 hours ago

      This is why it’s a proposal, and why I filed it more than 6 months earlier than strictly required.

      But just to clarify - we will need to drop support for 32-bit x86 at some point. It’s dead, and more and more software just doesn’t support being built and / or run in 32-bit environments at all.

      • Billegh@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        12 hours ago

        Honestly, fedora is pathologically open source. I admire their mission, but it’s difficult to use with the pathologically closed source world of gaming and related hardware. It’ll be for the best I think.

    • Billegh@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      12 hours ago

      Yeah, but we won’t get a choice if IBM tells Red Hat to drop x86 32bit upstream. Then fedora would have to maintain it entirely themselves, which they won’t.