highfive you shoulda sucked her dick to show them

Here is the pixel by pixel difference of bronze and participant: http://i.imgur.com/0PQbl56.png
If it's black, that means the images were the same there. There's a tiny bit of shine, and (possibly because of the shine) there's a difference of <10 in each RGB channel for the medal itself, like comanglia found, but it's really not enough to actually notice. The ribbons are the exact same.

For reference, here's gold and silver's difference: http://i.imgur.com/OOk9gEG.png
Just to show what two different images would look like compared.

They're pretty much impossible to tell the difference except for the little bit of extra shine.

Some mice more than others for sure (it's why stripping a WMO's cable is such a popular mod while nearly unheardof for most other mice, and is why braided cables are generally considered a bad thing), but mouse drag caused by cable stiffness and friction is a very real thing, unless you've got a lubed paracord cable or something. Some mice even have the design flaw where the cable points downwards from the mouse, and will drag immediately. The stitched ends on mousepads can start to fray and start catching your mouse cable too (mostly if it's a braided cable, but still). This is also why playing with wires everywhere in front of your mouse is absolute aids (though the best fix for this is to clean your desk).

A mouse bungee is a $5 solution to at least the issue of friction, and stiffness is less of an issue when the cable's in the air out of personal experience. DIY can make it cheaper too. Mouse bungees aren't as important as actually good peripherals and mousepads, but they also come cheap enough that it's not really a worry if they only slightly make things more comfortable and consistent. It does alter the feel pretty significantly and is all down to preference at the end of the day, but again, it's cheap as fuck to try out.

iirc Rhapsody's became equal to Comanglia's in terms of raw performance pretty quickly, but Comanglia's got recommended more because it's a lot simpler to install (and not have to fiddle with the file itself).

It's not unused, from what I've seen it looks like the most popular alternative to Chris's and Comanglia's, but it's not as standard.

There isn't really a resource for it. Mannterface was the first public example (colly and I both did it with the actual player's health before, I might still have the picture I used to explain it to Mannterface's maker somewhere...). It's basically just manipulating the bonus healthcross (the one that normally appears when you're at low health or have overheal) to always appear, and to fit within the bounds of your panel exactly. That way at max health, it covers the full panel, at half it covers half, and at 0 it's completely off-screen / out-of-bounds / has 0 width.

Pretty much just look at spectatortournament.res, note its health's size and HealthBonusPosAdj and HealthDeathWarning, and check out spectatortournamentguihealth.res's PlayerStatusHealthBonusImage's position. Those should be all you need, though the posadj and the image's position would need changes depending on your panel size.

I'm guessing it's a twitch error, I'm experiencing it too but it's random if it stays working.

There's a big difference between proper medication for diagnosed medical issues, and getting high or drunk because you feel like it. Not all drugs are addictive and not all put you at serious risk for permanent damage, but plenty do on both, and even just their habits can be an issue in daily life. And either way, feeling like they're a problem and wanting to quit/cut back is completely valid.

Like seriously, if the dude's concerned about getting high / drinking too much, you should know that saying "yeah but how much is too much? it probably won't kill you so just do even more lmao" isn't the right response.

Edit the script that turns on netgraph, somewhere in your cfg's. It would depend on what script you're using exactly and where you put it in your cfg's, but the process would be the same and you just need to edit it to set net_graph 1 instead of 2.

It's a tried and true archetype. It's so common because it looks good, it's what people want out of huds. And unless something else comes along and does a really good job doing something else (hudas iscariot and maybe medhud, mostly), huds that don't do similar get ignored pretty quickly. In no order, things like; metrohud, BazHUD, BelleHUD, edisHUD, solanoHUD, origamiHUD, are all some examples of huds that did try to do things differently (and whether or not they looked good, they never really became notable, other than for saying "yeah this idea was already tried and no one cared"). There are definitely more that I'm forgetting too, these are just the ones that come to mind.

Though I really gotta disagree on them all looking the same. Yahud looks nothing like m0rehud black looks nothing like ell's hud looks nothing like flamehud looks nothing like material hud looks nothing like wiethud. The health and ammo numbers alone, you do have a lot of choice when it comes to how you want to deal with them, and they can have a pretty significant impact on the overall feel of the hud. And I mean that's also, usually, the most similar part about huds.

None less different than rayshud is at least.

Yeah, the hud was largely an experiment testing-grounds for a lot of my hud ideas. Some were more trouble than they were worth (and were almost more proof of concepts than anything), but for others I really wish other hud editors could also look into and hopefully end up with a more seamless implementation. Hell, some, like chat_english editing, are just such good goodies that I'm surprised no one else has even taken a good look at them.

I'm on linux right now where font sizes are really screwed up compared to windows, so I can't really work on it myself to update and fix bugs.

65%: (general category for not-quite-60% layouts)

60% (usually pretty standard layouts of no numpad, nav cluster, or function row)

40% (these are all enthusiast-made stuff, so good quality custom built / DIY things)

Of note:

I don't know how many of these are available in nordic exactly, but that doesn't really matter much since nordic is like any other ISO in terms of key positions. The keycap labels might be wrong if you got ISO-UK or something, but changing it to be nordic in your OS would work fine. And for that matter 60% is where you start getting changes to the layout but huge programmability / layering powers, so the need to ISO breaks down a bit anyway.

e: had to spoiler this thing up because it was massive

Clean TF2's _prop_removal.vpk will do this, though it removes more props than just foliage.

Fullscreen = drawn directly to screen = less resources used and nothing forced on the game
Windowed Borderless = Using desktop window manager = slightly more resources used and forces triple-buffering

Like anything fps related, how much difference in frames will depend on your setup. I don't know the details of triple-buffering in windows, but it will result in input lag at the very least, and possibly decreased fps and stability depending on the specifics.

FPS affecting input lag should be pretty obvious, better fps = less room for input lag. If you ran at 60 fps and had your mouse or keyboard running at 125hz, your maximum input lag would be ~25ms ((1/60 + 1/125) * 1000) and your minimum would be the one with bigger latency (so 1/60*1000, or ~17ms), with no other factors involved. At 240 fps with 125hz, that max goes down to ~12ms with a minimum of 8ms (from the 125hz).

I know this is pretty specific, but I can't find it anywhere. Can anyone with a beta key try running it under wine to see if it works on linux? Doom can be made to work, so I bet QC could too, but I don't want to waste a beta key from someone else incase it doesn't.

How fast your mouse sensor can go before it starts malfunctioning (as in starts having negative accel). Often called the malfunction speed. Can also be used to refer to max acceleration, since they both cause malfunctions.

For example, the Pixart 3360/61/66 sensor has 250ips (inches per second) and 50g (g-force acceleration) as its max tracking speed. Anything past that and it will malfunction.

Some other popular sensors are:
Pixart 3310: 130ips/30g
Avago ADNS 3090: 60ips/20g
MLT04 overclocked: 60ips (I can't find its max accel)

400 DPI 0.992848985 ingame (41.4 inch/360, 105.9 cm/360)
zoom_sensitivity_ratio 0.793471413188092380619906740908785437547348780566443970924
Tried to map mouse distance 1:1 with my screen, but perspective and fov doesn't really work like that.

But to still rocketjump and look around fast I need to use

alias +incsens "multvar sensitivity 0 10000 4"
alias -incsens "multvar sensitivity 0 10000 0.25"
bind mouse4 +incsens