A heavily customizable, fullscreen-compatible crosshair overlay shader.
| Feature | Supported |
|---|---|
| Fullscreen | ✔️ |
| No input lag | ✔️ |
| No FPS impact | ✔️ |
| Customizable | ✔️ |
| One-time setup | ✔️ |
- Install ReShade from reshade.me.
- Click "Select game" and choose your game executable (take note of the path for step 6!).
- Check the appropriate game rendering API. If you don't know which one to pick, try the "Direct3D 10/11/12" option.
- Skip any extra shaders or options the ReShade installer might suggest (unless you know what you're doing).
- Download the latest shaders.zip from the releases page.
- Extract all files and folders from shaders.zip to the same folder you selected in step 2.
- Launch your game. If everything went correctly, you should see the crosshair appear. If you want to configure the crosshair, open the ReShade overlay by pressing the "Home" key.
Q: Does this work in fullscreen?
A: Yes. Rather than rendering the crosshair outside the game, the injected ReShade overlay renders within the the game.
Q: Will this get me banned?
A: No, reshade-xhair will not get you banned by itself. HOWEVER, the program that it runs on (ReShade) is blacklisted by some games/anti-cheats. Make sure you look up whether ReShade can be used safely on the desired game before installing it.
Use at your own risk!
For EA games such as Battlefield 4, it is against ToS to use an overlay of any type. Punkbuster and Fairfight take screenshots of the overlay and could result in official action being taken to ban your account. Additionally third party anticheats such as GGC, ACI, PBBans and BF4DB will ban you for usage.
Q: How do I uninstall?
A: Run the ReShade installer, select your game then click "Uninstall". If you want to keep ReShade but not the xhair shader, you can delete xhair.fx from the reshade-shaders/Shaders directory located in your game folder.
Q: My game is crashing, how do I fix it?
A: Go to your game folder and rename dxgi.dll to d3d11.dll.
Q: I'm getting suttering/fps drops/misc issues
A: reshade-xhair is unlikely to be the issue. It's probably a ReShade issue. Google it.
