Riot Games shipped Patch 13.00 on June 23, 2026, opening Act 4 with Sentinel buffs, shorter Initiator cooldowns, and a brand new map called Summit. Three days later, r/VALORANT and the official support forums were full of the same complaint that has followed the game since its 2020 beta: frames dropping mid-fight, on rigs that have no business struggling.
That complaint isn’t new, and that’s the real story here. Dot Esports has tracked the “Low Client FPS” warning as a recurring issue tied to overlay software and driver conflicts, not raw hardware limits. A player running an RTX 4090 can hit the same wall as someone on integrated graphics, which is part of why the fix rarely involves buying new parts.
What’s actually causing the frame drops?
The pattern repeats after almost every major patch. Valorant recompiles shader caches when a build changes enough visual assets, and if that process gets interrupted, the game hitches every time a new ability fires. Riot Vanguard adds another layer: recent Windows 11 24H2 security features have introduced conflicts that show up as brief stutters during fights rather than a flat drop in average FPS, so a scoreboard reading 240 FPS can still feel choppy in a clutch round.
None of this is unique to Patch 13.00. It shows up whenever Riot pushes a build heavy enough to force a shader rebuild, which is roughly every Act. What changes each time is which hardware combination gets hit hardest, and this cycle it’s been AMD Radeon users with Instant Replay enabled, plus anyone running full-screen optimization instead of exclusive fullscreen mode.
Does the new Summit map make things worse?
Summit adds a wrinkle. Forbes esports contributor Mike Stubbs reported that the map’s signature feature, droppable walls at both sites and mid, permanently reshapes sightlines once triggered, and Riot gave it a two-week reduced-RR-loss window specifically because of the learning curve. Early tracking from MetaBot.gg puts Summit’s competitive play rate at 0.4 percent across roughly 1,380 matches so far, low enough that queue times spiked while players avoided it or requested rematches.
If you’re trying to keep up with Act 4 changes without reading the raw patch notes every cycle, a video game news source like egw.news usually has the agent and map breakdowns summarized within hours, along with roster and event coverage running alongside it. That’s often faster than parsing Riot’s own changelog, especially during a patch this dense. The official patch notes confirm Fracture and Pearl left the competitive and deathmatch queues the same day Summit and the new Retake mode arrived, so the map pool shrank and expanded at once.
What can you do about it before the next patch lands?
Riot’s own troubleshooting page for frame rate issues is a reasonable starting point: confirm your specs meet the recommended minimums, run a clean boot to clear background processes, and dial graphics settings all the way down if a fight still feels choppy at max settings. It’s a blunt checklist, but it catches most of the obvious culprits before you touch drivers or BIOS settings.
I ran a quick before-and-after test myself after Patch 13.00 dropped: three Range warmups with the shader cache untouched, then three more after manually clearing it and rebooting. Frame time spikes during ability casts noticeably smoothed out on the second set, even though the average FPS number barely moved. That gap between what the number says and what a fight actually feels like is exactly why so many players assume their hardware is the problem when it usually isn’t.
Disabling AMD’s Instant Replay, turning off fullscreen optimization for the exe, and closing overlay apps like Discord’s or Nvidia’s GeForce Experience still resolve most cases. None of it is new advice. It just needs repeating every time a patch this size rolls out, because the underlying causes haven’t changed since Valorant’s earliest days, only the specific combination of software fighting for the same CPU cycles.
With Act 4 running through the summer and Champions qualification stakes climbing, players chasing rank stability will want these settings locked in before queue volume peaks again, not after another patch reshuffles the map pool.
How Is the Community Actually Reacting to Patch 13.00?
The reaction split almost immediately. Over on VLR.gg’s patch notes thread for 13.00, one of the top replies summed up the Sentinel changes bluntly: one commenter argued the buffs were simply too much for the role all at once. Several other posts in the same thread pointed out that Killjoy’s turret rate of fire and Sage’s doubled self-heal landed in the same patch as the Summit rollout, which made it harder to tell whether early queue frustration was about performance or about facing reworked agents on an unfamiliar map. That overlap is worth separating out, since FPS complaints and balance complaints tend to get lumped into the same “the patch broke everything” narrative even when they have almost nothing to do with each other.
