The SDK doesn't work in its current state and Valve isn't ever going to "fix" it. They've openly stated that the programs in the /bin/ folders are the real SDK now. If they could be arsed, they'd probably have removed it from Steam altogether by now.
Why, you fire up your debugger, load the debugging symbols (that you don't get) and load the dump to figure out what caused the crash.
It is partly the filesystem issue and partly engine differences. The SDK tool is coded for GCFs, not VPKs, so that's why it doesn't work for any of the steampipe (i.e. VPK) games. I also have a feeling they won't be updating it because of the varied engines. The tool already had three engine options for the games it supported, and stuff like L4D and AS had their own SDK tools long ago because of the engine differences. That incremental changes approach to Source progress is probably why they are inclined to go with a bin folder included with each game.What the actual fuck? Is there a thread explaining why this is?
Hopefully they're just getting lazy because Ep3 is coming soon and will make many things redundant.
Were you serious about this
Because what I tried so far is completely reinstall TF2 but Hammer still crashes instantly on load
Not for long, though. Half-Life Source and Half-Life Deathmatch: Source have SteamPipe/Mac+Linux betas as of a few days ago, and I think they were the last holdouts.I also could be mistaken, but I believe there are still games that use the GCF format, so the tool isn't broken per se. It still works for what it can work for.
Apparently my FrankenHUD in tf's custom folder made hammer instantly crash... (??) But you were right, thanksare all your config folders empty
what can tf2 be modifying that hammer isnt
its the only question