ValveSoftware / ValveSoftware/Fossilize

Does fossilize compute shaders for every graphics card detected ?

Open
#110 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
780
Forks
78
PR merge metrics
No merged PRs in 30d

Description

Hello,
it is more a question for now (but it could become a feature request)

Does fossilize compute shaders for every graphics card detected ?

I recently plugged a 2nd graphics card (radeon HD 6450) in addition to my main RX 5700 XT (so both are AMD).
(I use this old card only for a few games that are best displayed with the analog VGA output.)

Since that moment, I noticed that steam is computing shaders for games already processed : is it doing the whole library again for the 2nd graphics card ?

If that's the case, it would be nice to have more control and prevent shadercache duplicates.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. First determine whether shader computation is duplicated per detected graphics card, then define the requested control for avoiding duplicate shader caches and document how completion would be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.