It feels hard to get the devs’ attention on this, even though it’s a pretty crucial issue for how the game feels. Especially for players who don’t know how to fix it themselves.
You don’t have to disable fullscreen optimizations. This fix removes the stutter while also allowing the game to be launched through Steam instead of having to open it from the bin folder like before.
UPDATE 2:
Issue Summary:
When launching Deadlock through the Steam Client, severe frametime spikes occur every time mouse or keyboard input is provided. These spikes stabilize after a few seconds of no input but return immediately upon movement. This issue does not occur when launching...
UPDATE:
Fixed! The FPS drops when pressing keys or clicking the mouse were resolved by:
Disabling fullscreen optimizations on the Deadlock executable.
Running the game directly from the desktop instead of launching it through Steam.
After this, my FPS is completely stable, even during input.
UPDATE:
Fixed! The FPS drops when pressing keys or clicking the mouse were resolved by:
Disabling fullscreen optimizations on the Deadlock executable.
Running the game directly from the desktop instead of launching it through Steam.
After this, my FPS is completely stable, even during...
UPDATE:
Fixed! The FPS drops when pressing keys or clicking the mouse were resolved by:
Disabling fullscreen optimizations on the Deadlock executable.
Running the game directly from the desktop instead of launching it through Steam.
After this, my FPS is completely stable, even during input.
Description:
I’ve been noticing consistent frametime spikes whenever I press any keyboard key or mouse button while playing Deadlock.
Even though my average FPS is very high, the input causes visible stutter and a sharp drop in 0.1% lows.
For example, my 0.1% lows drop from around 120+ down to...
I’m having the exact same issue as well.
Any time I press a key or mouse button, my frametime spikes — even though my average FPS is very high. It’s especially noticeable in my 0.1% lows, which drop from 120+ down to around 40 whenever an input is pressed.
It doesn’t happen in other Source 2...