hammer.exe crashing immediately

seth

aa
May 31, 2013
1,019
851
So I used to launch Hammer from the Source SDK, but I kept getting a "failed to load default scheme" error, and tried to launch from the TF2 bin folder. It crashes immediately from there. Won't even launch, which SDK at least would do. I've tried deleting the gameinfo and gameconfig files and having the hammer.bat regenerate them as well as verifying the integrity of the game cache, but nothing works.

Help?
 

Dev

L1: Registered
Jan 9, 2014
8
4
You have to run hammer.bat? I never once did that. Does it run by itself sometimes? :p
 

Freyja

aa
Jul 31, 2009
2,994
5,813
My apologies, I completely missed that somehow.

The only advice I could offer is trying to update the ABS resource pack, I think it edits the scheme file? That may help
 

seth

aa
May 31, 2013
1,019
851
My apologies, I completely missed that somehow.

The only advice I could offer is trying to update the ABS resource pack, I think it edits the scheme file? That may help

Running hammer.exe as an administrator actually fixed the problem. Weirdest thing ever. Just right clicked and hit "Run as administrator" and it works perfectly. And I only had to do it once for some reason. Shortcut it to my desktop and don't even have to run it as the administrator anymore... really weird.
 

Fruity Snacks

Creator of blackholes & memes. Destroyer of forums
aa
Sep 5, 2010
6,394
5,571
My apologies, I completely missed that somehow.

The only advice I could offer is trying to update the ABS resource pack, I think it edits the scheme file? That may help

Or, if you don't have it installed, install it and that might help too.
 

Pocket

Half a Lambert is better than one.
aa
Nov 14, 2009
4,694
2,579
Running hammer.exe as an administrator actually fixed the problem. Weirdest thing ever. Just right clicked and hit "Run as administrator" and it works perfectly. And I only had to do it once for some reason. Shortcut it to my desktop and don't even have to run it as the administrator anymore... really weird.
I had a similar thing happen with Photoshop CS2 as well, back when I first started using Vista. It's probably because, like most apps that originated back in the day, it was designed to assume it would always run with admin privileges.
 

seth

aa
May 31, 2013
1,019
851
I had a similar thing happen with Photoshop CS2 as well, back when I first started using Vista. It's probably because, like most apps that originated back in the day, it was designed to assume it would always run with admin privileges.

Well that's still weird it only had to be done once though, I haven't been running it as the administrator since then.
 

grazr

Old Man Mutant Ninja Turtle
aa
Mar 4, 2008
5,441
3,814
Probably because once you run it as administrator, the files that were required to be edited (and the permission to do so) stay edited.

That's usually what the permission is for. To allow files to be modified.
 

seth

aa
May 31, 2013
1,019
851
Probably because once you run it as administrator, the files that were required to be edited (and the permission to do so) stay edited.

That's usually what the permission is for. To allow files to be modified.

Gotcha, thanks!