{"id":8067,"date":"2026-10-13T14:02:16","date_gmt":"2026-10-13T12:02:16","guid":{"rendered":"https:\/\/ultimatemove.eu\/?p=8067"},"modified":"2026-10-21T00:17:48","modified_gmt":"2026-10-20T22:17:48","slug":"deadlock-optimization","status":"publish","type":"post","link":"https:\/\/ultimatemove.eu\/en\/deadlock-optimization\/","title":{"rendered":"Deadlock optimization: six steps to more FPS in fights"},"content":{"rendered":"

Deadlock optimization comes down to six steps in a fixed order: measure, in-game settings, launch options, config, Windows, and finally CPU, memory and BIOS. After each step you check FPS in the same scene and keep only what added frames.<\/p>\n

I have been tuning gaming PCs for over 15 years. Deadlock players usually copy a list of tweaks from a video, apply ten at once, and never learn which one helped and which one hurt. Each step below has a short instruction and a link to the guide that covers it in full.<\/p>\n

1. Measure FPS before you change anything<\/h2>\n

Open the console with F7 and type cl_showfps 2<\/code>. Valve describes this value as a smoothed FPS counter, so it does not jump around in a fight like the plain one.<\/p>\n

A live match is useless for comparisons because no two look alike. Download a replay of your match from the history in your profile and watch the same big teamfight before and after a change. The quickest way to find the minute of the fight is the kill map in our free Deadlock Replay Analyzer<\/a>.<\/p>\n

For exact numbers, record those 60 seconds in the free CapFrameX. It calculates the average FPS and the 1% low, the frames from the heaviest moments of the fight. Do three runs and compare the middle one.<\/p>\n

2. In-game graphics settings<\/h2>\n

Among the settings, lower shadows and effects usually give the most frames. Turn VSync off and cap FPS at your monitor's refresh rate or slightly below.<\/p>\n

Stay on DirectX 11. Most players use it, and in my tests Vulkan very rarely does better in Deadlock, especially on GeForce cards. If you have a Radeon, test Vulkan on the same replay and keep it only if it gives a higher 1% low.<\/p>\n

Every slider with an explanation is in the best Deadlock settings for 2026<\/a>.<\/p>\n

Deadlock optimization on a low-end PC or laptop<\/h3>\n

On weak hardware, lower the render resolution with FSR scaling and set textures to low if the GPU has little memory. Plug the laptop into the charger and check in Windows graphics settings that Deadlock runs on the dedicated GPU, not the integrated one.<\/p>\n

3. Launch options<\/h2>\n

In Steam, right-click Deadlock, choose Properties and enter launch options. Add only what you have tested, for example -vulkan<\/code>if Vulkan won on your Radeon in step 2. Skip the long strings from videos, because many options from the Source 1 days do nothing in Source 2. The options that work are listed in the best Deadlock settings<\/a>.<\/p>\n

4. Deadlock config<\/h2>\n

Config podmienia plik gameinfo.gi i schodzi z grafik\u0105 poni\u017cej minimum z menu. Od aktualizacji City Never Sleeps silnik ignoruje 77 zmiennych z tego pliku, wi\u0119c cz\u0119\u015b\u0107 linii w starszych configach nic nie robi, a ka\u017cda du\u017ca aktualizacja nadpisuje plik. Dlaczego sam config ju\u017c nie wystarcza, wyja\u015bniam w tek\u015bcie jak zwi\u0119kszy\u0107 FPS w Deadlock, gdy config nie dzia\u0142a<\/a>.<\/p>\n

That is why we maintain our own Deadlock Ranked CFG<\/a> and update it after every patch. The install steps are on the same page.<\/p>\n

5. Windows<\/h2>\n

Windows out of the box is not set up for games. Check the power plan, the apps that start with the system, and overlays. A single overlay rarely hurts the result, but if you run several, turn off the ones you do not use and measure the difference.<\/p>\n

Microsoft itself says Memory Integrity can lower gaming performance. I covered its cost in the article on Memory Integrity and FPS loss<\/a>, and five safe post-patch steps are in the article on Deadlock FPS drops after the update<\/a>.<\/p>\n

6. CPU, memory and BIOS<\/h2>\n

Deadlock spreads its work across the CPU's physical cores. Below is my measurement from a match on a Ryzen 7 9800X3D: every other graph in Task Manager runs hard, one for each of the eight cores, while the second threads of those cores barely move. The game prefers physical cores to SMT threads, so when you pick a CPU, count cores, not threads.<\/p>\n

\"Deadlock<\/figure>\n

When the GPU clearly stays below full load in a fight and FPS drops, the CPU, memory or system is holding you back. What matters then is memory speed and timings, an enabled XMP or EXPO profile, and a CPU that does not throttle from heat. These are BIOS settings, and a mistake there costs stability, so check every change with a stability test, not just FPS.<\/p>\n

What the measurement shows and where to look<\/h2>\n

Keep Task Manager open on the Performance tab while the replay runs.<\/p>\n\n\n\n\n\n\n\n\n\n
What you see<\/th>\nMost common cause<\/th>\nWhere next<\/th>\n<\/tr>\n<\/thead>\n
GPU near 100%, low FPS across the whole replay<\/td>\nSettings or resolution too high<\/td>\nStep 2<\/td>\n<\/tr>\n
GPU clearly below full load, drops in fights<\/td>\nCPU, memory or system<\/td>\nSteps 5 and 6<\/td>\n<\/tr>\n
Result dropped after a patch with a config installed<\/td>\nThe update overwrote gameinfo.gi<\/td>\nStep 4<\/td>\n<\/tr>\n
Stutter only in the first matches after an update<\/td>\nThe game recompiles shaders<\/td>\nPlay two matches and measure again<\/td>\n<\/tr>\n
FPS counter stays flat but the game stutters<\/td>\nNetwork or Wi-Fi<\/td>\nCable instead of Wi-Fi<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

When your hardware is the limit<\/h2>\n

Valve has not published hardware requirements for Deadlock and the big hardware outlets have not tested it yet. If after every step the GPU still runs near 100% and FPS is low, what remains is a stronger GPU. If the GPU has headroom while the CPU cores stay heavily loaded through the match, what remains is a faster CPU.<\/p>\n

Deadlock optimization with us<\/h2>\n

This guide covers what you can do yourself. On a remote session we do far more, and we measure the effect on the same fight from your replay before and after the changes. We set up Windows remotely and the BIOS together over a Discord call: you show the screen with your phone and we walk you through every setting. Windows 11 optimization costs 200 PLN, and the Advanced package with BIOS, memory and safe overclocking costs 400 PLN.<\/p>\n

If you first want to know what limits your PC, the remote performance diagnostics<\/a> for 150 PLN finds the cause, and if the hardware is to blame you get a report on what to replace. Packages and dates are listed under remote PC optimization<\/a>.<\/p>\n

Settings and launch options take fifteen minutes, the config needs fixing after every big patch, and the rest of the frames come back in Windows, memory and the BIOS. Measuring on the same replay shows which step worked on your PC.<\/p>\n

Frequently asked questions<\/h2>\n
\nHow do I optimize Deadlock?<\/strong><\/summary>\n

Measure FPS on a match replay, then work through in-game settings, launch options, config, Windows, and CPU and memory in the BIOS. After each step measure the same fight and keep only the changes that added frames.<\/p>\n<\/details>\n

\nHow do I turn on the FPS counter in Deadlock?<\/strong><\/summary>\n

Open the console with F7 and type cl_showfps 2. It is a smoothed counter that is easier to read in a fight.<\/p>\n<\/details>\n

\nDo Deadlock configs still work?<\/strong><\/summary>\n

Partly. Since City Never Sleeps the engine ignores 77 variables in gameinfo.gi, and every big update overwrites the file. We update our Deadlock Ranked CFG after every patch.<\/p>\n<\/details>\n

\nIs Deadlock harder on the CPU or the graphics card?<\/strong><\/summary>\n

Check GPU load in a fight. If it reaches full load, the GPU is your limit. If it has clear headroom and FPS drops, the CPU, memory or system is holding you back. The game itself spreads its work across the CPU's physical cores.<\/p>\n<\/details>\n

\nDirectX 11 or Vulkan in Deadlock?<\/strong><\/summary>\n

DirectX 11. Most players use it, and Vulkan very rarely does better, especially on GeForce cards. On a Radeon it is worth testing with the -vulkan launch option.<\/p>\n<\/details>\n

\nHow much does PC optimization for Deadlock cost?<\/strong><\/summary>\n

Windows 11 optimization costs 200 PLN, and the Advanced package with BIOS, memory and safe overclocking costs 400 PLN. Remote diagnostics that pinpoint the cause of low FPS cost 150 PLN.<\/p>\n<\/details>\n