When the game is trying to issue a shader compile through its graphics API of choice, those are usually skipped, as we find the pre-compiled cache entry on disk." "On the Deck, we take this to the next level, since we have a unique GPU/driver combination to target, and the majority of the shaders that you run locally are actually pre-built on servers in our infrastructure.
"On the Linux/Proton side, we have a pretty extensive shader pre-caching system with multiple levels of source-level and binary cache representations pre-seeded and shared across users," Valve's Pierre-Loup Griffais told us. In this respect, Steam Deck has an advantage, because it is a fixed piece of hardware, just like a console. However, in a PC, where hardware spec varies so dramatically, the process is more complicated. We've talked about this a lot recently: it's not an issue on consoles because the fixed nature of the hardware means that shaders are pre-compiled and included in the package. Going back to our launch PC coverage, the stutter in the game was unbearable, with our working theory being that we were looking at yet another PC game suffering from shader compilation issues: split-second pauses whenever a new visual effect came into play. Were the issues truly resolved - and if so, how did Valve do it? In addition to that, we've since had a couple of further patches, which raises another crucial question: is Elden Ring on PC now fixed? Directly after finishing my Steam Deck review, I captured Elden Ring running 'out of the box' without Valve's optimisations in play, then tried out the 'fixed' experience.
One of the most intriguing stories to emerge from the launch of Steam Deck was the news that Valve leveraged their Linux-based Proton compatibility layer to effectively fix the problematic PC version of Elden Ring.
0 kommentar(er)
