Counter-Strike 2's Rush Hour Update Broke Every Crosshair Code You Saved. Valve's Notes Never Mention It.

CS2 called my own crosshair code invalid on September 22. The code was fine the day before.

Valve rebuilt the crosshair system in the Rush Hour update that afternoon, and the string sitting in my notes file went from correct to rejected while the download ran. The game's wording does not help: "Invalid or old crosshair code" reads like you mistyped something, so the first thing most people do is paste it again more carefully.

What the patch notes say, and what they leave out

The September 22 notes give crosshairs four lines. Quoted in full: "Crosshairs have been updated to be resolution independent." "A new 'Crosshair/Scopes' tab is available in the Settings menu, and includes updated crosshair settings." "Added new crosshair styles." "Updated the default crosshair to 'Dynamic Quad,' which better represents weapon accuracy."

Not one of those mentions share codes. Neither does the follow-up update on September 23, which goes into real detail about the new system.

That September 23 post is where the actual change is written down: "The new crosshair thickness and length units are in pixels. In the past, the values were defined with an arbitrary scale and converted to pixels based on display resolution so the same value would result in different pixel counts at different resolutions." Valve then gives an example. A crosshair one pixel wide with an eight pixel bar and a four pixel gap is thickness = 1, length = 8, gap = 4.

That is the whole thing. The numbers used to be measured against your screen height. Now they are pixels you can count. An old code describes a crosshair in units the current game stopped using, and it turns the code down rather than drawing you something you did not ask for.

I have no idea why neither post says this plainly. Every player with a saved code learned it from an error message.

Valve published that shot of the same patch's bullet impact work in the Rush Hour post on September 22, under the heading "Change You Can See". The crosshair change got no screenshot at all.

What actually stopped working

Your saved code, first. Then every pro crosshair code recorded before September 22, which is nearly all of them: the ones in video descriptions and the ones sitting in pro settings lists that nobody has touched since.

Your config too, if it had crosshair lines in it. SyberiaK, who maintains the csxhair project, catalogued the command changes on September 23: cl_crosshairgap is now cl_crosshair_gap, cl_crosshairsize is now cl_crosshair_length, and cl_crosshaircolor, cl_fixedcrosshairgap and cl_crosshair_outlinethickness no longer exist. Removed commands do not announce themselves when a config runs. They fail somewhere in your autoexec and leave you staring at the default Dynamic Quad crosshair, trying to remember what you changed.

Do not retype your old numbers

This is where an evening goes. Nothing stops you typing your old thickness of 0.5 into a field that now counts pixels, and the game will accept it. You get a crosshair half a pixel thick, decide the update ruined crosshairs, and go looking for a way to revert.

One more detail from the September 23 notes is worth knowing before you rebuild anything. The game now rescales pixel counts when your resolution changes. Valve's example: a crosshair configured at 1280x720 with a thickness of 2 becomes thickness 4 at 2560x1440, so it stays proportionally the same. The resolution you configure at is the baseline everything else is derived from, which makes it more important than whatever resolution you happen to be in when you next load the game.

Why this is worth ten minutes rather than a shrug

A crosshair is the one setting you read without looking at it. You know where the gap ends relative to a head at the far side of mid, and you learned that over hundreds of hours. Swapping to a default you did not pick costs you the reference, and you feel it as vague inaccuracy rather than as a settings problem, which is exactly the kind of thing people tilt into instead of fixing.

There is a fairness angle in it too. Players who screenshot their settings page are fine. Players who kept a share code and nothing else lost the record, and share codes were the thing Valve told everyone to use.

What you can actually do

Rebuilding by eye in the new Crosshair/Scopes tab works. It takes twenty minutes and rarely lands on what you had, because memory of a crosshair is worse than people think.

crosshairrestore.com, which appeared after the update, reads an old code and gives you back the settings plus console commands. That hands you the numbers, and you apply them yourself.

We went at it from the other end. Our crosshair code converter reads the old code and returns a new one, the kind you paste under Settings, Crosshair / Scopes, Share or Import. Pick your resolution before you convert, since that sets the baseline the game rescales from. If your config also had crosshair lines in it, the settings generator writes them with the command names the current game answers to.

The one thing to do today

Convert the code, then put the new string back wherever you keep your settings and delete the old one. A dead code in your notes is how you paste it into the game again in three months and blame the update a second time.