Angua on e1m2, dag on dm6, mutilator on dm4, reppie on aero. All wonderful sights in QW that no other quake game can match :(

Which files should I look at for editing the health bars and outlines of my teammates (the ones I see when I'm dead and shortly after respawning)?

https://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking#Optimizations

interpolation period = max(cl_interp, cl_interp_ratio / cl_updaterate)

So check your interp_ratio and updaterate. Sounds like your updaterate is set to something strange.

Those stop errors are all pretty much caused by a faulty driver or new hardware with faulty drivers. Did you change drivers or install new hardware recently?

http://www.techrepublic.com/blog/windows-and-office/how-do-i-use-windbg-debugger-to-troubleshoot-a-blue-screen-of-death/

https://support.microsoft.com/en-us/kb/315263

Make sure you have minidump files enabled and next time your PC BSODs, follow the steps here to check the minidump file with dumpchk or windbg. It'll tell you "probably caused by <driver name>". It may point to a kernel driver but that's because another driver corrupted something in memory that the kernel driver stepped on. Based on the varied stop codes you've received, you'll probably get the problematic driver after a couple of crashes.

EDIT: I'm retarded. Forgot +mlook was removed years ago

Check sensitivity, m_yaw, m_pitch in console.

I'm a HL engineer main subbing for this match I have no idea what I'm doing please don't cast.

] find m_customaccel
"m_customaccel" = "0"
 client archive
 - Custom mouse acceleration:
0: custom accelaration disabled
1: mouse_acceleration = min(m_customaccel_max, pow(raw_mouse_delta, m_customaccel_exponent) * m_customaccel_scale + sensitivity)
2: Same as 1, with but x and y sensitivity are scaled by m_pitch and m_yaw respectively.
3: mouse_acceleration = pow(raw_mouse_delta, m_customaccel_exponent - 1) * sensitivity
"m_customaccel_scale" = "0.04" min. 0.000000
 client archive
 - Custom mouse acceleration value.
"m_customaccel_max" = "0"
 client archive
 - Max mouse move scale factor, 0 for no limit
"m_customaccel_exponent" = "1" min. 1.000000
 client archive
 - Mouse move is raised to this power before being scaled by scale factor.

So unless there's a bug with the parameters or the console documentation is wrong, then m_customaccel_scale, m_customaccel_max, and m_customaccel_exponent do nothing with m_customaccel 0.

s c i z o r

Same issue here. I filed a support ticket already with my details.

EDIT: I did not accept the trade offer because I figured that would have made it more difficult for the saloon admins to fix this.

Lunacide wouldn't have let that happen

Ban the lochnload and beggars.

Go Spamfest!

Also ffs Kresnik missed everything on the soldier who jumped behind us on the midfight. You can see the healthbar remain the same.

He saw axio lower right before he started shooting at banny. Axio wears some bright unusuals.

And our spy was right above axio and called axio there.

Regarding https://www.youtube.com/watch?v=9-aS-1WwFik

@ 1:35ish -- Aside from the fact he shot at the scout when the sniper was about to peak him (oh the irony), he saw the scout go right. He already knew the heavy was there. He was peaking right because there are people right.

@ 1:55ish -- Look in the kill feed. Podgy destroyed a sentry and was probably called. Of course boar is going to scope there because podgy isn't going to rotate onto the cart to shoot him (boar already stepped back to avoid that sightline in case podgy did rotate there).

@ 2:08ish-- Look in the kill feed. Podgy killed red heavy. Red heavy most likely commed "sniper main spawn, left side."