Deadlock’s Performance Complaints Are Back On High-End PCs

On July 2, 2026, Deadlock creator Kunii posted the kind of performance complaint that gets attention because the hardware does not sound like the problem. The short version: an RTX 3070 laptop should not be turning Deadlock into an 80 FPS game with dips toward 60, at least not in a way that feels acceptable to a competitive player.

That post became the freshest high-engagement signal in the scout queue, but the complaint is not new. Deadlock’s official bug-report forum has months of performance reports: heavy frame drops during teamfights, stutters that get worse over time, memory and VRAM suspicions, and players saying restarts or settings changes do not reliably solve the problem. Some reports are old, some are hardware-specific, and some may be local PC issues. The pattern is still hard to ignore.

A February forum thread described drops from high frame rates into 30 FPS territory during teamfights, graphically intense map areas, or quick camera movement. A December thread from a player with an RTX 4070 Ti Super and Ryzen 7 7800X3D described major drops during big fights and performance degrading over a session. In July, related forum search results continued to show “still extreme optimization problems” and possible memory-leak threads near the top of the similar-thread list.

The Reddit reaction around the latest Yoshi update says the same thing in community shorthand. While some players were asking for matchmaking and item updates, others asked for a performance or optimization update and traded hardware examples in the replies. One player said a 5080 paired with an older Ryzen chip felt inconsistent. Another pushed back with a CPU-bottleneck read. That disagreement is useful: performance complaints are messy, and Deadlock is exactly the kind of game where CPU, GPU, RAM, drivers, effects, and late-game entity count can all be plausible suspects.

That is why the story should not be written as “Valve broke performance on July 2.” Kunii’s post did not prove a single patch caused the issue. The forum threads do not prove every affected machine shares the same bug. What they do show is that optimization has become a durable player-facing issue, especially when fights get crowded and competitive readability depends on stable frames.

For a closed, still-changing playtest, that is a serious user-experience problem. Deadlock can survive rough art, placeholder systems, and strange balance for a long time if players believe the match itself is responsive. It has a harder time surviving the feeling that the decisive fight was lost because a screen full of effects turned input into soup.

The practical next step is evidence. Players with performance problems should keep using the official bug-report forum with hardware specs, driver versions, match context, and reproducible moments. Creators can make the issue visible, but the useful fixes will come from patterns Valve can actually test.

Until Valve posts a public optimization note, the current framing is simple: Deadlock’s July performance discourse is a fresh wave attached to an old problem. High-end and midrange players are still reporting stutters, drops, and inconsistent frames, and the next major update will be judged partly on whether it makes fights feel smoother, not just more balanced.

Source Notes

• Kunii on X, July 2, 2026: optimization complaint.
• Official Deadlock forum, February 2026: performance and optimization report thread.
• Official Deadlock forum, December 2025: high-end PC performance-drop report.
• r/DeadlockTheGame: current player discussion mentioning optimization.