Hello @AtFreezingPoint, you're going to need to explain what you're currently seeing in substantially more detail for this to be considered a new, separate issue from the general discussion on #8076. Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. After that's added, give me a ping to re-open this issue report.
Steam's shader pre-caches are designed to be incrementally updated and in the common case most of the shaders replayed by fossilize_replay get matched to the video driver's on-disk shader cache which was previously warmed up, and that completes fairly quickly.
Hello @AtFreezingPoint, you're going to need to explain what you're currently seeing in substantially more detail for this to be considered a new, separate issue from the general discussion on #8076. Also, please copy your system information from Steam (
Steam->Help->System Information) and put it in a gist, then include a link to the gist in this issue report. After that's added, give me a ping to re-open this issue report.Steam's shader pre-caches are designed to be incrementally updated and in the common case most of the shaders replayed by fossilize_replay get matched to the video driver's on-disk shader cache which was previously warmed up, and that completes fairly quickly.
Ughhh... I can indeed do the gist part and all but just wanna ask, Steam isn't supposed to use like 10% of my cpu for like 2 hours every time i start the Linux client with the setting "Allow background processing of Vulkan shaders" on, right?
Background processing of pre-cache shaders is expected to be 25% of CPU cores or until disk IO pressure is saturated.
@kisak-valve just quick question, is it not at all possible to just distribute the shaders like pre-compiled so the local hardware doesn't have to be used?
I don't pretend to know how it works but it seems to me that something compiled for use on my machine is probably not going to be compatible with your machine & vice versa.
I don't pretend to know how it works but it seems to me that something compiled for use on my machine is probably not going to be compatible with your machine & vice versa.
I mean it's just textures, aren't they? Like drawings on paper on crack...
Copy of this issue, same setup pretty much & it turns out that it was somehow reintroduced?