|
|
| (22 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| This page will walk you through setting up Hammer++ with Slammin' tools for TF2Classic map development. | | This page will walk you through setting up Hammer++ with our custom tools for TF2 Classified map development. |
| | |
| __TOC__ | | __TOC__ |
| == Setting up Hammer == | | == Step 1: Installing Hammer++ == |
| Go to the [https://ficool2.github.io/HammerPlusPlus-Website/download.html download page for Hammer++], scroll down until you find the "Source SDK 2013 Multiplayer" option and click it. This will download a ZIP file.
| |
| | |
| If you open the ZIP file, you'll find a ''hammerplusplus_2013mpbuildXXXX'' folder, which itself contains a ''bin'' folder. You should merge the ''bin'' folder inside of the ZIP with the ''bin'' folder in your ''Source SDK Base 2013 Multiplayer'' directory that contains hammer.exe. After that's finished, hammerplusplus.exe and hammer.exe should be in the same folder.
| |
| | |
| Open up Hammer++ by double-clicking "hammerplusplus.exe". After it's started, in the main interface, go to '''Tools''' -> '''Options''' -> '''"Game Configurations" tab''' -> Click "Edit" next to the "Configurations" drop-down. Add a new one, titled however you like.
| |
| | |
| Edit this new configuration to point to the TF2C gamedata (the FGD files in the ''tf2classic'' folder), the game executable directory (your Source SDK Base 2013 Multiplayer folder), and the game directory (your ''tf2classic'' folder, containing GameInfo.txt)
| |
| | |
| [[File:Hammer configuration.png|frame|center|Example image showcasing what your configuration should look like]]
| |
|
| |
|
| == Setting up your compilation tools ==
| | # Make sure Team Fortress 2 Classified is installed on Steam. |
| A set of default compilation tools (vbsp, vvis, and vrad) will come with Source SDK Base 2013 Multiplayer, however these are ancient and unmaintained. They have a limited featureset, old defaults, bugs that can cause strange lighting bugs or performance issues, and much slower compiles. Every mapper is recommended to use the Slammin' Source Mapping Tools, which introduce modern features and fixes.
| | # Download the latest [https://ficool2.github.io/HammerPlusPlus-Website/download.html Team Fortress 2 build of Hammer++]. |
| | # Copy the files of the Team Fortress 2 build of H++ into the {{code|steamapps\common\Team Fortress 2 Classified}} folder, as if you were installing it for Live TF2. |
| | # Navigate to the {{code|steamapps\common\Team Fortress 2 Classified\bin\x64}} folder, and run {{code|hammer_tf2c_setup.bat}} (this should be right next to {{code|hammerplusplus.exe}} if you have installed everything correctly). |
| | # Run {{code|hammerplusplus.exe}}. |
|
| |
|
| At time of writing, you can find the latest version of these tools for TF2C at: https://drive.google.com/file/d/1gqmMkHTadUmWBMOqSPSlKRLL1zYvoRsS/view?usp=sharing
| | As of the Steam release (3.0.0) we include new customized versions of the compilers with the game. Older versions of TF2C's VBSP, VRAD, and VVIS are no longer compatible. ficool2's compilers [https://ficool2.github.io/HammerPlusPlus-Website/tools.html (VBSP++/VVIS++/VRAD++)] have a superset of our compiler's functionality, however some features like ambient occlusion may need to be retuned, as VRAD++ takes different parameters than ours. |
|
| |
|
| Like with Hammer++, this is an archive you'll need to open and extract. The entire contents of the 7z file you download should be extracted into your bin folder. This will '''overwrite''' your existing set of compilation tools, including Valve's Hammer (Hammer++ will be untouched).
| | == Step 2: Configuring VRAD == |
|
| |
|
| After extraction, these tools should be used by Hammer++ without further configuration. Refer to the thread for more information on which options you can use with these tools: https://knockout.chat/thread/992
| | When preparing a final compile of your map, you need to make sure that the parameters you're passing to VRAD are supported by our custom build. Some, such as -staticproplighting, are now enabled by default and will produce an error if you include them. The default VRAD settings we use for most official TF2C maps are: |
|
| |
|
| === VRAD options ===
| | {{pre|-final -hdr -softencosine -ao -aoradius 2 -LargeDispSampleRadius -worldtextureshadows -StaticPropIndirectMode 2 -choptexlights}} |
| This is a recommended set of flags for VRAD which will compile LDR and HDR, and enable all optional graphical features. This is also horribly slow, and you shouldn't use this except for your ''final'' map compile, when you're ready to distribute it to others:
| |
| -final -both -ambientocclusion -LargeDispSampleRadius -softencosine -worldtextureshadows -translucentshadows
| |
| [[File:Vrad.gif|frame|center|The SDK2013 VRAD compared to the Slammin' VRAD on ctf_2fort]]
| |
|
| |
|
| | You can add these to your final compile settings in H++ by going to the the "Run Map..."/F9 dialog, click the "Expert..." button in the bottom-left corner of the panel to view your configurations, and add those the parameters to the $light_exe command in your final compile configuration. |
| | |
| [[Category:Guides]] | | [[Category:Guides]] |
