a cutie ~^_^~

the original darkfall online & gunz
~gunz bois 4 life~

do not make your own weapon script file.
you need to extract the appropriate ctx from tf2_misc_dir.vpk, and then use Vice to decrypt the ctx and convert it to a text file; it's under the scripts folder.
use GCFScape to open the tf2 vpk's: http://nemesis.thewavelength.net/index.php?p=26
Vice: https://forums.alliedmods.net/showthread.php?t=72924

your crosshairs, as installed with your hud, work fine as they're setup as HUD crosshairs.

with sv_pure 2, custom folders within materials\... (besides the loophole discussed in my main post) are effectively ignored; only "trusted_sources" are used (the main tf2 vpk's).

as such, messiah's method will not work with sv_pure 2 without preloading; custom vgui\crosshairs folders are ignored, as only the tf2 vpk's vgui\crosshairs folder is referenced.

i never knew you had such a nice collection of vtf crosshairs included with your hud though! will definitely play around with them.

there's artifacting in the vtf near the dot, and the wings don't have equal spacing from the dot.
if the dot is centered, then you need to close the gap between the wings slightly (seems left-sided currently).

that actually looks sick as fuck. subtle and plays well with your hud. very nice job.

mind posting your vtfs?

with your solution, you need to preload your crosshair for it to work in sv_pure 2 & you won't be able to edit it until you go back into an sv_pure 0/1 server.

your solution has been known for a while, but the overhead from preloading made hud crosshairs much more appealing for most people. and since you could overwrite the classmodelpanelBG with your vtf crosshair, you could even toggle it with a convar if you so desired (in other words, by overwriting the hud playerclass model panel, which can be toggled with the cl_hud_playerclass_use_playermodel convar).

however, this brought about the disadvantages of needing to manually position it based on resolution & needing to alt-tab & hud_reloadscheme to make changes. and more than anything else, typical HUD vtf crosshairs may be too finicky to properly center with your desired size; there's a good chance you need to make a compromise on the size of your crosshair to get it perfectly centered.

my method brings back the convenience of in-game crosshair resizing, coloring, & automatic centering while avoiding the need to preload.

omg luc plz call i need to know if ur ok

you could make 3 copies of your universal crosshair (after converting it to a vtf, if you haven't already done so), making the canvas size of your vtfs large enough to draw the numbers 1 through 3 in the corners on each of them respectively, and then point the crosshairs of each weapon to your new vtfs as necessary.

for example, primary weapons such as your scattergun or rocket launcher would point to your crosshair with a 1 down way in the corner; secondary weapons such as your pistol or soldier shotgun would point to your crosshair with a 2 down way in the corner; etc.

alternatively, you could just make vtfs with the numbers, keeping your hud vtf crosshair while using the default crosshairs for your weapons, and crop it in such a manner that it is off-center on your screen so you can still see your hud crosshair, but whatever floats ur boat...

although this would take a little bit of time, you'd be able to see which slot you have engaged without needing to toggle viewmodels nor needing to utilize any fancy scripts that have volatile state storage which couldn't read from the game's memory anyway.

(or you could just look at your ammo count lolz)

also, i'm not entirely sure if it's possible to incorporate the dead ringer into this issue, as i never play spy so i've never cared enough, but i'll look into it when i wake up. more than anything, i could see this concept being useful for spies that don't like viewmodels & want to avoid script bullshit.

i used to overlay a bunch of different hud crosshairs over one another, so they weren't necessarily meant for this strategy & some may be lower resolution than recommended. APOLOGIES.

but yeah, definitely agree with you. white crosshairs would be the way to go if you want to use singularly colored/outlined crosshairs. but if you want more complex colors or if you want to gamma-shift something that looks complicated, like in the included ExcaliburRainbow, then VTF crosshairs still give you the flexibility to do so by manually coloring them.

just make it blank
cl_crosshair_file ""

they will rue the day...

With the advent of weapon script editing to modify projectile explosions and sounds, I've theorized that it was possible to change the crosshairs of weapons. Sure enough, it's an easy step up from HUD-based VTF crosshairs, and it expands the customization options of VTF crosshairs dramatically since the scripts reference a splicing utility that lets you crop multiple crosshairs from one VTF file.

NOTE: This will only work in sv_pure 2 if you place your .vmt and .vtf files in folders that aren't cross-referenced with the default folders for validation, such as materials/vgui/replay/thumbnails.

The optimal format I've found for VTF's is:
Format: RGBA8888
Size: 32x32 and up

Necessary checked VTF flags for color preservation:
No Mipmap
No Level Of Detail
No Minimum Mipmap
Eight Bit Alpha (Format Specific)

Optional checked VTF flags:
SRGB (try it if the color quality is low for some reason)
Point Sample (thanks to JarateKing for the explanation -- "makes resizing pixelated rather than blurry")

The rest of the flags should remain unchecked.

Step 1. Place your .vmt and .vtf in materials/vgui/replay/thumbnails. Make sure your vmt references your vtf.

Step 2. In your weapon script (for example, tf_weapon_scattergun.txt), point your desired crosshair file like so:

"crosshair"
{
      "file"	"vgui/replay/thumbnails/DESIRED_VMT_NAME_HERE"
      "x"	"0"
      "y"	"0"
      "width"	"MAX_WIDTH_OF_VTF_FILE"
      "height"	"MAX_HEIGHT_OF_VTF_FILE"
}

If you aren't cropping a specific portion of your crosshair, just specify your "x" and "y" as 0, and your "width" and "height" as the sizes of the vtf (the width and height of your vtf should be scaled by powers of 2).

If you want to jam-pack a bunch of crosshairs in one vtf file, then it's relatively easy to figure out. Just look at the sprites/crosshairs file in the "tf2_textures_dir" vpk and work back from there.

For instance, everyone knows about the sniper/spy crosshair being off-centered. If you lower the "y" value of the sniper rifle script file's crosshair to -1, you can fix this. In fact, you can modify the position, width, and height to be spliced from the default crosshairs without needing to worry about sv_pure.

Example: If you like the default crosshair for the scattergun but don't like the default crosshair for the pistol, just copy over the "x", "y", "width", and "height" values from the scattergun script to the pistol script while referencing the sprites/crosshairs file.

The "x" and "y" specify the location on the vtf file to begin cropping from. The "width" and "height" specify the boundaries from that location.

Step 3. Load the game, set your crosshair type to "none", and enjoy your custom VTF crosshair. You can resize & recolor it in game without preloading or editing resource files & calling hud_reloadscheme.

The biggest benefit overall from doing this over using a typical HUD vtf crosshair (or, god forbid, a text-based crosshair) is that it is resolution independent. If the VTF is centered (or if you crop the VTF in such a manner that it will be centered), then your crosshair will be centered in-game, period.

I've linked my custom folder below.
Feel free to use the crosshairs in the flamehud-master\materials\vgui\replay\thumbnails folder (FULL CREDIT TO WATSON FOR ALL THE PRETTY CROSSHAIRS), and feel free to modify my weapon scripts in the scripts folder to your liking. Note that I've removed tracers on most of the hitscan weapons by pointing their particle materials to null and changed a bunch of hud elements for increased visibility, so if you don't like that, then just use it as a basis to modify your own script files.

Not all of my VTF files have the proper flags set. Go ahead and tweak those if you want to use anything but GreenDotBlackOutlineGreenCircle (the best crosshair in the universe...)

I don't have the scripts for every single weapon in the game (I only use stock anyway), and the only one I've modified to include a custom crosshair is the scattergun script. Again, please reference the "no explosion effect" threads to figure out how to extract more scripts.

https://www.dropbox.com/s/bbaig6g9d654z80/custom.zip?dl=0

also plz dont let truetf2 know about this they are bigots and baned me so they deserve 2 die..

p.s. i'm not going to draw or clean up your favorite crosshair from a random picture or frag video (just trace an image of it; it's just fucking pixel art lol). however, feel free to post your vtf's here to either share or get help with (but please put in a modicum of effort before you do so).

update:

i knew it
u were the one who gave me stomach flu

fuk u..

looks like the same interface that they shell out to centurylink customers for their dsl plan
even if not, zyxel & low-end actiontec routers have really shitty NVRAM and CPU speeds.
you could be filling up the NAT table or choking your connection from your slow CPU.

the main reason i'm necroing this is because, after being so fucking frustrated with my parents' satellite connection every time i visit them, i finally figured out a very accessible & extremely effective QoS solution using an ASUS RT-N16.

get the ASUSWRT-Merlin firmware revision 378.50 with an ASUS RT-N16
pretty much the most accessible & affordable QoS package that finally stops my packets from being dropped
although it doesn't utilize codel, it doesn't suffer from bufferbloat & requires minimal customization (if you want to go deeper, you can use layer7 rules in iptables, which the firmware's readme provides documentation for)
good inherent UDP and TCP timings are probably working alongside this.

the only disadvantage is that the RT-N16 is graded for 100 mbit networks, but it seems that your connection more than happily meets that mark. its wifi isn't top-notch either, if that's a big issue to you (weak coverage & wall penetration).