See that's just you being mad :p

Obstruction VERY RARELY comes into play - the only reason it did here is because he was attempting to advance a base and was prevented from doing so. In *most* cases obstruction is just let go because it doesn't *really* effect anything - examples are like when a bat hits the catcher's mitt, a runner taps a fielder, a batter fails to immediately get out of the way of the catcher who wants to throw, or a first basemen's leg slightly blocks a runner sliding back into first. Had he laid still it'd probably have been alright, especially given that Craig could barely run anyhow especially after sliding into third, getting up, and being hit by the throw from home lol. It looked like he was going to be able to clear him until his legs came up and tripped him - I imagine Middlebrooks assumed Craig was just going to stay at third being as he couldn't really run and didn't appear to have a particularly good slide into third and so he attempted to get up without paying any attention to what was going on. Had he not made any motion that blocked craig, and they still wanted to call obstruction since he was laying directly in the base path, they could have called a "minor" obstruction - which would have just called the ball dead and the umpires would have decided where the runner-batter would end up (first or second).

That particular call is just rare and sad because of how arbitrary it feels, but it was the right one and was made by the third base umpire *not* the home plate umpire who signaled that he deferred to the third base ump. The balls and strikes though - if you wanted to say those were shit I would totally agree lol. The pitching performances were pretty bad tonight in general - nobody pitched like they had any confidence whatsoever (maybe by design), but it's hard to get ahead in the count when the strike zone is less of a square and more of a thin amoeba.

On the bright side for the bosox, it's only 2-1, which is totally surmountable, and the cards basically wrecked their bullpen tonight so the next few nights may be p-rocky lol.

The obstruction call was correct... Intentional or not when he raised his legs it was donezo.

The balls and strikes were pretty goddam questionable + frustrating the whole game. At least the calling there was shit for both teams' pitchers.

I worked in a factory for like the whole time I was in college (excluding in-class semesters, but I went every saturday, and then full time whenever I had a break) and then the year following my graduation.

As a lowly 0 seniority manual laborer, I got 6 sick/personal days, and 1 week of vacation - I could distribute that 1 week of vacation (5 days) however I felt it necessary so long as nobody with more seniority bumped me off - and even then as long as I wasn't a dumpster I could just burn a sick day. So even in that shitty horrible job LAN would have been perfectly viable, especially if I balanced my shifts properly (trade hours to get 4 less hours on the Friday before and so forth).

Would've been perfectly reasonable to do. They didn't pay us enough to go to Cabo :( lol.

gg - don't let the score line fool you, this one was full of excitement and good times http://www.twitch.tv/teamfortresstv/b/473236077

don't forget day one dlc you need to get to planning that right now.

I know the "display marker over target" causes some issues - esp in dx8 - but that's all I've got.

Yeah the last time I used system restore was with Windows ME and it basically soured me on the whole operation for all time lol.

ME - ahhh the times.

All custom configs, launch options, hud, hitsound etc reapplied, everything works as intended.

Ok I believe I've fixed it - i'll start reapplying stuff.

Step 1. Delete C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\download
Step 2. Delete C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\downloadlists
Step 3. delete C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\materials
Step 4. Delete C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\scripts
Step 5. remove all custom cfgs, launch options etc
Step 6. restart computer
Step 7. verify integrity

errors are gone game works as intended

I shy away from system restore because the only time I actually used it was like back in 2001 and it made my problems worse - I take it they've made it not a complete waste of time over the last decade?

I dont think that's a viable option either since I doubt I've ever actually made a restore point lol.

No I'm referring to tf2, literally nothing has changed in regards to tf2 since I played only a few hours ago lol. My video card isn't even really supported anymore so I doubt that it did anything randomly either lol. I also haven't had any windows updates.

My guess is some file is randomly corrupted but I can't figure out which one - nor can steam apparently lol.

I also doubt that it's a driver option since there wasn't an update during the night and my tf2 worked fine only a few hours ago :( lol

Reinstalling tf2 is the nuclear option because it would take me 1-2 days to dl it (very shit download)

I also tried deleting items_game, it did validate and reacquire that file, but the crash persists.

It just loads the main menu (I've got my console set up to immediately display which is how I see the error message in the console) it will function normally for approximately 10 seconds and crash right to desktop with no error message - if I attempt to load a demo or join a server within that 10 seconds it immediately crashes to desktop with no error message.