Controls & Peripherals / Deadlock / Source 2

Deadlock: Stable Mouse Input and Source 2 Console Settings

A conservative Source 2 input and frame-time setup for Deadlock, plus the overlay checks that actually matter.

Official Steam Store header artwork for Deadlock.

Deadlock is a Source 2 game with a very different feel from a tactical shooter. A copied CS2 autoexec is more likely to confuse the configuration than improve it.

Stable Mouse Input and Source 2 Console Settings

Verified field fix

The shortest safe order for this issue:

  1. Run the game without overlay hooks and verify raw mouse input before changing sensitivity.
  2. Use a short autoexec with only documented Source 2 cvars, then confirm it executes.
  3. Cap frame rate for consistency and test the same practice scenario after each change.

Raw input is the foundation

Disable mouse acceleration in Windows and remove overlays that hook the game process. Test a slow 360-degree turn in the practice area and watch for acceleration or skipped counts. Sensitivity is a preference; inconsistent movement is a bug.

<Steam>/steamapps/common/Deadlock/game/citadel/cfg/autoexec.cfg
fps_max 0
sensitivity 1.15
m_yaw 0.022
// Keep only commands that the current build accepts.
// Launch with +exec autoexec.cfg or exec it manually.
Verify every line in the developer console. An unknown cvar should be removed, not replaced by a copied guess.

Keep the autoexec short

A single frame cap and a verified sensitivity are enough for the first baseline. If a command is rejected in the console, remove it rather than inventing a replacement. Source 2 changes and community cvar lists go stale quickly.

Field notes before you change the build

Input for Deadlock passes through the device firmware, Windows, any vendor software, Steam Input if enabled, and finally the Source 2 client. Test one layer at a time, starting wired and with the vendor layer removed. A sensitivity change cannot repair a skipped USB report.

Use the same display refresh rate and a stable frame cap for every comparison. If aim or camera motion feels inconsistent only when frame time spikes, treat it as a performance problem before buying a new peripheral.

  • Do not stack two deadzones or two response curves.
  • Do not change DPI, polling rate, and in-game sensitivity in the same test.
  • Do not use a third-party injector to bypass an anti-cheat input path.

Check it before you keep it

Repeat the same practice-room test after each change

0 / 5 complete

One input chain at a time

When the setup feels right, write down the device, connection, profile, and in-game values. That baseline is more useful than another round of random sensitivity adjustments.

The line to keep

A good input setup is boring: raw, consistent, and verified. Keep the files small enough to audit after every patch.

Did this fix work on Patch Playtest build — March 2026 matchmaking update?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against Playtest build — March 2026 matchmaking update. Votes are local-only telemetry.

Deadlock: bench questions

2 answers
Can I use my CS2 autoexec in Deadlock?
Do not copy it wholesale. The games share Source 2 heritage, not an identical command set. Validate each cvar in Deadlock itself.
Is 8000 Hz polling worth it in Deadlock?
Only if the CPU has headroom and the mouse implementation is stable. Drop to 2000 or 1000 Hz when testing frame-time inconsistency.
Filed under

Controls & Peripherals

Patch tested: Playtest build — March 2026 matchmaking update

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.