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 fixThe shortest safe order for this issue:
- Run the game without overlay hooks and verify raw mouse input before changing sensitivity.
- Use a short autoexec with only documented Source 2 cvars, then confirm it executes.
- 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.
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. 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 completeOne 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 answersCan I use my CS2 autoexec in Deadlock?
Is 8000 Hz polling worth it in Deadlock?
Controls & Peripherals
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.
Deadlock: Save File Location, Cloud Conflicts & Console Commands
Back up and repair Deadlock saves, resolve Steam Cloud version conflicts, and open the developer console or launch options with the correct argument set for Source 2.
Deadlock: Best Build, Graphics Preset Matrix & Beginner Checklist
A spoiler-light progression and build plan for Deadlock, plus Low, Competitive, and Ultra graphics matrices and the mechanics checklist for the first ten hours.
Deadlock: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Deadlock on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Source 2.