Oh no, hammer isn't working from the sdk menu! ...\Steam\SteamApps\common\Team Fortress 2\bin hammer.exe Done.
except that file cant parse tool textures and will invariably tell you that every compile has a leak. nice try though
Small payoff for what inevitably will be fixed soon (ish). Majority of the time if you know what you're doing in Hammer you shouldn't get a leak, and if you do have one it won't be map-breaking.
I haven't done any full compiles yet, but fast compiles are turning out fine and I haven't had any leak issues using that method. I guess I'm just lucky?
...what? is this some new problem now? I mean, it worked for me the couple times I was testing stuff to update my pack. If you aren't using the batch file, that is likely the problem. It sets the required environment variables if they are missing, which would cause the compilers to fail I believe.
I mean I just started using hammer.exe and I haven't had any leaks reported in my map compiles so yeah, but whatever floats your boat I guess.
Yes. I took the GameConfig.txt [new one] from steamapps\common\team fortress 2\bin and replaced it in steamapps\username\sourcesdk\bin\orangebox\bin GameConfig.txt [old one] VBCT works fine after that... credits to bshear for helping me fix it
this broke my hammer if i did it right. i changed my gameconfig.txt in hammer from the first file location you said to the second one.
You can't specify a gameconfig.txt in Hammer, per se, there is no setting for it because it is the file that all the game settings in Hammer are stored in. It is just a text file in the bin folder. What he is saying is replace sourcesdk\bin\orangebox\bin\gameconfig.txt (the file VBCT is looking at, presumably) with the file from common\team fortress 2\bin so that VBCT will be pointed to the correct tools.
Yes, this is correct. I'm assuming since everything is to the new hammer, the old config files won't be touched. So VBCT can use it without having other things broken. I'll reword it because it seems very confusing.
No, I mean it will render sky texture and not understand that the map is sealed, making everything fullbright
Are you still using the SDK beta, Penguin? Before I opt'd out of the sdk beta, I was getting fullbright maps with tool textures visible too. Right click TF2 in Steam, go to Properties, then Beta tab, and make sure it's set to "NONE - Opt out of all beta programs". The SDK and TF2 the game are now combined into one thing...no need to download/install anything other than TF2 itself. Also, make sure to run Hammer.bat which should be in "Steam\steamapps\common\Team Fortress 2\bin\".
I'm using /common/Team Fortress 2/bin/hammer.exe - works just fine for me. Full compiles are flawless.
