Error: The System can not find the file specified

Ctrl Alt Defeat

L1: Registered
Jun 10, 2014
31
5
I've made several maps before, just not in TF2. I made around 3 or 4 TTT maps for Garry's Mod, the most recent being several months ago and a very complex and semi-well received one. I took a small hiatus from mapping, but now I want to get into making TF2 maps. I plan to make a KOTH map as my first, as they seem to be the simplest. I've read a few pages about Spawn Rooms and such, but I'm not able to test my map. When I go to to run Map, I set VIS to Fast and BSP and RAD to Normal, but as it compiles, it says it's unable to find the file.

I delved into the options to see what was wrong, and I'm not sure what the problem is.

Game Executable Directory: $SteamUserDir\Team Fortress 2

Game Directory: $SteamUserDir\Team Fortress 2\tf

Hammer VMF Directory: $SteamUserDir\sourcesdk_content\tf\mapsrc

I'm fairly certain the problem is in the 3rd one. I tried changing it to the tf\maps, but that didn't solve it, so I set it back to what I believe was the default, as shown above. What do I do? Hammer has had a reputation of being an ass with me and several of my mapper friends, but it's usually at least opened the map.

(To be fair, Source SDK didn't work, I had to go into the Team Fortress 2 Directories to hind hammer.exe, but I digress)
 

xzzy

aa
Jan 30, 2010
815
531
If you're running Hammer out of your tf2 directory, don't click the exe. There's a hammer.bat in there you use instead.

You may want to uninstall the source sdk because it sets some environment variables that can interfere with running Hammer from the tf2 dir, but I know other people leave the sdk installed and have no problems at all.

You can also go into the control panel and delete the VPROJECT environment variable.
 

Ctrl Alt Defeat

L1: Registered
Jun 10, 2014
31
5
Nevermind, I fixed it. I had a white, 8-sided spike (supposed to be a dunce cap decor) that literally made it not work.

Also, the .bat doesn't work, while the .exe does. The .bat opens something in command prompt for about a third of a second then closes it.
 
Last edited: