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.
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:
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.
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.
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.
A good question on Bazzite lol
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.
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:
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:
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.
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.
Oh! Good to know!
It’s still a PITA they should just use the game name for compatdata.
You literally just right click the game in Steam and click browse files.
Don’t most games keep save files separately from the main game files?
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.
could you not open a console and use find or grep?
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.
ah. makes sense.
find is really easy.
find -type f -name "*wildcard_filename*"find -type d -name "*wildcard_directoryname*"I’ll have to remember this, thanks.
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: