Source SDK & SteamPipe Quick Fix!

  • If you're asking a question make sure to set the thread type to be a question!

iciz

L2: Junior Member
Mar 17, 2009
84
60
UPDATE: Valve has released the new SDK tools which you can now easily access using the launcher program I've created over here.



Here's a simple method to get the current (non-beta) Source SDK working again since Valve updated the TF2 file system.

Preparations
First make sure you have an unaltered (non-custom, non-beta) version of the Source SDK installed. To insure this is the case select "refresh sdk content" followed by "Reset Game configurations" in the SDK launcher. Also make sure steam cloud support is disabled.

Note: All TF2 game files in your user directory are no longer needed or used with the new tf2 setup and can be deleted to save space. However, make sure you transfer any custom files you want to keep (maps, models, materials, etc.) over to the new TF2 location in the common folder before deleting it!



Step 1
Go to \steam\steamapps\common\Team Fortress 2\tf and open the file there named “gameinfo.txt”. Add “ToolsAppId 211” to line 22 and "Game |gameinfo_path|." and "Game tf" right above line 77. Save and close.

sdk_fix_step01.png


sdk_fix_step02.png


Note: The above step allows the SDK tools to load all needed scheme files and prevents the error message "Failed to load default scheme file. The map views may be missing some visual elements." from appearing when you open or create a new map in Hammer.


Step 2
Open the Source SDK and click “Edit Game Configurations” select “Team Fortress 2” and click “Edit...” Under the directory path replace the user folder (e.g. \username\) with “\common\” and click “OK” and close the SDK.

sdk_fix_step03.png



Step 3
Relaunch the SDK and Open Hammer, click on "Tools > Options" and change the following:
Game Executable Directory = $SteamDir\steamapps\common\team fortress 2
Game Directory = $SteamDir\steamapps\common\team fortress 2\tf
Hammer VMF Directory = place where you store your VMFs important!

sdk_fix_step04.png


Note: If you don't set the VMF Directory to the location of the current VMF you're working on you may get the error message "Cannot find the file specified" when trying to compile it



Step 4
Then go to the "Build Programs" tab and update the following:
Game executable = $SteamDir\steamapps\common\team fortress 2\hl2.exe
Compiled maps directory = $SteamDir\steamapps\common\team fortress 2\tf\maps

sdk_fix_step05.png




I discovered this method after reinstalling Steam and comparing it to my backup. Looks like someone else discovered this method too, but I thought I'd make a more detailed walk through here. Let me know if you have any problems with this method.

Hope it helps someone. :)
 
Last edited:

Izotope

Sourcerer
aa
May 13, 2013
698
764
Works for me :thumbup:

Here's a simple method to get the (current non-beta) Source SDK working again

What's the difference between this method and the use of the beta? (performance)
 

iciz

L2: Junior Member
Mar 17, 2009
84
60
Glad to hear it! No idea if there's any performance difference in the beta. I'd guess it's just redesigned to work with the new file system. But I'll probably stick with this for now since it's supposedly more stable. I don't need Hammer crashing on me any more then it already does!
 
Last edited:

Snowshoe

L2: Junior Member
May 16, 2012
53
125
Thanks! I'm able to compile my map properly again, without all that fullbright and crap. Nice guide. ;)
 

Fragancia

L2: Junior Member
Feb 22, 2013
91
33
Anyone knows why SDK hammer doesn't take more than 50-100k ram?
It really makes everything choppy and I'm unable to use it properly...
If I make hasty movements with my mouse, hammer doesn't respond and crashes
 

Izotope

Sourcerer
aa
May 13, 2013
698
764
Anyone knows why SDK hammer doesn't take more than 50-100k ram?
It really makes everything choppy and I'm unable to use it properly...
If I make hasty movements with my mouse, hammer doesn't respond and crashes

You haven't tried the SDK beta, have you?
 

hooky

L2: Junior Member
Aug 1, 2012
68
27
Getting the same problem, Fragancia. I just use the beta for editing and the standalone for compiling. Works just fine.
 

Toxindude

L3: Member
Aug 2, 2012
103
4
Worked for me :)

Getting the same problem, Fragancia. I just use the beta for editing and the standalone for compiling. Works just fine.

Yeah I plan on using it this way also. The engine is so dumbed down you can't even use it for anything but compiler.
 

compfast

L1: Registered
Apr 25, 2013
18
0
most everything works now, by opting in to the sdk_tools_beta, in tf2 properties, and launching hammer with the hammer.exe in: C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\bin

I do still see the trigger texture, and it crashes alot, but works. :)

Thanks
 

Lolkat

L1: Registered
May 24, 2013
10
1
I get this error when i try to start hammer after doing the steps before that:
MountFilesystem( 443 ) failed:
SteamMountFilesystem(32664,443,0x1db0f598=,0x1db0f488) failed with error 116: Cache needs repair

I have a feeling "Cache needs repair" means something but im no good with error messages so..:O
 

compfast

L1: Registered
Apr 25, 2013
18
0
go to tf2 properties in steam and click local files tab, then click verify integrity of game cache, and it should find the bad file and replace it.
 

Lolkat

L1: Registered
May 24, 2013
10
1
go to tf2 properties in steam and click local files tab, then click verify integrity of game cache, and it should find the bad file and replace it.

Ok, that helped me and i did all the stuff in hammer but when i press new map i get
Failed to load Default scheme file. The map views may be missing some visual elements.
and then hammer crashes
 

compfast

L1: Registered
Apr 25, 2013
18
0
Ok, that helped me and i did all the stuff in hammer but when i press new map i get
Failed to load Default scheme file. The map views may be missing some visual elements.
and then hammer crashes


launch hammer from the hammer.exe in this folder:

C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\bin\hammer.exe

make a shortcut on your desktop ^

don't run it from the sdk launcher anymore. :)
 

compfast

L1: Registered
Apr 25, 2013
18
0
I haven't had any problems running hammer via the .exe and opting out of the beta.

I also run the SDK in the background just to be safe.

I'm still opted IN to the beta, am I suposed to opt OUT now? It crashes alot and is buggiy maybe that's why. :)