{"id":5931,"date":"2026-03-27T21:03:55","date_gmt":"2026-03-27T19:03:55","guid":{"rendered":"https:\/\/ultimatemove.eu\/?p=5931"},"modified":"2026-05-10T13:15:16","modified_gmt":"2026-05-10T11:15:16","slug":"deadlock-fps-config-how-to-install-optimizationlock-and-actually-get-more-frames","status":"publish","type":"post","link":"https:\/\/ultimatemove.eu\/en\/deadlock-fps-config-how-to-install-optimizationlock-and-actually-get-more-frames\/","title":{"rendered":"Deadlock FPS Config: How to Install OptimizationLock"},"content":{"rendered":"
\"Deadlock<\/div><\/figure><\/div><\/div>\n\n\n

Most Deadlock \"fps guides\" tell you to set shadows to low and call it a day. That works - but it leaves 30-50% of the potential gains on the table. The real ceiling on Deadlock performance isn't your graphics settings. It's how the game communicates with your system, and that's exactly what OptimizationLock fixes.<\/p>\n\n\n\n

This guide covers what OptimizationLock actually does, how to install it correctly, which launch options matter, and what to set in Windows so the config has something to work with.<\/p>\n\n\n\n

\n\n\n\n

What Is OptimizationLock and Why Does It Exist<\/h2>\n\n\n\n

Deadlock runs on Source 2 - the same engine as CS2. Like CS2, it's heavily CPU-bound and ships with a default configuration that prioritizes stability over performance. That default config contains settings that make sense for Valve's servers and average hardware, but actively hurt frametime consistency on a tuned gaming PC.<\/p>\n\n\n\n

OptimizationLock is a community-maintained replacement for gameinfo.gi<\/code> \u2013 the main configuration file that controls how Deadlock loads engine settings, convars, and the rendering pipeline. The current version (V2, maintained by Sqooky and contributors) is built on Maihdenless's original work with one major improvement: every single AI-hallucination command from the original has been removed and replaced with verified, documented convars. Over 7,700 downloads on GameBanana. Updated March 27, 2026.<\/p>\n\n\n\n

Two versions are available:<\/p>\n\n\n\n

Performance<\/strong> - moderately reduces graphical quality, keeps the game readable. Recommended for most competitive players.<\/p>\n\n\n\n

Ultra Performance<\/strong> - prioritizes FPS above everything. Dramatically reduces visual quality. For older or weaker hardware.<\/p>\n\n\n\n

\n\n\n
\"Deadlock<\/div><\/figure><\/div><\/div>\n\n\n

Before You Touch the Config: Windows First<\/h2>\n\n\n\n

Installing OptimizationLock on a misconfigured system gets you maybe half the gains. The config assumes your Windows baseline is clean. Check these first:<\/p>\n\n\n\n

Power Plan<\/strong> - must be High Performance or Ultimate Performance. The Balanced plan throttles CPU frequency reactively, which creates exactly the kind of inconsistent frametimes that a tight engine config can't fix.<\/p>\n\n\n\n

To unlock Ultimate Performance (if it's missing from your power options):
<\/p>\n\n\n\n

powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61<\/em><\/strong><\/p>\n\n\n\n


Then set it in Control Panel - Power Options.<\/p>\n\n\n\n

Timer Resolution<\/strong> - you want 0.5ms locked, or the value that precisely stabilizes the timer on your specific hardware. Convars unfortunately don't cover this kind of function, though typically the game engine imposes its own rhythm on the timer unless you force a system-level cap beforehand. Use a lightweight tool like SetTimerResolution running as a startup service. On Windows 11, for this to work at all you need to add a registry entry: HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\kernel<\/strong> - add DWORD GlobalTimerResolutionRequests<\/strong> with value 1<\/strong>.<\/p>\n\n\n\n

Don't mess with bcdedit \/set useplatformclock<\/strong> - regardless of what you read on Reddit and YouTube, it causes scheduler instability on most modern systems and the DPC latency increase outweighs any timer precision gain.<\/p>\n\n\n\n

MSI Mode<\/strong> - check that your GPU and network card are running in Message Signaled Interrupt mode, not legacy interrupts. Legacy interrupts can generate DPC latency spikes that show up as stutter and micro-freezes. Use MSI Utility v3 or check Device Manager - Properties - Details - Resources.<\/p>\n\n\n\n

\n\n\n
\"Deadlock<\/div><\/figure><\/div><\/div>\n\n\n

How to Install OptimizationLock<\/h2>\n\n\n\n

Step 1 - Download<\/strong><\/p>\n\n\n\n

Go to GitHub repository: github.com\/Sqooky\/OptimizationLock<\/strong><\/a><\/code><\/p>\n\n\n\n

Download the gameinfo.gi<\/strong> file from the version you want (Performance or Ultra Performance).<\/p>\n\n\n\n

Step 2 - Find your Deadlock installation<\/strong><\/p>\n\n\n\n

In Steam: right-click Deadlock - Manage - Browse local files.<\/p>\n\n\n\n

Navigate to: \\game\\citadel\\<\/code><\/p>\n\n\n\n

You'll see the existing gameinfo.gi file there.<\/p>\n\n\n\n

Step 3 - Backup the original<\/strong><\/p>\n\n\n\n

Copy the original gameinfo.gi somewhere safe before replacing it. If the game updates and the new config is incompatible, you'll need this to restore and wait for an OptimizationLock update.<\/p>\n\n\n\n

Step 4 - Replace<\/strong><\/p>\n\n\n\n

Drop the downloaded gameinfo.gi into \\game\\citadel\\<\/code> and overwrite.<\/p>\n\n\n\n

Step 5 - Set to read-only (optional but recommended)<\/strong><\/p>\n\n\n\n

Right-click the file - Properties - tick \"Read-only\". This prevents Deadlock updates from overwriting your config automatically. If a major patch breaks the game after this, uncheck read-only and verify game files through Steam.<\/p>\n\n\n\n

\n\n\n\n

Launch Options That Actually Work<\/h2>\n\n\n\n

Right-click Deadlock in Steam - Properties - Launch Options. Paste this:<\/p>\n\n\n\n

-dx11 -m_rawinput 1 -high -preload -fullscreen +exec autoexec.cfg +@panorama_min_comp_layer_cache_cost_TURNED_OFF 256<\/strong><\/p>\n\n\n\n

What each option does:<\/p>\n\n\n\n

-dx11<\/strong> - forces DirectX 11 renderer. Vulkan supports FSR3 but DX11 consistently produces better FPS stability for most hardware in 2026. Test both and keep whichever gives you lower frametimes in a teamfight - not on the main menu. Some setups, particularly AMD\/Radeon, may perform better with -vulkan.<\/p>\n\n\n\n

-m_rawinput 1<\/strong> - forces raw mouse input, bypassing Windows mouse acceleration entirely. Non-negotiable for aim consistency.<\/p>\n\n\n\n

-high<\/strong> - sets the Deadlock process to high priority in the Windows scheduler. Combined with a tuned power plan, this reduces the chance of other processes eating into your frame budget during ranked games.<\/p>\n\n\n\n

-preload<\/strong> - preloads game resources at startup. Trades loading time for eliminated in-game stutter from asset streaming.<\/p>\n\n\n\n

-fullscreen<\/strong> - exclusive fullscreen. Lower input latency than borderless windowed. If you alt-tab constantly during play, swap to borderless and accept the ~1 frame latency cost.<\/p>\n\n\n\n

+@panorama_min_comp_layer_cache_cost_TURNED_OFF 256<\/strong> - reduces UI composition overhead. The Panorama UI in Source 2 games can eat CPU time during heavy teamfight moments. This caps the compositor cache cost and keeps the UI from stealing frame budget at exactly the worst possible moment.<\/p>\n\n\n\n

\n\n\n\n

In-Game Settings to Pair With the Config<\/h2>\n\n\n
\"Deadlock<\/div><\/figure><\/div><\/div>\n\n\n

OptimizationLock handles engine-level convars. These in-game settings complete the picture:<\/p>\n\n\n\n

Rendering<\/strong>: Direct3D 11. Matches the -dx11 launch option. Some setups, particularly AMD\/Radeon, may perform better on -vulkan.<\/p>\n\n\n\n

Scaling Mode<\/strong>: FSR2 (TAA) if you want frame stability, or Stretch if sharpness is the priority and you have a strong GPU. Avoid DLSS unless you're on a very high-end Nvidia card where it clearly outperforms.<\/p>\n\n\n\n

Texture Quality<\/strong>: Medium. Going lower gives minimal FPS gain - set it however you like or based on how much free VRAM you have.<\/p>\n\n\n\n

Shadow Quality<\/strong>: Low or Off. Highest single setting impact on FPS with the least gameplay cost in Deadlock.<\/p>\n\n\n\n

Ragdoll Quality<\/strong>: Off. Ragdolls are CPU work you don't need.<\/p>\n\n\n\n

Effects Quality<\/strong>: Low. Reduces particle density during things like Bullet Dance and other AoE ultimates. Your FPS in teamfights - where it matters most - will thank you.<\/p>\n\n\n\n

Depth of Field, Motion Blur, Bloom<\/strong>: All off. These are purely visual and hurt both FPS and readability.<\/p>\n\n\n\n

Reduce Flashing Effects<\/strong>: On. Helps during team ultimates and genuinely makes ability tracking easier in chaotic fights.<\/p>\n\n\n\n

VSync<\/strong>: Off. Always. Cap your FPS instead.<\/p>\n\n\n\n

FPS Cap<\/strong>: Set to your monitor refresh rate or slightly below (e.g. 237 for 240Hz) - this will vary depending on which limiter you use. An uncapped framerate on a 240Hz monitor wastes GPU frames and can cause GPU temperature spikes leading to thermal throttling during extended fights - stutter and floaty inputs. If you don't have temperature issues and know your hardware, leave it uncapped - it's always lower input lag if you're exceeding your Hz significantly in FPS.<\/p>\n\n\n\n

\n\n\n
\"Splash<\/div>
PLEASE NERF HER AIMBOT – IT’S CRAZY, WHAT IS THIS, HELP MOM.<\/figcaption><\/figure><\/div><\/div>\n\n\n

How to Check It Worked<\/h2>\n\n\n\n

After installing and launching with the new config, open the developer console (add -console<\/strong> to launch options temporarily) and type fps_max 0<\/strong>.<\/p>\n\n\n\n

For frametime specifically: add a performance overlay via Steam (Shift+Tab - in Steam settings - In-Game - FPS counter) or use RTSS (RivaTuner Statistics Server) to monitor 1% and 0.1% lows during a real match. OptimizationLock's primary benefit shows up in those low values during teamfights<\/strong> - not in peak FPS in the main menu.<\/p>\n\n\n\n

\n\n\n\n

Important: Valve and Config Files<\/h2>\n\n\n\n

As of March 2026 there's active discussion in the Deadlock community about Valve potentially restricting certain config convars. OptimizationLock V2 was specifically built to remove unverified commands and only include documented, legitimate convars - so it's in a better position than the original version if Valve does tighten restrictions, but that doesn't mean Valve won't change their mind (which would be unfortunate and harmful for players and the game long term).<\/p>\n\n\n\n

The safest approach: keep the original gameinfo.gi backed up, watch OptimizationLock on GitHub<\/a> after every major Deadlock patch, and update the config whenever it's revised.<\/p>\n\n\n\n

\n\n\n\n

What to Expect<\/h2>\n\n\n\n

Realistic numbers after OptimizationLock V2 and the Windows setup above:<\/p>\n\n\n\n