ValveSoftware / ValveSoftware/Fossilize
Accumulating many .foz files with Gamescope
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 780
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
So I am running Emulationstation-DE (non-steam game), Resident Evil HD, and Nier Automata all with Gamescope. I have been noticing that every time I start up with gamescope it creates a new .foz file inside of the steamapps/shadercache/fozpipelinesv6 directory. It looks like the way it is creating them is a bug because the hash is the same, but it keeps making copies. Take RE HD for example:
it is executed with gamescope -H 1440 -h 1440 -r 60 -f -- %command%
The Foz files that are created every time look like:

With emulationstation-DE, something that's been installed longer than RE HD and has been used quite a bit:

Note that for ES-DE the hash changed at some point, this may have been due to me installing new GPU drivers
With Nier its the same situation, a new .foz file everytime I launch the game
All the .foz files are the same size, is this a bug? This only happens when games are executed with gamescope. It does not matter if its a non-steam game or not
Edit: the screenshots are a bit dated now since I originally opened this issue over at https://github.com/Plagman/gamescope/issues/749, but I got no feedback, it might not be a gamescope issue perse, any help would gladly be appreciated
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported Gamescope command with Resident Evil HD, EmulationStation-DE, or Nier Automata, then inspect steamapps/shadercache/fozpipelinesv6 across repeated launches. Compare the generated .foz files and their hashes to determine whether identical files are being created unnecessarily; done means the cause is identified and duplicate accumulation no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100