• Zacryon@feddit.org
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    16 hours ago

    If my quick maths has the correct assumptions, then we can store 225 Petabytes of data in the balls.

    Human sperm contains about 3 million base pairs (haploid genome).
    Each base pair of DNA (A, C, G, T) is encodable with 2 bits.
    3 million * 2 bits / 8 (to convert to bytes) = 750 MB.
    Using a rough and imprecise average of 300 million sperm cells stored in testicles, we get:
    300 million * 750 MB = 225 PB.

    Plenty of space for your savegame data!

  • BurgerBaron@piefed.social
    link
    fedilink
    English
    arrow-up
    47
    ·
    1 day ago

    User/Appdata, User/Saved Games, User/Documents/a bunch of shit but usually My Games unless you’re EA Games or Electronic Arts or 4000 other special developers.

    You can never escape if you game on linux distro, plus you add non-conforming special devs on linux next for native apps. Too many .fuckface folders dumped in /home.

    • Javi@feddit.uk
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      18 hours ago

      Tbf the reality for like 90% of people gaming on Linux the path is something like

      ~/home/.steam/steamapps/compatdata/{game_id}/c/users/steam user/appdata

      etc… as most will be leveraging proton via steam. And I reckon the other 10% are making use of proton via lutris or heroic… Or if they’re feeling particularly oldschool, just a wine installation.

      IMO it doesn’t make sense for Devs to build games directly for Linux, as the long term compatibility is better via proton than it seems to be for native Linux releases. I have a catalogue of games that offer both installers, and I’d say around half of the Linux versions are fucked. (Tesla Vs Lovecraft is a prime example for me, as it even borked my soundcard for a while when it crashed, which was a real pain to sort, but the windows emulated version doesn’t have this issue.)

      And I say this as a Linux enthusiast/Microsoft doomsayer. Using a compatibility layer unifies the way distros interact with games… It enables the wide diversity in Linux without sacrificing compatibility when choosing a distro.

      Edit: I just pulled these numbers out my arse to make my point. I have no data on how many Linux users actually use steam.

      • BurgerBaron@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        10 hours ago

        I think you missed my point. The same song and dance of finding where the hell the game dumped its config files and saves still happens no matter what OS you use to play Windows games on. Adding native games to the pile is just that: additive.

        Please note I don’t really care that strongly, certainly not enough to start symlinking a folder I’ll visit a single time ever to tweak a setting like another suggested lolol.

      • HereIAm@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        17 hours ago

        Since each windows game installed through lutris and steam run in their own sandbox where they are free to mess with things, I don’t see why the same couldn’t be done for Linux games. It’s not exactly an ideal solution, but it would abstract each game’s quirks in where they want to store files just like steam does with the compatdata folders. I know this is basically what flatpak does.

        • Javi@feddit.uk
          link
          fedilink
          English
          arrow-up
          2
          ·
          17 hours ago

          Oh definitely; and I don’t think there is a great deal of users that would argue for the use of snap over flatpak either, so flatpak would be an ideal unified compatibility solution.

          Not sure if I’ve seen a commercial game with a flatpak release; and given the open nature of flatpak, a company (ie: steam) could theoretically implement their own gatekept repository to manage purchases etc…

          The main hurdle with adoption is native compatibility with steam; if they started hosting and supporting flatpak installs, the concept would likely stand a better chance. I suppose you could run the whole application sandboxed, which would theoretically sandbox every game installed; but canonical try that, and well… If you search snap steam, you’ll see the issues that brings about.

    • PieMePlenty@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      17 hours ago

      Any idea how proton handles this for windows only games running on linux? Where is My Documents mapped to?

      • LucidNightmare@anarchist.nexus
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 hours ago

        The easiest way I’ve found my game folders through Proton is to use KDE Runner. I look up the game on PCGamingWiki and find the Steam ID of the game under Game data then Configuration file(s) location then i.e. 3321460 for Crimson Desert. So, I put 3321460 into KRunner, and it will usually show me the folder. Then I just save the top level folder compatdata onto my Dolphin Places for easier finding later. I still have to find the Steam ID for the game on PCGW, but the folder is easier to use to search than KRunner sometimes. :-]

        • Javi@feddit.uk
          link
          fedilink
          English
          arrow-up
          3
          ·
          15 hours ago

          @PieMePlenty@lemmy.world I should clarify that was me pulling the path from memory. So might not be 100% accurate but it explains how the path works with proton/wine when using steam.

          Essentially WINE creates a windows styled directory, with all the core folders, and then the emulator uses this as it’s root directory.

          Documents is a great example. On Linux the document path is

          /home/<USER>/Documents.

          On windows it’s

          C:\users\<USER>\documents

          If we use the default wine settings, the path for the wine documents folder on Linux is

          /home/<USER>/.wine/drive_c/users/<USER>/documents

          Any program running in wine will only see the files from drive_c and down, emulating how a windows environment would work.

          Happy to answer any questions if that isn’t clear. Feel free to DM.

    • MonkderVierte@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      15 hours ago

      You could go to Steam/steamapps/compatdata/<game-id>/pfx/drive_c/users/steamuser/ and symlink the respective directories. It’s how wine handles integration anyway, so 100% compatible. If only wine had a cli option or environment variable to change that path.

  • Treczoks@lemmy.world
    link
    fedilink
    arrow-up
    14
    ·
    1 day ago

    Depending on context, even someone who is a developer might ask such a question. Some games for example save files in the weirdest places, and if you look across the Windows/Linux border, those locations are totally different.

    • The Picard Maneuver@lemmy.worldOPM
      link
      fedilink
      arrow-up
      9
      ·
      1 day ago

      I haven’t used Bazzite, but I recently needed to find my save data on PopOS for a steam game that runs with proton, and it was so buried in subfolders that I only found it after asking chatgpt.

      • KoboldCoterie@pawb.social
        link
        fedilink
        English
        arrow-up
        20
        ·
        edit-2
        1 day ago

        Anything using a compatibility layer (e.g. Proton) through Steam is going to have an entry in the ‘compatdata’ folder in your Steam library. Inside that, there’s an entire windows filesystem folder structure, so finding the actual data is a two part process:

        • Find your compatdata folder in your Steam library; usually you can do this by rightclicking a game in Steam -> Browse Local Files -> go up 2 folder levels (to steamapps) - should be a compatdata folder in there. Open that, find the folder whose name matches the app ID, and you’re in business.
        • Navigate the fake Windows folder structure to wherever the save data would be stored in Windows. [user] is always ‘steamuser’.

        It looks like a really obtuse file path because it’s essentially two filepaths in one, but it’s not as bad as it looks to actually navigate.

        Here’s an example - Linux file structure boxed in red, windows file structure boxed in green:

        • The Picard Maneuver@lemmy.worldOPM
          link
          fedilink
          arrow-up
          6
          ·
          1 day ago

          That’s very logical, I just wish it was more readable, especially that subfolder after compatdata that’s just numbers. I’m pretty sure that directory was full of folders with non-descript numbers on my pc, and the only way to proceed to the windows-style filesystem was to guess + check or have a reference to match it.

          • KoboldCoterie@pawb.social
            link
            fedilink
            English
            arrow-up
            14
            ·
            edit-2
            1 day ago

            The numbers are just the Steam app ID - you can easily find this by just opening the Steam store / community page for the game. There’s nothing stopping two games from having identical names on Steam, so they need a unique identifier to index them by, and the app ID is the logical choice as it already exists and is already unique per game.

          • zewm@lemmy.world
            link
            fedilink
            arrow-up
            4
            ·
            1 day ago

            Depends on the game engine I suppose. You can just browse up a few directories inside the prefix and find the second common place. Usually it’s c:\users<username>\appdata\ and sometimes even get stored in My Documents.

            But using steam to browse files will get you directly into the prefix. After that it’s a matter of browsing around to the common locations the same as you would on windows.

        • The Picard Maneuver@lemmy.worldOPM
          link
          fedilink
          arrow-up
          2
          ·
          1 day ago

          I don’t have much experience searching like that yet and still default to using the gui for navigating directories… I’m still a relative linux noob.

          • GreenKnight23@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            1 day ago

            ah. makes sense.

            find is really easy.

            find -type f -name "*wildcard_filename*"

            find -type d -name "*wildcard_directoryname*"

              • village604@adultswim.fan
                link
                fedilink
                English
                arrow-up
                2
                ·
                1 day ago

                It’s best to not run it on your root folder, because you’ll be greeted with a wall of errors from /proc or other system directories.

                The main ones I check are:

                • /usr
                • /var
                • /opt
                • /etc
                • /home
                • /lib (usually only when troubleshooting compile errors)