ValveSoftware / ValveSoftware/Fossilize
Extremely long shader compilation times
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 780
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Using Proton Experimental as my default proton version, I'm seeing EXTREMELY long shader compilation times. I'm talking over an hour for certain games. Deadlock takes 15 minutes and re-compiles every time there's an update. I'm trying to run Once Human right now and it's been compiling shaders for 45 minutes and it's only at 57%.
I have a Ryzen 3700X and 32GB of RAM, along with 7900XT. I can compile the Cosmic desktop environment from source code faster than I can most of these shaders. I believe there's something wrong with Proton and how it's handling the compilation of shaders. If this is unusual or there's anything I can do to improve the situation, I'd love to know.
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
The issue names no source files, tests, or entry points. Start by reproducing the long shader compilation with Proton Experimental, Deadlock or Once Human, and the reported Ryzen 3700X/7900XT setup; inspect whether Fossilize is involved in the compilation path. Done requires identifying a reproducible cause and defining a concrete fix or explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100