ValveSoftware / ValveSoftware/Fossilize
[Enhancement] show status of the current shader compilation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 780
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
As a desktop user,
I want to verify the status of shader compilation
So that I can get some expectations of remaining work, time, and potentially decide to stop the processes.
One of the things that I believe makes people extra annoyed at fossilized taking a long time to compile shaders, is the fact that once it starts, there's no way to verify what's going on, expected runtime, or even a percentage on total work...
Basically, a simple improvement would be allow a user to even know what's going on in the first place.
What shaders are being compiled?
How many files?
How long on average do they take?
Even if possible, generate a historical database of time taken for shader compilation for each game, so we can get an average expected time per job.
Help us understand, and that may even allow users to detect leaks/stuck jobs.
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
No files, tests, or entry points are named. Start by mapping the current shader-compilation workflow and its observable jobs, then define acceptance criteria for reporting progress, expected duration, cancellation, and historical timing before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100