search

ValveSoftware / Fossilize

A serialization format for various persistent Vulkan object types.
MIT License
584 stars 47 forks source link

Does fossilize compute shaders for every graphics card detected ? #110

Open Saroumane opened 4 years ago

Saroumane commented 4 years ago

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.

monosoul commented 3 years ago

I'd love to get an answer for that as well

amardhruva commented 2 years ago

I would too love to have an answer to this in case of hybrid graphics/optimus systems. Also does it have something to do with device-index flag?

minionprocyk commented 2 years ago

This has been an issue for me ever since fossilize was added to steam. I always turn the feature off since it seems to recompile everything every single time I load a game. I thought by keeping drivers on 1 version and lack of game updates there should yield no shader cache update, but it still runs. It just adds time to launch, sometimes a nontrivial time when launching something like FF XV. Before upgrading my cpu it would add sometimes add minutes to launch time.

hardware gist: https://gist.github.com/minionprocyk/c216ba4ed2a939f28a849f8c91e77c13