/r/wtf is that way --->

I recently sent off an e-mail to the TF2 Team explaining the steps to re-produce the bug, and I thought it would be a good idea to let everyone else know about how to reproduce it. It's really quite simple.

1) Be in Spectate Mode (whether dead, spectating in game, or in SourceTV it doesn't matter)

2) Spectate a person who is either a) respawning b) switching classes c) switching loadouts IN FIRST-PERSON VIEW (VERY IMPORTANT THAT IT'S FIRST PERSON VIEW)

Then when you change the POV to either another person, third person, free-camera, or just respawn if you're in game and dead, the player will be invisible to you, but will still show any cosmetic items the player is wearing.

Now, avoiding this bug is more practical when spectating or in SourceTV, but is also possible while playing the game. There are a few things that you can do to avoid this bug.

1) Never spectate a player who is about to respawn or change classes in first person view. If you are spectating someone and are about to change classes, switch to another POV (third-person or another player entirely).

2) Record a demo. This can be done in one single line with "record 1; stop". If you're recording a POV demo, you'll have to stop your demo recording first then record another demo with "stop; record 1; stop" or wait for the player to die, as it fixes itself upon death (as long as you don't trigger the bug again).

Hopefully this helps casters and players alike who want to try to avoid this bug.

I sent a email to valve explaining how to reproduce the bug (spectate a person who spawns). Hopefully they can figure out the issue from that.

Try downgrading to 306.xx or something along those lines for video card drivers.

I almost got myself caught in a loop with those annotations at the end of the video

I was able to circumvent this issue entirely by parsing out the lines with IP addresses within the tf2.pug.na bot before uploading the logs to our stats site. If you use an IRC bot for uploading logs from servers, add me on steam and I'll give you the code for it (It's written in ruby but should still give an idea of what to do)

Computer Programming Student working part time flipping burgers at Wendy's, writing for ESEANews, and all of my TF2 community shit (I swear it's full time with no pay)

SteamPipe update incoming?

I'll be bringing out the IM predictions tonight on ESEANews

Oh no you didn't!

http://www.youtube.com/watch?v=cBRhCMvbRmk

might as well post it here too

Fog quick question
dy-dx yes
Fog would it be possible to host the log parser on your own servers?
dy-dx there is no log parser
dy-dx there are no logs
Fog oh what
Fog head asplod

Oh, I'll update the list when I get home

There's a server plugin that does it via sourcemod called matchrecorder

https://forums.alliedmods.net/showthread.php?t=92716

Nothing that I know about for client side STV recording

Would there be any noticable difference between a 120hz monitor (like the VG248QE) and a 85hz 17" CRT (SyncMaster 763mb)?