Published Nov 20, 2026, 5:30 PM EST Sydney Butler is a technology writer with over 20 years of experience as a freelance PC technician and system builder and over a decade as a professional writer. He's worked for more than a decade in user education. On How-To Geek, he writes commerce content, guides, opinions, and specializes in editing hardware and cutting edge technology articles. Sydney started working as a freelance computer technician around the age of 13, before which he was in charge of running the computer center for his school. (He also ran LAN gaming tournaments when the teachers weren't looking!) His interests include VR, PC, Mac, gaming, 3D printing, consumer electronics, the web, and privacy. He holds a Master of Arts degree in Research Psychology with a minor in media and technology studies. His masters dissertation examined the potential for social media to spread misinformation. Outside of How-To Geek, he hosted the Online Tech Tips YouTube Channel, and wrote for Online Tech Tips, Switching to Mac, and Helpdesk Geek. Sydney also wrote for Expert Reviews UK. He also has bylines at 9to5Mac, 9to5Google, 9to5Toys, Tom's Hardware, MakeTechEasier, and Laptop Mag. You've probably noticed when playing the PC versions of the latest games that, no matter how powerful your computer is, there's a good chance you'll encounter hitches and stutter when playing games that are perfectly smooth on consoles. This is all thanks to something called the "shader compilation stutter." This can happen when a game needs a shader or graphics pipeline that hasn't been compiled or created for your system; creating it during gameplay can cause a hitch, though the size and duration vary by game. The big questions are why this is happening, and what can be done about that? Your graphics driver used to get away with it Hiding in plain sight Credit: NVIDIA A "shader" is actually a small program that runs on your GPU. It has a specific job, like making metal look shiny or making water look wet. Game developers program the shaders they need or, more likely, use the ones that come with the engine they're using. These days, that's probably going to be Unreal Engine 5. Either way, the shaders that ship with a game are in an intermediate format. A universal shader language. The instructions inside the shader need to be mapped to the hardware that's actually in your PC. Since there are so many different generations and models of GPUs, the developer can't pre-compile shaders for every model out there. The game would balloon to impossible sizes. So instead, shaders are compiled on your computer. You only have to store the shaders your computer actually needs, and your computer gets optimized code for its hardware. Now, complaints about shader compilation stutter have largely coincided with DirectX 12. However, shader compilation isn't new. Shader compilation as we know it today, using HLSL (High-Level Shader Language), has been around since Shader Model 2.0 in DirectX 9. The big difference is that Direct3D 12 makes the game responsible for creating and managing pipeline state objects (PSOs), which combine shaders with other rendering states. The graphics driver still compiles shader code for the hardware, but PSOs can take time to create, and a game that creates them during play can hitch. Earlier Direct3D drivers often handled more of this work behind the scenes, sometimes on background threads, but shader-related stutter was still there to some degree. DirectX 12 gave games a chance to see the hitch coming But just because you see the iceberg doesn't mean you can avoid it Credit: FromSoftware The obvious solution to this problem is to just compile all the shaders ahead of time, right? You've probably seen games with a screen that says "compiling shaders" that has to complete before you get to play. The thing is, this only minimizes shader stutter. Both Direct3D 12 and Vulkan let you preview which shaders will be needed ahead of time; the engine can tell the API what shader combos will be used in the next level and ask it to compile them while the loading screen is up. But there are so many combinations, and games are dynamic systems where unforeseen things can happen. This is when you get those on-the-fly compilation hitches. You started paying for the work in loading screens or lost frames It's a bumpy ride for everyone on PC The short version is that Direct3D 12 puts more responsibility on game engines and developers to create and manage pipeline state objects at the right time, and some games have handled that process poorly. In turn, this now means you as the player have to deal with a bad experience as a result. Meanwhile, console gamers with much lower-spec hardware have a stutter-free gaming experience because the GPU target is known and all the shaders ship with the game properly compiled. It feels bad because it's not just a few skipped frames or a drop in frame rate while the CPU and GPU work on compilation. It's a brief all-stop of the game while it waits for the process to complete. They're trying to fix it Since the onus is now on the game engine to manage shader compilation, engine makers have been trying to improve the situation. Unreal Engine 5 has received several updates that overhaul how shader compilation works and automate it to a greater degree, so a developer's experience with the technology doesn't play such a major role. SteamOS on the Steam Deck and other officially supported handheld PCs also effectively addressed the shader stutter issue by automatically including the shaders for these known GPUs. That trick has now been shared with Steam users more broadly, as Valve crowdsources shaders and shares them among players with the same GPUs and configs. This is already helping reduce stutter in games played via Steam. In the meantime, driver vendors are also working to reduce shader-related delays: Nvidia, for example, has introduced a feature that rebuilds DirectX 12 game shader caches in the background after driver updates. Recently, a third-party tool called SCS Killer has tackled the issue head-on, with great results. So, while the stuttering nightmare isn't over, there's light at the end of the tunnel. Which, ironically, probably triggered a hitch the first time we saw it.
This is how shader compilation stutter became your problem
Full Article
Original Source
Read the full article at Howtogeek →KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.