[00:03] persistent problem in PC gaming for years now. And it's something we've covered extensively here at Digital Foundry, particularly through our friend and colleague Alex Battaglia's ongoing hashtag stutter struggle. But it turns [00:16] out Alex's coverage inspired an independent developer operating under the hacker alias Blue Heisenberg to take matters into their own hands. Turns out that Blue Heisenberg is one of our supporters, and he says that Alex's [00:30] stutter elimination ambitions were a key driver in producing this intriguing project. The result is SCS Killer, a free open-source application designed to pre-compile shaders and graphics pipelines before you play, potentially [00:43] eliminating one of PC gaming's most frustrating problems. Now, we've been putting it through its paces across a wide range of PC games over the last week, and while some of the results are clearly remarkable, as reported [00:56] elsewhere in the PC press, we've also uncovered some significant limitations and trade-offs. So, how exactly does SCS Killer work, and how effective is it in practice? Well, let's find out. But first, [music] this. Digital [01:10] Foundry's PC coverage is brought to you by Alienware and its new flagship gaming monitor, the 5K 2K [music] ultrawide Alienware AW3426QW. include ultrawide functionality [music] testing carried out on this display in [01:25] concert with the Alienware Area-51 desktop [music] PC. This cutting-edge screen features a native 165 Hz refresh rate and a massive curved RGB stripe tandem OLED panel, the first of its kind in this 39-in format at 5120 by 2160 [01:41] resolution. That means colors are bright and vibrant with no wash out, while OLED text fringing is eliminated, making it impressive [music] not just for gaming, razor-sharp text clarity. Dual mode functionality is there for those who [01:54] want impressive e-sports [music] support with a range of options culminating in a 2560 by 1080 resolution running at a max 330 hertz. Connectivity-wise, [music] this full DisplayPort 2.1 support dual HDMI 2.1 inputs along with USB-C with [02:10] DisplayPort out mode functionality and 90 watts power delivery, [music] which is perfect for attaching laptops. Meanwhile, an integrated KVM means that one keyboard [music] and mouse can switch between connected PCs. The [02:22] Alienware AW3423DW [music] delivers massive screen real estate, supplying image quality and impressive adaptability for a wealth of PC gaming Check out the link in the video description below to find out more. [02:37] description below to find out more. >> [music] ready to run on every GPU. Instead, they contain shader bytecode that needs to be combined into graphics pipelines alongside the appropriate rendering [02:52] state, which the GPU driver then compiles for your specific hardware. SCS Killer attempts to reconstruct these pipelines from the game's files and precompile them into the GPU driver's shader cache before you launch the game. [03:07] So, when the game subsequently requests those same pipelines, the driver retrieves the already compiled versions rather than compiling them on the fly during gameplay. So, this potentially avoids those dreaded shader compilation [03:22] stutters. The application also includes an optional recorder that observes how a game constructs its pipelines during gameplay, helping SCS Killer identify combinations it might otherwise miss. For our testing, we're using a Ryzen 5 [03:36] For our testing, we're using a Ryzen 5 5600 paired with an RTX 4070 Ti Super. Now, this is a deliberately unbalanced setup with a relatively modest CPU combined with a relatively powerful GPU, which helps to better expose shader [03:50] compilation stalls that might be less apparent on faster processors. We're focusing exclusively on Nvidia for this video with AMD testing something we may explore separately in a future video. Alongside what appears to be an Unreal [04:05] Engine based solution that Team Red has added stealthily to recent driver revisions. So, first of all, let's talk methodology. To establish our baseline, we clear the relevant shader caches using Nvidia app or SCS Killer's own [04:19] option where applicable. Then we launch the game, allow any built-in shader pre-compilation step to complete, and capture our first gameplay run. Just be clear, this is required to simulate the first play experience where no cached [04:35] first play experience where no cached shaders exist. Then the game is closed, we clear the shader cache through SCS Killer, and let the application finish pre-compiling before relaunching the game and repeating the exact same [04:48] gameplay sequence. So, let's begin with Silent Hill F, a game we covered at launch where we encountered unusual shader compilation behavior. The game does have a short shader pre-compilation step when first launched after a driver [05:02] update or after clearing the shader cache, but it doesn't cover everything. And one of the clearest examples comes right at the beginning, amazingly enough. In the opening cutscene, the character's arms are initially missing, [05:15] only popping into view a moment later. Now, we saw this back at launch and remarkably, it's still happening today. The game compiles the necessary skin shader asynchronously, meaning the arms aren't rendered until that shader is [05:28] ready. Astonishing stuff. With SCS Killer, that problem disappears. The character's arms are visible from the outset with none of that delayed pop-in. So, even before looking at frame rates, performance, frame time spikes, etc., [05:42] there's a noticeable, visible improvement. Moving into gameplay, we can compare frame times directly. On the left, we're running with a cold shader cache after completing the game's built-in pre-compilation step. On the [05:54] right, we're using SCS Killer before we boot the game. Despite that initial pre-compilation, the default run still suffers from stutters, seemingly a combination of shader compilation and the usual Unreal Engine traversal [06:08] hitches. SCS Killer reduces or eliminates many of them. So the result is much closer to a second run through the same area once the relevant shaders we're getting that benefit on the very first run after using SCS Killer. The [06:25] disappeared leaving what appears to be the usual Unreal Engine traversal or streaming hitches. Loading directly into a later section of the game reveals updated your graphics driver or cleared the shader cache then returned to an [06:40] existing save. Even after the game's short pre-compilation step entire initially missing with buildings and other objects gradually appearing in front of the player. After using SCS Killer, the environment renders [06:54] correctly from the moment we load in. One detail worth pointing out however, Killer run on the right whereas they're rendered correctly on the left. We've reproduced this shadow rendering bug without SCS Killer so it doesn't appear [07:08] to be caused by the application. Continuing through this area there's a further performance difference. The default run suffers a noticeable frame rate drop lasting several seconds before recovering whereas performance with SCS [07:20] Killer remains consistent. So here's the thing, Silent Hill F relies on asynchronous shader compilation alongside visibility skipping but it's initial pre-compilation misses some shaders needed during gameplay. The game [07:34] then compiles them in the background adding CPU load and causing these temporary frame rate drops. Once those shaders are compiled and cached, performance returns to normal matching the SCS Killer run. But as you see, with [07:48] performance penalty and reach the intended level of performance straight away. So let's move on to another interesting example where this tool shines. RoboCop: Rogue City is another Unreal Engine 5 [08:02] title but here the improvement can be far more dramatic even if SCS Killer doesn't solve everything. So, we start inside the police precinct, right? Loading into an existing save, and as we make our way upstairs, we're greeted [08:14] with an absolutely enormous hitch. The game effectively freezes for over 2 seconds, bringing gameplay to a standstill. Can't believe I'm seeing involve both shader compilation and asset streaming, although we can't [08:27] isolate the exact cause. Either way, it's an incredibly disruptive interruption. After using SCS killer, that lengthy freeze is gone. Now, that's smaller frame time issues. A spike a little over 33 milliseconds in [08:42] this instance. It's not ideal, but what remains looks more consistent with traversal-related stuttering as opposed to shader compilation. The downtown area makes that distinction clearer. The familiar traversal hitches are present [08:57] in both runs, and SCS killer does little to address them. But, the default run also suffers much larger spikes, including one exceeding 150 milliseconds, followed shortly afterwards by another approaching 700 [09:12] milliseconds. 7/10 of a second freezing there. Both absent from the SCS killer run, making these sections dramatically smoother. So, Robocop still exhibits traversal-related stuttering. There's nothing that SCS killer can do about [09:26] that, but several of the most disruptive frame time spikes are gone. It's a substantial improvement, even if the game isn't entirely stutter-free. Let's move on to our next game example, Sand Land, developed by Japanese studio [09:40] ILCA, and powered by Unreal Engine 4. And this gives us a different use case, a game that actually has no dedicated shader pre-compilation step at startup. This leaves us with some pretty severe stuttering during gameplay. Not great [09:55] actually rather convenient for testing SCS killer. Now, without [music] SCS killer, the problems begin almost immediately, the moment we first take control. Uh yeah, a massive frame time issue there. It exceeds 300 [10:09] milliseconds, almost a third of a second. Hardly the best first impression when playing this game. SCS killer eliminates that initial hitch, making for a much smoother introduction to the game, and it doesn't stop there. Even [10:21] something as simple as striking this boulder causes another noticeable hitch in our baseline run, which is also eliminated with SCS killer. >> As we enter combat, each new attack introduces different visual effects. [10:35] permutations or pipeline states that haven't yet been compiled, that work happens during gameplay instead. The result is a series of intrusive frame time issues. Some spikes exceeding 100 milliseconds as we use different attacks [10:50] for the first time. This is exactly where SCS killer shines. Compiling those pipelines ahead of time avoids much of the first use stuttering, resulting in considerably smoother combat as our comparison shows. Of course, the [11:04] severity of those hitches will vary with the CPU and the state of the shader cache, but Sand Land makes a strong case for handling that compilation before gameplay rather than as players encounter new effects. [11:18] Moving on, Final Fantasy Rebirth, one of the key titles that Blue Heisenberg actually developed this tool to address. This brings us back to a game with built-in shader pre-compilation, but the stuttering starts almost immediately. As [11:33] there's a noticeable hitch, and that's just the beginning. The opening alternates between pre-rendered cinematics and real-time cutscenes with some particularly intrusive frame time spikes whenever we transition back to [11:46] real-time rendering. Even camera cuts within those real-time sequences produce noticeable stuttering, uh repeatedly interrupting what should be a seamless cinematic presentation. With SCS killer, those interruptions are effectively [11:59] eliminated, and the cutscenes play out much more smoothly. Once we're in control, the stuttering continues, however. Simply moving from an interior to the outdoor environment produces a series of bothersome frame time issues, [12:11] interrupting gameplay as we move between areas. Intrusive stuttering we could well do without. Our first combat encounter is worse still with a pattern that's similar to Sand Land. Unlike that game [12:23] though, Final Fantasy VII Rebirth performs shader pre-compilation at startup, yet these first use hitches still slip through. their visual effects appear for the first time, the game appears to compile [12:37] previously unseen shader permutations or pipeline states on the fly, producing substantial frame time pauses. Stuttering during a cutscene is distracting enough, but here it happens in the middle of player controlled [12:50] actions, disrupting combat and making the game feel momentarily unresponsive. largely eliminates these first use hitches, letting both combat and the smoothly. Now, let's move on to another game we [13:05] were really interested to test out. Beast of Reincarnation though presents a rather different problem. As we highlighted in our original PC coverage, the game suffers from some alarming visual issues when loading with a cold [13:17] shader cache. Large parts of the environment take several seconds to appear with assets gradually popping into view accompanied by noticeable stuttering. The game doesn't perform a dedicated shader pre-compilation step at [13:30] startup, leaving players to encounter those issues during game play. And remarkably, even today, the situation remains unchanged in the PC version, which is kind of unacceptable. So, could SCS killer address those problems by [13:44] preparing the shaders before we even launch the game? And well, the answer is yes, and the difference is immediately apparent. The environment renders correctly from the moment we load in without those distracting delays as [13:57] Getting there though requires some patience. On a Ryzen 5 5600, SCS killer takes nearly an hour to complete the pre-compilation process, and slower processors will obviously take longer. The resulting shader cache also occupies [14:13] around 16 GB of disk space, which is worth bearing in mind. There's also the matter of system memory. On a 32 GB configuration, total RAM usage rose from a little over 18 GB without SCS killer to around 24 GB with it. [14:30] That's roughly 6 GB of additional RAM usage. Not necessarily a problem with this much memory available, but another consideration nonetheless. So, SCS killer does a good job of addressing those visual problems, but spending [14:43] nearly an hour preparing shaders just to have the environment render correctly on the first load is quite a lot to ask of players. And really, this is something the game itself should be handling properly. Let's move on now to Silent [14:56] Hill Townfall. And again, we're looking at a much more limited result. This recent Unreal Engine 5 title has recently received a couple of updates compilation stutter, frame pacing, and streaming issues. So, right out of the [15:10] box, it's an improvement over the highly compromised PC experience Konami put out at launch that I looked at on DF Direct. Even today, there are still noticeable hitches moving between areas. Initially, shader compilation seemed like the [15:24] culprit, but after pre-compiling with SCS killer, there's virtually the same gameplay. In fact, the SCS killer run actually exhibited more frequent smaller hitches in certain sections, although that could be incidental rather than [15:37] anything caused by the application. There is one noticeable exception, however. During this transition from gameplay into a cutscene, the default run suffers a substantial frame time spike in the region of around 300 [15:49] milliseconds. That's absent from the SCS killer comparison. >> So, while SCS killer appears to help in this instance, the overall improvement is modest. Most of the remaining hitches appear to be traversal or streaming [16:01] related, which shader pre-compilation alone won't resolve. And yeah, I mean, we had to test this one, right? Star Wars Jedi Survivor takes that limitation even further. Here, pre-compiling shaders makes surprisingly little [16:14] perspective, the PC version is still in a pretty rough shape when it comes to frame time consistency. We went in expecting substantial shader compilation stuttering, and sure enough, the initial run was riddled with nasty hitches. And [16:28] this gave us hope to expect that SCS killer might help. So, we cleared the shader cache using its built-in option and waited roughly 20 to 30 minutes for the pre-compilation to finish within the app. And the result, well, not quite [16:41] way through the opening section on Coruscant, there are the same stutters at almost exactly the same points as our baseline run. So, despite all of that pre-compilation, the gameplay experience is largely unchanged, and that's an [16:55] important distinction. The hitches persist in the same locations even after SCS killer has done its work. And this strongly suggests that we're dealing streaming-related stuttering rather than shader compilation. Jedi [17:10] Survivor demonstrates SCS killer's limits rather clearly. Even with all the shaders pre-compiled and ready to go, streaming and traversal-related stalls can still disrupt gameplay. So, let's finish up by taking a look at [17:23] The Last of Us Part 1, a welcome departure from the Unreal Engine titles we've been looking at thus far. This game became rather infamous for its lengthy shader compilation process alongside a host of technical problems [17:37] when it originally launched on PC. Now, returning to it today, the situation is considerably improved over the launch code. There's excellent frame time consistency throughout our tested gameplay with good hardware utilization, [17:51] compilation stuttering. It's a refreshing change given the game's troubled beginnings. While its upfront shader compilation can still demand some patience, the resulting gameplay is remarkably smooth in the areas tested [18:05] here, and that's ultimately what matters. Here, the game's own pre-compilation is successfully doing the heavy lifting, and the results speak So, this is an example of where the developer has gone back and made the [18:18] necessary fixes to deliver the required experience that should have been there at launch and that we're not seeing with other titles months or even years on from launch. So, a bunch of games tested then with fascinating results. So, [18:31] what's the verdict on SCS killer? Well, it's a genuinely impressive achievement for an independent developer and testing demonstrates just how effective shader pre-compilation can be even in games that already have their own [18:44] pre-compilation routines. It's also highlighting that developers really need to do a much better job in eliminating this issue. SCS killer though, it's not a universal solution and that's because [18:57] fundamentally not every stutter is caused by shader compilation and in some titles the time storage and memory requirements can introduce significant shows what's possible but players shouldn't have to rely on third-party [19:11] applications to enjoy a smooth experience from the very first launch. That responsibility ultimately lies with game developers and the wider PC Still, there are encouraging signs that the industry is moving in the right [19:24] direction. Microsoft's advanced shader delivery, for example, aims to address shader compilation at the platform level, supported hardware rather than leaving that work to the player or indeed the [19:37] developer. In fact, while we were producing this video, Nvidia released a new driver introducing support for advanced shader delivery. Although the select games and store [music] funds, the driver also changed how compiled [19:51] shaders are stored, temporarily breaking compatibility with SCS killer. Blue Heisenberg subsequently updated the application to accommodate those changes and we've since revisited our tests with the latest driver and SCS killer build. [20:07] But, the results remain largely consistent with original findings. addressed the fact that SCS killer is targeting shader compilation stutter, but there are other issues prevalent within PC games and traversal stutter is [20:23] foremost amongst them. Dead Space is particularly notorious for this and we'd kind of written the game off completely as there was no evidence that the developer would ever go back to fix the issues. Simply moving through doorways [20:35] or between different sections of the Ishimura can trigger substantial frame time spikes causing sudden jarring interruptions to gameplay. It's these hitches occur repeatedly throughout the game ruining the PC [20:49] experience. Fortunately a new mod the Ishimura patch developed by Luke Man 3000 aims to tackle these persistent traversal issues. It does this primarily by changing how the Frostbite engine handles GPU memory allocation preparing [21:04] larger blocks of memory in advance rather than making numerous smaller allocations during gameplay reducing the associated overhead and stores and got to say the improvement is genuinely remarkable. With the patch areas that [21:18] previously suffered from severe frame time issues are now considerably smoother with many of those hitches dramatically reduced or eliminated altogether. So take this particular comparison for example and the frame [21:30] time spike of close to 120 milliseconds in the unmodified game drops to under 25 milliseconds with the patch installed and that's just one example of a much broader improvement. The reduction in traversal stuttering throughout the [21:45] areas tested is genuinely transformative making Dead Space Remake a considerably smoother and more enjoyable experience now. So previously we were not optimistic about issues like this ever being resolved but the landscape is [22:00] shifting and now the impossible does seem eminently possible. one. As ever a big thanks to Ryan for tackling the core testing for this video and the editing for that matter and with all of that out of the way it's time to [22:15] sign off. So like subscribe share etc. Bells and whatnot but really yeah the F patreon.com/digitalfoundry enables a lot of what we do and we'd be check that out. But, in the meantime, thanks for watching and supporting [22:31] thanks for watching and supporting Digital Foundry.