Deadlock Stuttering & Lag Fix: Stop FPS Drops and Freezes
By Tier1Settings Updated Published
On this page
If Deadlock feels laggy, first find out which kind of lag it is: a flat frame-time graph with rubber-banding means your connection, while a spiking graph means PC stutter — most often the Vulkan renderer freezing when big ultimates fire (switch to DirectX 11), shaders rebuilding after a patch, or a CPU bottleneck late in the match. Deadlock’s mix of MOBA-scale team fights and shooter mechanics makes either kind doubly punishing, because it breaks both your aim and your ability timing. The fixes below run in the order most likely to help.
| What you see | Likely cause | Fix |
|---|---|---|
| Enemies rubber-band, hits land late, FPS counter steady | Network lag (packet loss / ping) | Section 1 |
| Freezes when ultimates or big effects go off | Vulkan renderer | Section 3 |
| Hitching in the first match after an update | Shaders rebuilding | Section 4 |
| FPS sinks in late-game team fights | CPU bottleneck | Section 5 |
Six-hero fights are the stress test. Tune for the team fight, not the lane phase.
1. Separate stutter from network lag
Deadlock is fast enough that packet loss feels like frame drops:
- Put up a frame-time overlay.
- If the frame-time graph stays flat while gameplay rubber-bands, it’s your connection — go to the high ping and packet loss guide.
- If the graph spikes, continue below.
2. Cut effects load
In Deadlock’s video settings, the effects-heavy options are the fight-time killers:
| Setting | Recommended value |
|---|---|
| Display Mode | Fullscreen |
| V-Sync | Off |
| Frame Rate Limit | Stable cap below refresh |
| Shadows | Low |
| Effects / Particle Quality | Low |
| Ambient Occlusion | Off |
| Texture Quality | As VRAM allows |
The label set evolves while the game is in active development — keep the principle: anything that scales with number of abilities on screen goes down first. Full build advice lives in the best Deadlock settings guide.
3. Switch to DirectX 11 if ultimates freeze the game
Deadlock runs on DirectX 11 or an experimental Vulkan renderer. On Valve’s Deadlock forum, players on very different PCs (an RTX 3080 desktop and a GTX 1650 laptop) reported Vulkan freezing for a second or more whenever a big ultimate or effect came on screen, even after the game’s shader pre-compilation step. Switching to DirectX 11 removed the freezes. A later patch fixed it for some of them, so it’s worth testing both on the current build.
- In Deadlock’s video settings, change the render setting from Vulkan to DirectX 11 and restart the game.
- Or right-click Deadlock in Steam → Properties → General → Launch Options and type
-dx11to force DirectX 11 on every launch.
The trade-off players report on DirectX 11 is more shader compiling at launch and when leaving a map, so loads are slower. Fullscreen alt-tabbing is also worse. If Vulkan crashes rather than stutters, the Deadlock crashing fix covers the boot.vcfg edit.
4. Handle shader stutter after patches
Deadlock patches frequently, and each patch can invalidate shaders:
- Play one casual match after a patch before judging performance.
- Still hitching? Clear the shader cache and let it rebuild.
- Pair it with a DDU clean driver install if stutter started after a driver update.
5. Free the CPU
Late-game Deadlock is CPU-bound on most systems:
- Enable XMP/EXPO — faster memory directly lifts worst-case frame times.
- Close launchers, browsers and overlays; disable Game Bar/DVR.
- Set the high performance power plan so cores stay clocked between fights.
- Check VBS if you’ve never reviewed it.
6. Stabilize pacing
- Cap FPS at what you hold in a 6v6 fight — capping guide.
- Run Tier1Suite for higher Windows timer resolution; ability-timing games benefit noticeably from consistent frame delivery.
Related guides
Frequently asked questions
Why is my Deadlock so laggy?
Deadlock 'lag' is one of two problems. If a frame-time overlay stays flat while enemies rubber-band or abilities land late, it's network lag (packet loss or high ping). If the frame-time graph spikes, it's PC stutter: most often the Vulkan renderer freezing when big ultimates fire, shaders rebuilding after a patch, or a CPU bottleneck late in the match. Players on Valve's Deadlock forum report the Vulkan freezes stop on DirectX 11.
Should I use Vulkan or DirectX 11 in Deadlock?
If Deadlock freezes or hitches when large effects or ultimates appear, try DirectX 11. Players on Valve's Deadlock forum report it removes those freezes, at the cost of more shader compiling at launch and on map changes. If Vulkan runs smoothly on your PC, there's no need to switch.
Why does Deadlock stutter in team fights?
Six heroes' abilities firing at once spikes both CPU and effects load. Lowering effects-related settings and stabilizing your frame cap below the worst-case FPS removes most of it.
Does Deadlock have shader compilation stutter?
Like most Source 2 titles it compiles some shaders on first run after updates. The first match after a patch can hitch; it settles, and a shader cache clear helps if it does not.
Why does my FPS drop near the end of Deadlock matches?
Late-game item builds multiply projectiles and effects, raising CPU load. If GPU usage drops as FPS drops, you are CPU-bound — memory speed and background-process cleanup help most.
Is Deadlock stutter sometimes network lag instead?
Yes. Rubber-banding and hit delays look like stutter but are packet loss. Check with a frame-time overlay: flat graph plus choppy gameplay means the network, not the PC.