• @[email protected]
    7•1 year ago

    The NTFS warning is a little disingenuous. I wouldn’t recommend people go with it if they’re choosing Linux only obviously, but I’m going to say with years of personal testing about 99.9% of things work just fine using an NTFS drive. I think it’s been years since I had any kind of issue with game data that I attributed (and maybe falsely) at the time to the NTFS filesystem.

    In steam you’ll need to symlink your compatdata folder to a linux filesystem, but that’s about it.

    • @CarlosCheddar
      3•1 year ago

      I switched to BTRFS and used a Windows plugin that allows it to read/write to it. It solved all my NTFS and EXFAT issues and works great.

      • @[email protected]
        5•1 year ago

        I’ve tried this also. It works alright unless you write files in Windows, it will set the UID to the Windows SID. WHen you use a Steamlibrary and move back and forth, games that are updated in Windows can give you permission errors in LInux, etc.

        It’s all workable and definitely an option, but WinBTRFS has a performance overhead, and the dualing permissions made it not a perfect solution.

        • @CarlosCheddar
          3•1 year ago

          Yeah I remember having permission issues that were easily fixed with chown but they were hard to notice. I haven’t booted to Windows in over a year now so I must’ve forgotten lol.

          • MKCEnglish
            1•1 year ago

            I’m pretty sure WinBTRFS’s readme has a section about properly setting up the user and group permission stuff. Essentially just providing the Windows UUID to Linux POSIX equivilant, which generally ends up fixing all the permission related problems. The only real caveat is it not working with SuperFetch, so files aren’t cached in memory and have to be loaded from disk with every read.

    • @[email protected]
      3•1 year ago

      I don’t even symlink compatdata and haven’t run into any problems. The whole NTFS thing is wild :D