Whole-pixel centres
Crosshair units are physical pixels and the centre is snapped to a whole device pixel, so lines stay sharp at 125%, 150% and 200% instead of being antialiased into a grey smear.
Compatibility
Over your game. Never inside it.
crshX draws an ordinary borderless window on top of the desktop. Everything below follows from that one decision — including the display modes it cannot cover, and the ones it will not pretend to.
- Windowed
- Supported
- Borderless
- Supported
- Exclusive fullscreen
- Not possible
- Multiple displays
- Supported
- Controller switching
- Not implemented
| Mode or situation | Result | Detail |
|---|---|---|
| Windowed applications | Works | The overlay draws over ordinary windows and every click passes through to them. |
| Borderless fullscreen | Works | The recommended mode for full-screen play: a windowed overlay can be composited over it. |
| Multiple displays, mixed resolutions | Works | Each display is enumerated with its own physical rectangle; the overlay can target any one of them. |
| Display scaling (100%–200% and fractional) | Works | Crosshair units are physical pixels. The centre is snapped to a whole device pixel, so lines stay sharp at 125%, 150% and 200% instead of turning into a grey smear. |
| Displays with negative coordinates | Works | A monitor left of or above the primary one has negative virtual-desktop coordinates; placement uses them as they are. |
| Exclusive fullscreen | Not supported | A windowed overlay cannot be composited into an exclusive fullscreen swap chain. Switch the game to borderless fullscreen. This will not be worked around. |
| Games whose anti-cheat blocks overlays | Limited | Some titles hide or refuse third-party overlay windows. crshX does not bypass that, because every bypass technique is one this product refuses to use. If a game blocks the overlay, switching still happens; you just cannot see it. |
| Secure desktop and the lock screen | Not supported | A normal desktop window cannot draw over protected surfaces by design. |
| Screen capture tools | Limited | Whether the overlay appears in a capture depends on how the tool captures, not on crshX. Window-by-window capture normally excludes it; full-desktop capture normally includes it. |
| Controller input | Not supported | Dynamic switching is keyboard only. No controller, mouse-wheel or gesture switching is implemented. |
01Anti-cheat
The position, stated plainly
Some games hide or refuse third-party overlay windows. crshX does not attempt to work around that, because every technique that would work is one this product refuses to use. If a game blocks the overlay, dynamic switching still happens — you simply cannot see it.
The application asks for no elevation, installs no driver and opens no other process. Whether a given game or anti-cheat vendor permits a desktop overlay is that vendor's decision, not something this product can settle for you.
Not present in this codebase
- Inject code into a game or any other process
- Read or write another process's memory
- Hook, patch or modify game files
- Bypass or interfere with anti-cheat software
- Generate synthetic keyboard or mouse input
- Automate gameplay in any way
- Install a kernel driver
- Request administrator rights
- Disable or weaken Windows security features
02Verification
What has actually been run
201 automated tests cover the crosshair model, geometry, validation, colour handling, persistence, import and export, profiles, hotkey parsing and the switching policy. They were run with dotnet test in a .NET 8 container (Linux), Release configuration.
Verified here
- Release build of the whole solution with no warnings
- 201 automated tests passing, 0 failed
- A self-contained win-x64 single-file publish producing crshX.exe, and the same build as an unpacked folder, both published with their SHA-256 on the download page
Not yet verified
- Everything that needs a Windows desktop: the window itself, the overlay, click-through, hotkeys, display changes and the installer
- Idle CPU and memory, which have not been measured and therefore are not quoted
- Code signing: the build is unsigned, so SmartScreen will warn on first run
No claim is made about running on Windows
The window, the overlay, click-through, hotkeys, display changes and the installer cannot be executed in the environment where they were written. They carry no verified claim. The Windows smoke test guide exists to turn each of those rows into evidence.
| Fixed |
|---|
| A cancelled keyboard-listener start could leave a thread that never pumped messages, which could block shutdown |
| The small icon frames drew a closed square instead of an open targeting frame |
03Displays
Displays, scaling and coordinates
Placement is computed from the display's real device rectangle rather than from assumptions about the primary monitor, which is what makes the awkward cases work.
Negative coordinates
A display to the left of or above the primary one has negative virtual-desktop coordinates. Those values are used as they are, so the crosshair lands where it should.
Reacts to the display set
Adding, removing, moving or resizing a display repositions the overlay. A saved display that has been disconnected falls back to the primary with a warning in the log rather than leaving the overlay off-screen.
04Systems
Requirements
| Item | Requirement | Note |
|---|---|---|
| Operating system | Windows 10 (1809 / build 17763) or Windows 11 | x64 only. This is the declared support range; the build has not been run on either yet. |
| Runtime | None | The distributed build is self-contained and includes .NET 8, so there is nothing to install first. |
| Privileges | None | The process manifest requests asInvoker. No UAC prompt should appear at any point. |
| Disk | 63.0 MB, one file | The folder build is 64.3 MB as a ZIP and about 150 MB unpacked; an install takes about 70 MB. |
| Network | Not used | There is no update check, no telemetry, no account and no licence server. |
Full instructions, including what to expect on first launch, are in the quick start guide.