Today we're checking out a new application that's been getting a lot of attention recently called Shader Compilation Stutter Killer, or SCS Killer for short. As the name suggests, this application is designed to combat PC shader compilation stutters, an issue that has plagued gamers for many years now. So, we're going to find out if it actually works. And along the way, I did discover something very interesting in relation to Radeon GPUs, something that's kind of a big deal, I feel, and I'd not heard about it before, so maybe it'll be news to you as well. And you know what else might be news to you. Today's video is brought to you by Sapphire and their Pulse range of GPUs and motherboards. If you're a value-conscious builder looking for a great 1440p gaming experience in a compact system, this is the range for you. The Sapphire Pulse B850M Wi-Fi motherboard supports the latest Ryzen processors, PCIe 5.0, onboard Wi-Fi, and Bluetooth. The matching two-and-a-half slot Sapphire Pulse Radeon RX 9070 GRE 12 GB graphics card features Sapphire's Dual-X cooling, a dual-fan compact cooler. It's perfect for smaller builds while still offering excellent performance and value. Despite its small size, the card runs very cool and quiet, which is important for more compact builds. Sapphire's value-oriented pairing is a great option for those looking at a mid-range gaming experience. So, for more information, please check the links in the video description.
Okay, so before we get into it, SCS Killer is a free, open-source application. So if you're interested, I recommend just heading over to scskiller.com, downloading it, and giving it a shot for yourself. Now, if you're unaware what shader compilation stutter is, in the simplest of explanations, it's a common issue in modern PC gaming where the game freezes briefly the first time a new visual effect appears. Now, some games try to tackle this issue by pre-compiling shaders before loading into a game. The Last of Us Part One, for example, has a famously long wait time for pre-compiling shaders. Unfortunately, despite pre-compiling shaders, some games still have horrific shader compilation stutter, and some games don't even pre-compile anything, and that can also lead to a poor experience.
So rather than relying on the game to compile the shaders, either preloading or on the fly, SCS Killer intercepts and pre-compiles them locally before you even launch the game. The application scans the game's files, extracts the necessary shader code, and forcefully recompiles as many shaders as it can into the pipeline state objects directly into your GPU driver's cache. The goal here being that because the shaders are already compiled when you launch the game, the GPU driver doesn't have to pause gameplay to process new visual effects. And I should note that SCS Killer doesn't rely on a whitelist of specific games. Rather, it works at the engine level. It can detect games built on Unreal Engine 4, 5, Unity, RE Engine, and FromSoftware's engines, alongside a generic reader for other DirectX 12 games. Games where the shader pipeline can't be easily extracted from the game files, SCS Killer includes an optional recorder. This allows you to play the game for a few minutes with the recorder on, and the tool uses that data to compile the necessary shaders afterwards.
Now, it is important to note that this application doesn't solve all stuttering in games, because not all stutters that you'll be seeing are shader compilation related stutters. One of the biggest issues, especially for Unreal Engine 5 games, has been traversal stutter, and SCS Killer can't address that. Traversal stuttering is generally more game-breaking in my opinion, as it results in longer pauses as new environmental assets are loaded in from the local storage, and this happens when you cross like an invisible map boundary or something like that. Perhaps we can get a shader traversal stutter killer or STS Killer in the future. Fingers crossed. Now, I should note that there are some drawbacks of the SCS Killer app, though they are really just a necessary evil. For example, brute forcing every shader takes quite a bit of time, though how much time will depend on how many shaders need to be cached and how fast your CPU is. Of course, the advantage here being that you can compile shaders while not using your PC, but it will pin your CPU usage at 100% for extended periods of time, but providing you set up right, that won't be an issue. It does however eat into your storage, and with SSDs at a premium right now that is something to consider, and this is because compiling thousands of shaders inflates the size of your GPU driver's shader cache. As a result you will need to manually increase the size of the shader cache. Though only Nvidia users can currently do this. The standard Nvidia cap is 10 GB, but you can make that 100 GB if you'd like, or even unlimited, and this prevents older shaders from being deleted to make room for new ones.
However, if you have a Radeon GPU, the usefulness of SCS Killer is extremely limited. Though AMD themselves appear to have a fix for this, which I am going to explore in this video. As it stands though, AMD's driver has a fixed shader cache of 16 GB, at least according to SCS Killer. I'm yet to confirm this with AMD, but according to SCS Killer, this is indeed the case. And so, it means you can't increase it. And that means once you exceed 16 GB, the driver removes the shader cache for the least recently played games. And SCS Killer will show those games as needing to be recompiled. This is a problem as it means Radeon users can really only optimize a few games at a time with SCS Killer. All of that said though, no need to panic cuz I have discovered some pretty damn interesting shader compilation behavior on Radeon GPUs, and we'll get to that shortly. Now, for all of this testing, I have stuck with our Ryzen 7 9800X3D test system, but depending on interest, I can do more testing in the future with slower CPUs. And I'm sure that is something many of you will want to see. But for now, we'll go over what I have. And initially, I should be clear, the goal of this content was simply to see if the SCS Killer application actually worked. And I was able to clearly demonstrate this with the 9800X3D. So, let's get into the results.
And we'll start with Star Wars Jedi Survivor, a game famous for its many stutters. This game does pre-compile shaders when loading for the first time. And in this example, this was the first time each configuration had played the game right after the initial pre-compiling shaders. And there's quite a few interesting things to note here. Firstly, performance is obviously much better for the SCS Killer configuration, boosting the average frame rate performance by 25% with a similar improvement to the 1% lows. However, you might have also noticed that the standard configuration is consuming around 60% more power from the GPU, at least at the start of this test. That figure does drop down to just under 40% by the end of our test. And this is because despite pre-compiling the shaders when we first load into the game, there is still quite a lot of shader building going on while we play, especially for the initial gameplay. This reduces FPS performance and increases load on the GPU. Something else you might notice is that SCS Killer is loading more data into the system memory or RAM. We're looking at around 7% more usage in this example, and that's a result of those additional pre-compiled shaders, which have been buffered into the system memory.
Now, for a second Star Wars Jedi Survivor test, I loaded into an earlier section of the game right after the first playthrough that you just saw. So, the game has been open for quite a while at this point. In terms of performance, the SCS Killer configuration was around 14% faster, though neither configuration suffered from what I would call shader compilation stutter. SCS Killer was loading around 30% more data into system memory, almost 7 GB more data, which wasn't a problem for our 32 GB configuration, but it is something to be mindful of if you have less than 32 GB of RAM. Now, the GPU power did increase with SCS Killer this time as we're driving more frames. So, that makes sense. And it would seem that the RTX 5090 is doing less shader compilation work on the fly. So, although SCS Killer isn't solving shader compilation stutter in this specific example, as the standard configuration didn't suffer from any stuttering, it still managed to boost performance by loading more pre-compiled data into the system memory for faster access. It's possible if we were to use slower hardware, we would have seen stuttering here for the standard configuration, but again, that is something I'll have to explore in future content. It's also worth noting that despite loading more shader data into the system memory, SCS Killer didn't always improve FPS performance. As we see in this cutscene example, and as I noted at the start of the video, it doesn't fix traversal stutter, which is what we're seeing here. We're also seeing it here and here.
Another game that apparently has a lot of shader compilation stutter is Grounded 2. So, I decided to get that and take a look. However, with the hardware configuration that I'm testing with, I didn't really see any stuttering issues, at least in the sections of the game that I tested. Despite loading 5 to 6 GB worth of additional data into the system memory using SCS Killer, I didn't see any improvements in performance.
A game that I was really keen to try, and the developer of SCS Killer notes on their website that it does improve performance here, is Hogwarts Legacy. Unfortunately though, I wasn't able to record any improvements in my testing using the ultra quality preset at 4K with performance upscaling and ray tracing enabled. Performance was still pretty poor after running SCS Killer, especially the 1% lows, and I didn't really see any improvements to the frame times. What we did see was over a 20% increase in system memory usage, basically maxing out our 32 GB capacity. So worried that we might have been maxing out the system memory and therefore SCS Killer wasn't able to improve performance, I decided to retest without ray tracing enabled as this will reduce memory usage, but it didn't really change anything. Performance was much the same for both configurations. If anything, the standard configuration was slightly better. And now SCS Killer was consuming over 50% more system memory for no advantage. Frame pacing was also much the same for both configurations.
So in a final effort to reduce system memory usage, I resorted to the medium quality settings again with ray tracing disabled. But again, frame rates and frame pacing was much the same between the two configurations. In this example, SCS Killer consumed around 25% more system memory for no real advantage. So, either it's the hardware configuration that I'm currently testing, though SCS Killer did note improvements in Hogwarts Legacy using an RTX 5090, or maybe it's just the section of the game I'm testing. I'm not sure.
The Blood of Dawnwalker is another game that I've heard suffers from shader compilation stutter. Though, in my testing, it didn't seem too problematic. That said, by loading more compiled shader data into the system memory, we did see a reasonable performance improvement with SCS Killer. By the end of our test, 1% lows were improved by 15%, with a 6% increase to the average frame rate, which is pretty great given it is free performance, assuming you have enough storage space and system memory available. In this example, system memory usage did increase by 33% as SCS Killer loaded around 5 GB of additional data into the RAM.
Another new game I decided to check out was Silent Hill Townfall, but in this example, performance was much the same. SCS Killer wasn't able to solve any of the stuttering in this game. And in fact, we saw more stuttering with SCS Killer, though this is just a single pass, which is a drawback of this side-by-side testing. So, keep that in mind.
Now, a game that I know stutters like absolute buggery is Tiny Tina's Wonderlands, an Unreal Engine 4 game, which has so much shader compilation stutter, it's almost unplayable at times. For those of you who haven't played this game, here is some full screen action just to give you an idea of what we're talking about. And keep in mind, I'm using a 9800X3D and an RTX 5090 here. The average frame rate certainly looks pretty great, but look at those 1% lows. It's absolutely horrid. The game does recompile shaders before you play, and while things do improve the more you play, as soon as you move to a new area, it's Stutter City all over again. For example, I left the initial test area for a few minutes and then returned. And as you can see, although I haven't moved very far within the world, it doesn't take long before those shader compilation stutters return. Admittedly, they're not as bad, but still pretty annoying, and especially given the hardware configuration that we're using. But this is where SCS Killer comes in clutch. It takes Tiny Tina's Wonderlands from a stuttery mess to a perfect experience with no stuttering at all. By the end of our test, 1% lows were boosted from 45 fps to 147 fps. But more crucially, the constant hitching and stuttering is now gone.
So, having seen how well SCS Killer worked for the RTX 5090 in Tiny Tina's Wonderlands, I decided to install the Radeon RX 9070 XT. And I'm glad I did because the results were very puzzling, but in a good way. What we're looking at here is the first few seconds of gameplay after freshly installing the 9070 XT along with the latest display driver. SCS Killer hasn't been used here. We're simply using the game's pre-compiled shaders. And then I loaded my save game file. Yet, despite that, given what we saw with the 5090, the game ran perfectly fine with no stuttering at all. I couldn't quite believe what I was seeing, again having just finished testing the GeForce RTX 5090, which was a complete mess. So, I continued to play, walked around to a few new areas, but at no point did the game stutter at all. This left me very confused and looking for answers.
And that's when I came across this extremely brief article on the AMD website titled AMD Software Adrenalin Edition 26.9.2 background shader compilation. And this is the driver that we were using for our testing. And the post is so short that I'll just read it all out. What is happening? AMD Software Adrenalin Edition expands DirectX 12 background processing to Unreal Engine 5 titles. It is already enabled for Unreal Engine 4 titles, plus Borderlands 3, Dirt 5, Cyberpunk 2077, Guardians of the Galaxy, Halo Infinite, and Tiny Tina's Wonderlands. Impact. Background shader compilation reduces initial game load times. Reduced performance may be observed in affected titles until compilation has completed. Shader compilation is a CPU-heavy process and completion time may vary depending on CPU performance and system load. Workaround. AMD recommends allowing approximately 15 minutes of gameplay for background shader compilation to complete prior to capturing performance measurements. When using an in-game benchmark, the first run of each new session should be excluded from results.
So, based on that, AMD seem to be suggesting that they've been supporting background shader compilation for Unreal Engine 4 titles for some time now. Though this post is rather confusing as they said plus titles such as Borderlands 3 and Tiny Tina's Wonderlands, which is an Unreal... well, they're both Unreal Engine 4 games, so I don't know why they mentioned them in addition to supporting Unreal Engine 4 games. It's a bit confusing. It of course makes sense to mention games like Dirt 5, Cyberpunk 2077, Guardians of the Galaxy, and Halo Infinite sort of individually because they're not Unreal Engine 4 games. So supporting those games in addition to Unreal Engine 4 games, as I said, makes sense to note that. Anyway, this was all news for both myself and Tim. We didn't know that AMD was offering DirectX 12 background processing for all Unreal Engine 5 titles with their latest driver. How I didn't even know it was working previously with Unreal Engine 4 games. Admittedly, shader compilation performance isn't something that we've looked at in quite some time as nothing really seemed to be happening there. It was just an issue that we'd accepted to live with for now. But as we've just seen, and I'm discovering for the first time, in games like Tiny Tina's Wonderlands, AMD appears to have completely solved shader compilation stutter. And for us, it's happening almost instantaneously, at least in that example. Just a quick pre-shader compilation before loading into the game, and then we start playing the game without any stutters. Whereas it is still a complete mess with all GeForce GPUs.
Despite working perfectly fine, I wanted to use SCS Killer. And this is when I learned that AMD GPUs have a 16 GB fixed shader cache buffer size. Anyway, having pre-compiled the Tiny Tina's Wonderlands shaders using SCS Killer, I ran the game again and found pretty much the exact same performance. SCS Killer did increase RAM usage by around 2 GB, but this in no way improved performance.
Now, for comparison, here is how the GeForce RTX 5070 performed under the exact same test conditions, looking at both the default driver behavior and SCS Killer. As you can see, SCS Killer completely solves shader compilation stutter for the GeForce GPU and increases VRAM usage by around 4 GB to roughly the same usage we're seeing with the 9070 XT. Here's a side-by-side comparison between the 9070 XT and RTX 5070. Looking at stock driver behavior, as you can see, despite similar average frame rate performance, the 1% and 0.1% lows of the Radeon GPU are significantly better. And this is because AMD's background shader compilation method is working a treat.
Now, here is how the stock 9070 XT compares to the RTX 5070 with the GeForce GPU using SCS Killer's pre-compiled shaders. Both GPUs are now delivering smooth performance at roughly the same frame rates, though overall the RTX 5070 is now ever so slightly faster. But what's crazy about this is that we're looking at no noticeable pre-shader time for the 9070 XT. I literally installed the driver, reset the system, loaded into Windows, and then immediately loaded Tiny Tina's Wonderlands, at which point the game quickly preloaded shaders, and then I was gaming without an issue. For the same kind of performance, the RTX 5070 required me to install SCS Killer, then spend about 30 minutes pre-compiling shaders before the performance you're seeing here was even possible. So AMD's driver implementation is doing all of this very quickly. It appears to be far more efficient. Very impressive stuff.
Interestingly though, AMD's own article recommended allowing approximately 15 minutes of gameplay for background shader compilation to complete prior to capturing performance measurements. But for us, where we were testing within the game and the hardware configuration that we were running, waiting 15 minutes was not required in Tiny Tina's Wonderlands. It just seemed to work straight away.
Now, just lastly, I wanted to compare the RTX 5070 and 9070 XT in Final Fantasy VII Rebirth. As I've heard, this game is a shader compilation stutterfest. And I've heard correctly. Here is the 9070 XT comparing the standard driver configuration to SCS Killer, and neither of them are flawless. I should also note the game is hard capped at 120 FPS, which is a bit annoying for testing, but it's really the 1% and 0.1% lows that we want to focus on anyway, at least for this testing. The AMD driver manages to keep 1% lows over 60 fps, but we're still seeing stutters which are reflected in the 0.1% lows. And while SCS Killer certainly helped, it didn't fully kill the stutter issues in this particular title.
Although the 9070 XT performance wasn't perfect, it was considerably better than that of the RTX 5070. In fact, the situation here is very similar to the one we saw in Tiny Tina's Wonderlands. So, that is to say, it's a stuttery mess in Final Fantasy VII Rebirth with the GeForce GPU. Whereas the Radeon GPU kept 1% lows above 60fps, the 5070 was essentially broken, dropping down to single digits. In this example, the average frame rates are very similar, but the 1% and 0.1% lows of the RTX 5070 are terrible.
Here's how the RTX 5070 performs after recompiling shaders using SCS Killer. The performance issues are basically solved entirely now and the jarring stutters are gone. 1% lows remained well over 60 fps throughout our testing and even 0.1% lows were very good. Excellent frame pacing overall and a completely transformed gaming experience. I captured a few minutes of gameplay here, but I played for even longer and I saw no issues. Using SCS Killer for both the 9070 XT and RTX 5070 provides pretty similar results between the two GPUs. Of course, we are frame capped, but when focusing on the 1% and 0.1% low data, we find that both GPUs are quite similar in this title. SCS Killer does use more RAM with the RTX 5070, and this is possibly due to the on-disk cache capacity limitations of the Radeon GPU.
Well, SCS Killer certainly has taken me down a rabbit hole that I didn't expect, and at some point, I'm going to have to do a lot more testing comparing Radeon and GeForce GPUs using a range of hardware configurations, and of course, games. For now though, we can conclude that SCS Killer looks to be a useful tool that can indeed improve performance in games with shader compilation stutters. Just be aware that building shaders can take quite a lot of time. You may need to do it frequently, and it can use a lot of local storage space, more so for GeForce GPUs as you can set unlimited size there, but it does eat up your RAM as well, which may or may not be a problem for you. The good news is there's really no risk in giving it a go. It's a free application, so even if you are playing a game that does suffer from shader related stutters, it's well worth trying out. It's very quick and easy to download and just as easy to use. It was impressive to see how dramatically it improved performance for games such as Final Fantasy VII Rebirth and Tiny Tina's Wonderlands, at least for the GeForce GPUs. Radeon GPUs, on the other hand, are a bit of a different story, and there appears to be good news here for Radeon owners. At first, it did seem like a bit of a Radeon fail that you can't increase the on-disk shader cache size. And while I would like to see that changed, if AMD keeps improving how the driver works, it may not be necessary.
And I did speak to AMD about this, and they said that while they appreciate third-party applications such as SCS Killer, AMD also leads the industry in support for DirectX 12 advanced shader delivery, which aims to solve the same problems as SCS Killer in a supported way. Still, SCS Killer did help the 9070 XT in Final Fantasy VII Rebirth, but it was completely useless, or rather unnecessary, for Tiny Tina's Wonderlands, as AMD's driver appears to have solved shader compilation stutter in that title. Or at least I can confirm that it completely solved it for the section of the game that we looked at. And I have to say, I'm honestly not sure if this is news or not. Is it known that Radeon GPUs work flawlessly now in a game such as Tiny Tina's Wonderlands, while GeForce is often still a stuttery mess? Like I said, it was news to us, so I have to admit that. But then, I haven't been looking at this that closely, and I haven't tested Tiny Tina's Wonderlands in a hot minute. But also, AMD has officially stated that this is a thing that they've fixed, and yet, we didn't know about it. As in, we didn't learn about it directly from AMD, and I've not heard or seen anyone else testing this. I should also note that AMD didn't even put this news in their regular driver notes, which is why we missed it. Rather, they created a separate page that we just happened to stumble upon when trying to work out why the 9070 XT was working so well in Tiny Tina's Wonderlands. Pretty strange stuff, but this is how AMD tends to roll. If Nvidia had solved a serious shader compilation stutter issue in a number of games, we would have almost certainly seen a big announcement about this. Probably some kind of branding as well. Anyway, as I said, AMD stuff pretty interesting.
But yeah, I'm keen to do more digging into this to see, you know, how it affects other games and other hardware configurations as I've said. But yeah, for this video, that is going to do it. If you're interested in SCS Killer, I'll put a link in the video description, but you can just go to scskiller.com and download it there as well. It's pretty straightforward. If you like the video, you know what to do. If you want to support the channel more directly, you have the join button or Patreon. Sign up to either one of those things will give you access to our exclusive Discord server, monthly live streams, Q&A stuff, and behind the scenes content. So, check that out if you're interested. If not, that is perfectly fine. And of course, I would like to thank you for watching this video. I'm your host, Steve. See you again next time.