any of you guys wouldn’t know how to make the crosshairs smaller, would you? on triple screen they are insanely huge.
Our problem is the reverse of what you’re having; we can’t see the MP5’s reticule.
I wish someone would tell us how to make the reticule pips thicker.
yeah but figuring out how to change crosshair size is my problem too, so I’ll stick around
Me getting chewed up because of the Lilliputian reticule:
(I’m currently making a Let’s Play)
I haven’t figured out how to change the size, yet - but it is possible to change the crosshair’s color (to [COLOR=’#00FFFF’]Cyan or [COLOR=’#7FFF00’]Chartreuse, for example).
There’s a post of mine that describes how to do that (if you didn’t know):
To adjust the opacity (alpha) of the crosshair, change the ‘crosshair_color_alpha’ CVar’s value to anything from “0” (invisible) up to “255” (solid).
Example:
crosshair_color_alpha "123"Let’s hope the next update brings a shiny new options panel / tab for crosshair and HUD colors, size, type, ecetera. 
Helllo Jenova,
Yes, I did try out your guide. I will be making a heads-up article about it and I’ll give you a shoutout in my site: https://imbacore.blogspot.com. 
We need to find a way to thicken the MP5’s reticule though. Either that or tomorrow, I’m going to start taping cut-up transparent straws on my LED. 
)
Ooh, thank you! :what:
By the way, I found a neat little ‘trick’ to add a little helper to the HUD, I’ll be posting it in all its detail, in just a few hours or minutes (still need to edit some things).
All I can say is, that you’ll be able to toggle it (On/Off) by the touch of ‘a’ button (whichever you choose).
I like the idea with the tape, although I’d assume it would leave some unpleasant residues, after removing it (for another game, etc.)… 
if is tipical to change size, why not just change the crosshair to another one?
wow… THAT site brings back old memories!
hmmm… must try this.
Just buy these lol.
ok I lol’d irl!
Solved the MP5 problem with a piece of straw. ) Gave a shoutout to Jenova19 in the 11th part of my Let’s Play series (should go up within the next 24 hours). Part 10 just went live:
Sorry about the delay, I am working on two posts at the same time (the one for the HUD Transparency thread and the one about the helper I mentioned before), but I’m really pushing towards getting at least one of them done in time (probably today).
Seems theres no real fix for it so I guess my problem will be infinetly worse. I play in 3D nVidia give you a 3D lasersight which works in practically every game but not HL2 BM etc. When you hit the key (F12) it comes up in green writing "3D lasersight turned on/off but there is no visible difference. 3D works very well but the crosshair is doubled except the Gluon cannon for some reason works fine - the crosshair reacts to surfaces IE: If Im pointing at a distant wall the crosshair will be on that wall, If I turn back to a wall close to me it is on that wall dead center and on its own, the other crosshairs as I said there are two and they appear to be on the top of the screen probably where the 2D image would normally be. I’d love a fix for it.
[COLOR=’#FFAA00’]How-To ‘bind’ a key (TOGGLE) to enable or disable an additional reticle / crosshair on the screen.
Description:
This is a mini-guide - it explains how to add an ‘extra’ reticle around the crosshair for all weapons (including the Crowbar, Grenades, etc.), if you choose to follow its instructions.
It is nothing special, just a little helper for all of you who are having trouble seeing the crosshair (it’s a bit ‘cheaty’, though - well, sort of).
The first section describes how to ‘implement’ the reticle and bind it to a toggleable (On / Off) key, using a script, the next ([OPTIONAL]) section describes how to bind another script to a key, to enable and disable the reticl on HOLDING said key.
It also includes a short section showing examples of how it would look like, if you chose to add one of the scripts to the autoexec.cfg directly.
You may choose whichever you like best (TOGGLE = Press once to enable, press again to disable; HOLD = Press and hold to enable, release to disable).
Also, the method I chose for this guide is (probably) unecessarily complicated, since you can just add the script file’s lines to the autoexec.cfg directly (as mentioned above), but for the sake of a more clean ‘implementation’, I recommend following and using the instructions below.
If you do not have any problems with scripts being executed from the autoexec.cfg file, rather than externally (from another config / script file), be sure to follow the steps from ‘[COLOR=’#FFAA00’][OPTIONAL 2] Mini-Guide (Examples for autoexec.cfg):’ to the end of this post.
The “sv_cheats” and “developer” commands are not needed for this to work!
Preview:
^- Enabled -^
^- Disabled -^
Note: “^-” and “-^” are supposed to be arrows, pointing up.
[COLOR=’#D08900’]► Mini-Guide (Part 1 [Config P1/2]):
- Close Black Mesa.
- Browse to this location: ‘\SteamApps\sourcemods\BMS\cfg’.
- Locate the file ‘autoexec.cfg’, copy and paste it into the same location (directory) and open the newly created file with a text-editor (Notepad++ or anything similiar [preferably with line-counting]).
- Select all the text inside (press Ctrl + A on your keyboard) and delete it (press Del on your keyboard).
- Add the lines from inside the Code-Box below into the file and save it.
Lines to add (this is a TOGGLE Script):
alias "toggleReticle" "incrementvar hud_draw_fixed_reticle 0 1 1"
bind <KEY> "toggleReticle"Note: Replace with any key you want to bind the (toggleable) reticle to (such as: T, G, X, etc.).
Note 2: More information about alias and incrementvar can be found by clicking on the previous links (within this sentence).
[COLOR=’#D08900’]► Mini-Guide (Part 2 [Config P2/2]):
- Once the file has been saved, close the text-editor.
- Rename the file from ‘autoexec - Copy.cfg’ to ‘.cfg’ (replace with any name you want [toggleCrosshairReticle, for example]), without using special characters.
- Locate and open the file ‘autoexec.cfg’ (inside the cfg folder) with a text-editor.
- Add the name of the file you’ve previously renamed as a line to the autoexec file, as shown below.
autoexec.cfg (Edited):
exec config.cfg
exec <FILENAME>.cfg
//exec threading.cfg
Note: Replace with the previously specified file name (e.g. toggleCrosshairReticle).
To revert the file back to default, simply remove the “exec .cfg” line entirely.
How to proceed:
- Save the file and close it.
- Start Black Mesa, load a map or savegame and test the script, by pressing the key you’ve previously specified (via the bind command / line) in the script file.
Note: If you see an orange reticle / crosshair in the center of your screen, the script has been successfully executed and is ready for use (since it is toggleable, simply press the key again and the reticle should disappear)!
If you are interested in more details (such as: additional commands, etc.), feel free to read the rest of this post - if you’re satisfied with what you got so far, go play the game and hit stuff!
[COLOR=’#D08900’]► Mini-Guide Demonstration (Part 1 [Screenshots P1/1]):
Without the additional reticle / crosshair (disabled):
Size: 1920x1080
With the additional reticle / crosshair (enabled):
Size: 1920x1080
[COLOR=’#FFAA00’][OPTIONAL] How-To ‘bind’ a key (HOLD) to enable or disable an additional reticle / crosshair on the screen.
This section is purely optional - it explains how to add a script to the autoexec config, which allows you to enable or disable the reticle by HOLDING the specified key (as long as the key is held down, the reticle is present; on release, it disappears).
[COLOR=’#D08900’][OPTIONAL]► Mini-Guide (Part 1):
- Close Black Mesa.
- Browse to this location: ‘\SteamApps\sourcemods\BMS\cfg’.
- Locate the file ‘autoexec.cfg’, copy and paste it into the same location (directory) and open the newly created file with a text-editor (Notepad++ or anything similiar [preferably with line-counting]).
- Select all the text inside (press Ctrl + A on your keyboard) and delete it (press Del on your keyboard).
- Add the lines from inside the Code-Box below into the file and save it.
Code-Box (this is a HOLD Script):
alias "+reticle" "hud_draw_fixed_reticle 1"
alias "-reticle" "hud_draw_fixed_reticle 0"
bind <KEY> "+reticle"Note: Replace with any key you want to bind the reticle to (such as: T, G, X, etc.).
Explanation:
First, the command “hud_draw_fixed_reticle 1” is assigned to the alias +reticle (+ for key down [press]) - this enables the reticle (as long as the key is held).
Then, the command “hud_draw_fixed_reticle 0” is assigned to the alias -reticle (- for key up [release]) - this disables the reticle (as soon as the key is released).
Lastly, the alias +reticle is bound to the specified key.
Originally I had added a “wait” command as well, but since there are problems with higher intervals (wait 100, for example), causing the script to start mocking up and get caught in one or the other state (On or Off), if the bound key is pressed repeatedly, I decided not to include it.
You can try to add it, if you want to:
alias "+reticle" "hud_draw_fixed_reticle 1"
alias "-reticle" "wait <VALUE>; hud_draw_fixed_reticle 0"
bind T "+reticle"Note: Replace with any valid value (10, 100, 1000, etc.).
[COLOR=’#D08900’][OPTIONAL]► Mini-Guide (Part 2):
- Rename the file from ’ - Copy.cfg’ to ‘.cfg’ (replace with any name you want [holdCrosshairReticle, for example]).
- Locate and open the file ‘autoexec.cfg’ (inside the cfg folder) with a text-editor.
- Add the previously edited CFG file’s name as a line to the autoexec file, as shown below.
autoexec.cfg (Edited):
exec config.cfg
exec <FILENAME>.cfg
//exec threading.cfg
Note:Replace with the previously specified file name (e.g. holdCrosshairReticle).
autoexec.cfg (Original):
exec config.cfg
//exec threading.cfg
How to proceed:
- Save the file and close it.
- Start Black Mesa, load a map or savegame and test the script, by pressing (and holding) the key you’ve previously specified (via the bind command / line) in the script file.
Note: If you see an orange reticle / crosshair in the center of your screen, while holding down the specified key, the script has been successfully executed and is ready to use (release the key and the reticle should disappear)!
[COLOR=’#FFAA00’][OPTIONAL 2] Mini-Guide (Examples for autoexec.cfg):
autoexec.cfg (TOGGLE)
exec config.cfg
//exec threading.cfg
alias "toggleReticle" "incrementvar hud_draw_fixed_reticle 0 1 1"
bind <KEY> "toggleReticle"Note: Replace with any key you want to bind the (toggleable) reticle to (such as: T, G, X, etc.).
autoexec.cfg (HOLD)
exec config.cfg
//exec threading.cfg
alias "+reticle" "hud_draw_fixed_reticle 1"
alias "-reticle" "hud_draw_fixed_reticle 0"
bind <KEY> "+reticle"Note: Replace with any key you want to bind the reticle to (such as: T, G, X, etc.).
[COLOR=’#D08900’]► Mini-Guide Extras (Part 1 [CVars P1/1]):
This is just an extra section, listing different commands / CVars for you to play around with (including the one demonstrated in the video above).
hud_reticle_alpha_speed:
hud_reticle_alpha_speed <VALUE>Note 1: Replace with any valid value (0 and above) - it affects the time that is needed for the reticle to fade away, when you sprint (Examples: 0 = Does not fade; 350 = Fades away slower; 700 = Default (faster than 350); 1000 = Fades away faster (than 350 and 700); etc.).
For a demonstration, see the video below (“Demonstration: hud_reticle_alpha_speed - YouTube”).
Video: Demonstration: hud_reticle_alpha_speed - YouTube
Note 1a: This is a small collection of clips, for 4 different settings (0, 350, 700, 1000) of the above command “hud_reticle_alpha_speed”, I edited into one, including text overlays.
It shows how each of the four settings above affect the reticle’s time to fade from solid to invisible and back.
hud_reticle_minalpha:
hud_reticle_minalpha <VALUE>Note 2: Replace with any valid value (between 0 [= invisible] and 255 [= solid]) - Determines the reticles’ minimum opacity (alpha).
hud_reticle_maxalpha:
hud_reticle_maxalpha <VALUE>Note 3: Replace with any valid value (between 0 [= invisible] and 255 [= solid]) - Determines the reticles’ maximum opacity (alpha).
The minalpha and maxalpha commands may come in handy if the reticle is too ‘apparent’ for your taste or if you simply want to reduce its overall opacity.
If you want to use any of the commands above, just add the preferred one (including a custom value) to the autoexec.cfg or to the script file you created earlier.
There is another command called ‘hud_draw_active_reticle’, as well, but it seems to be unused at this point in time.
If it’d work it would probably be responsible for an ‘active’ crosshair (the size increases steadily as you fire your weapon or run), much like the “Auto-Size” setting in most multiplayer games.
To use the two alpha commands above, simply add them to the very end of the autoexec.cfg file (including a value, between 0 and 255), then save and close it.
You may want to test different values in-game, to see what setting you are most comfortable with.
[COLOR=’#FFAA00’][THE END] Not much to say:
Well, I guess this “Mini-Guide” quickly became a relatively large “Guide”, sorry about that.
I am well aware of the (potential) flaws of this guide, if you’re having trouble understanding or using it, please let me know!
Also, be sure to reply whether the scripts work or not!
EDIT (10-08-2012 - 08:24 PM): Updated the guide’s overall structure from ‘TOGGLE, Extras, HOLD, End’ to ‘TOGGLE, HOLD, Extras, End’.
I love you Jenova19. Gonna go try this now.
Let’s hope it works…
I can vouch for the toggle. <3
Holy popsicles batman, I have to try this out. Thanks!
Don’t expect a miracle, though…
This seems to be a ‘Source-Wide’ CVar / option, as it appears in both HL2 and TF2, although the latter does not work, properly.