Reading from NTFS is nearly flawless. Writing and actively using it is pretty bad occasionally though, to the point where steam doesn’t support it and recommends against it for game libraries on Linux.
That may be an old issue, but I just set up a couple of NTFS drive Steam libraries on Linux last week and it didn’t give me any errors or warnings about the drive format. But I did have big issues with the Flatpak edition of Steam - it couldn’t even write to a local second ext4 partition. Had to switch to .deb Steam install to fix all that
You might know this already, but some (all?) flatpaks are denied access to most drives in the system. I’ve used Flatseal to address that issue when it comes up, though there may be better ways.
Yes I did read up on that and tried using Flatseal for permissions granting, but it didn’t work so I didn’t troubleshoot it very far before doing to the .deb install
Reading from NTFS is nearly flawless. Writing and actively using it is pretty bad occasionally though, to the point where steam doesn’t support it and recommends against it for game libraries on Linux.
My experience was miserable attempting to do so, to the point that it was better to just nuke everything across 4 drives and start over
That may be an old issue, but I just set up a couple of NTFS drive Steam libraries on Linux last week and it didn’t give me any errors or warnings about the drive format. But I did have big issues with the Flatpak edition of Steam - it couldn’t even write to a local second ext4 partition. Had to switch to .deb Steam install to fix all that
You might know this already, but some (all?) flatpaks are denied access to most drives in the system. I’ve used Flatseal to address that issue when it comes up, though there may be better ways.
Yes I did read up on that and tried using Flatseal for permissions granting, but it didn’t work so I didn’t troubleshoot it very far before doing to the .deb install