Toggle search
Toggle menu
TF2 Classified Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Setting up Hammer: Difference between revisions

From TF2 Classified Wiki
More actions
← Older editNewer edit →

Admin (talk | contribs)

5 user groups
166 edits
Add example GIF for the VRAD differences
Initial edit to adjust for 2.1.2 compiler changes
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 TF2Classic map development.
__TOC__
__TOC__
== Setting up Hammer ==
== Setting up Hammer ==
Hammer++ is highly recommended. Valve's Hammer will not display materials correctly without using the [https://www.moddb.com/mods/mapbase/downloads/mapbase-multi-tool Mapbase Multi-Tool] to create a shortcut. This section will guide you through installing Hammer++ instead, which does ''not'' require using the Multi-Tool.
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.
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.


Line 13: Line 15:


== Setting up your compilation tools ==
== Setting up your compilation tools ==
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.
A custom set of compile tools is required in order to have proper lighting on your maps, due to the default compilers not supporting custom shaders, and relying on DX8 models. We use the Mapbase VBSP and Slammin' VRAD which fix both of these problems, along with many other bugs: https://cdn.discordapp.com/attachments/164555395082223616/1134165005286260776/tf2c_compilers.zip
 
Like with Hammer++, this is an archive you'll need to open and extract. The entire contents of the ZIP file you download should be extracted into your bin folder. This will add vbsp_tf2c and vrad_tf2c executable files, alongside the regular vbsp and vrad files.


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
After extraction, you will need to configure Hammer++ to use these tools. In the menu bar, click on "Tools" -> "Options..." -> "Build Programs", and adjust the BSP and RAD executable names to add the _tf2c suffix to the binary names. In the end, the paths should end with vbsp_tf2c.exe and vrad_tf2c.exe.


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).
=== Configuring VRAD ===
When you're ready to compile 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 a RAD error if you include them, causing your map to appear fullbright in-game.


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
In the "Run Map..."/F9 dialog, you should click the "Expert..." button in the bottom-left corner of the panel to view your configurations, and adjust the parameters for the $light_exe command in the configuration you use for your final compile to be:
-final -hdr -ambientocclusion -aoscale 0.5 -LargeDispSampleRadius -softencosine -worldtextureshadows -translucentshadows -game $gamedir $path\$file


=== VRAD options ===
Meanwhile, for fast compiles when prototyping your map, you can simply use:
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:
  -fast -ldr -game $gamedir $path\$file
  -final -both -ambientocclusion -LargeDispSampleRadius -softencosine -worldtextureshadows -translucentshadows
[[File:Vrad.gif|frame|center|The SDK2013 VRAD compared to the Slammin' VRAD on ctf_2fort]]


[[Category:Guides]]
[[Category:Guides]]
Retrieved from "https://wiki.tf2classified.com/wiki/Setting_up_Hammer"