NewsCounter-Strike 2
CS2 update closes Cache gaps and rebuilds camera tools
Counter-Strike 2's latest patch addresses competitive issues on Cache. It also restructures custom camera and spectator HUD tools for creators.
Competitive fixes arrive for Cache
Counter-Strike 2's September 9, 2026 update tackles several Cache issues tied to map integrity and round-to-round consistency. Valve closed various gaps in the map and removed an unintended wallbang position on the B site. Fixes of this kind do more than clean up rough geometry: they make commonly held angles, defensive cover and rotation choices behave closer to what teams reasonably expect.
The patch also restores a missing competitive CT spawn point and adds more T spawn positions. Spawn distribution can influence which player reaches an opening route first, so even a compact note like this matters to coordinated teams. The update does not redesign Cache or announce a balance overhaul; its map changes instead focus on making the existing competitive layout operate more consistently.
CSPlayerCamera becomes CustomPlayerCamera
The most substantial creator-facing change is a rework of CSPlayerCamera, now named CustomPlayerCamera. The revised component adds GetPlayer, GetMode, SetMode and SetFollowConfig functions. Custom map authors, broadcast-tool developers and other creators can therefore read the followed player and manage camera modes through a clearer set of controls.
Valve has deprecated the older IsEnabled, SetEnabled and SetIsControllingAngles functions. Deprecation does not necessarily mean every existing Workshop project stops immediately, but it is a clear signal to migrate before later compatibility problems appear. Projects with custom observer systems should retest camera transitions, angle ownership and follow configuration after adopting the new interface.
More deliberate spectator HUD behavior
A new observable property has been added to custom_hud_layout. It controls whether an observer sees the interface as it appears to the player being spectated, and it defaults to false. That gives HUD creators an explicit way to decide when player-facing interface information should also be reproduced for observers rather than relying on ambiguous behavior.
The update also fixes several cases where stale custom_hud_layout state could remain after switching spectator targets. Two top-level classes driven by client state, HUD_BUYMENU_VISIBLE and HUD_SCOREBOARD_VISIBLE, are now available as well. Designers can use those states to adapt interface elements when the buy menu or scoreboard is open, producing cleaner custom layouts for play and broadcasts.
What players and creators should check
For regular competitors, the practical changes are concentrated on Cache. Teams should stop relying on the corrected B-site wallbang, verify familiar cover around the repaired gaps and test opening routes across the expanded spawn distribution. Because the supplied notes do not describe weapon, economy or global movement adjustments, practice time is better spent confirming map-specific timings than rebuilding every broader match strategy.
Workshop creators and broadcast operators have a longer checklist: audit references to CSPlayerCamera, replace deprecated calls where possible, and verify the new HUD classes under real spectator transitions. Testing rapid target changes is particularly sensible given the stale-state fixes. CS2 skins and other in-game items can be traded securely on GameinShop with escrow protection.
Source: Steam News