Valve Hammer Adding Custom Models

Drewpew

L1: Registered
Jul 15, 2015
3
0
Hello,

I am attempting to make a WW2 themed tf2 map, and I would like to have some tanks and other props to put in the map. However, I am unable to locate the folder in which the tank model will go. A lot of old posts have a folder called USERNAME, but that folder doesn't seem to exist in the steamapps folder any longer. Within Hammer, it shows the file path being steam/steamapps/common/team fortress 2/tf/models, but the models folder doesn't exist!

Please help me, thank you.
 
Last edited:

worMatty

Repacking Evangelist
aa
Jul 22, 2014
1,257
999
Hi, Drewpew. Welcome to TF2m.

Custom models and materials should go in tf/custom/<anything>/models and tf/custom/<anything>/materials. You can replace anything with whatever you like. Anything that exists within a folder inside the custom dir is mounted in Hammer and TF2 as living in tf. The custom dir helps you keep your special stuff separate. You can have multiple folders inside custom with that goal in mind. So for example you could have one folder for your WW2 assets, one folder for your own custom assets, and so on.

Bear in mind that models typically live inside a folder within models/. For example, models/props_gameplay/. If your tank comes in a ZIP file, you should be careful to preserve the directory structure when you copy things.
 
Last edited:

killohurtz

Distinction in Applied Carving
aa
Feb 22, 2014
1,016
1,277
You can actually create the "models" and "materials" folders in /tf yourself if they don't exist. The game doesn't store any base assets in those folders, so you are free to use them for your own custom content. You also have the option to put your things in the Custom folder like Matty said, but make sure Hammer is configured to read whichever directory you choose.
 

tyler

aa
Sep 11, 2013
5,102
4,621
Before the Steam Pipe update (when TF2 moved from GCF storage to VPK storage like all newer Source games), everything lived in a user-specified folder like you've seen. But now, everything has moved to the common folder. Your path to the /tf folder should be something like C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\tf assuming you have Steam on the C drive.

Usually when you download models the assets come in two folders, models and materials. Just put them where Matty said or in the main tf directory.
 

Tumby

aa
May 12, 2013
1,084
1,192
IMO the custom folder should only be used to replace existing content for your own entertainment. A few packing programs won't recognize things inside this folder anyways.
Also, whats the point in keeping your stuff seperate when it's already being kept seperate? Things like props_gameplay, props_coalmines, nature, and so on exist for a reason.
 

Drewpew

L1: Registered
Jul 15, 2015
3
0
Thanks to everyone for the quick and helpful replies.

I unfortunately can't test them right now, because I'm actually making the map with a friend, and he has the pc (I'm using a mac, which doesn't support Hammer :/). However, that sounds like it will work. Thanks a ton.

Btw, in my original message, I mistyped the path, I really meant: steam/steamapps/common/team fortress 2/tf/models

I'll edit my post accordingly.

And again, thanks a lot for the quick replies. My friend and I were really starting to get annoyed! :p
 

worMatty

Repacking Evangelist
aa
Jul 22, 2014
1,257
999
No worries, Drewpew.

VIDE, Pakrat and CompilePal each pick up stuff in custom. The former two, if you point them there. The latter, without any configuration.

The benefit of keeping your custom stuff in separate folders inside custom is modularity. You can remove or disable any group of assets you like by deleting or temporarily moving each folder out. I have folders in custom for the mapping assets I have made myself that I distribute with my maps, for my experiments with replacement voice lines, for third-party assets like the TF2maps Construction Pack, the ABS resource pack, and places for work by friends and other folks. I don't have to go fishing around and deleting things bit by bit, and I can be sure I know where I got something from so I give credit.