Skip to content
Modification of Source Valve Hammer Editor to fix some issues. Fixes brush vertex precision loss.
C++
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Images
Open Source Licenses
Output
Projects
Property Sheet Add MinHook as NuGet package Oct 14, 2017
.gitattributes
.gitignore
ReadMe.md

ReadMe.md

HammerPatch

The program can be downloaded here. Visit here if you wish to support the development.

Installing

Both HammerPatch.dll and HammerPatchLauncher.exe should go in the same directory as hammer.exe. This will be in the bin directory of each Source game. Examples:

  • steamapps\common\Counter-Strike Source\bin\
  • steamapps\common\Half-Life 2\bin\

Instead of using hammer.exe to start, you should now use HammerPatchLauncher.exe.

This will not magically fix existing corrupted brushes, it will only have a change on new brushes that were saved with this.

Now when you save a map with HammerPatch loaded, it will create additional files next to the VMF. The .hpverts file contains the vertex data in binary form and the .hpvertstext contains a human readable representation. Only the binary file is used by the program.

Vertices moving on load

In default Hammer, unless your geometry is of perfectly straight angles, the vertices will move every time you open the map. This is because the vertices' positions are recalculated every time from plane points. This is a lossy process and will only get worse every time the map is loaded.

In HammerPatch, all vertices are saved separately and are restored on load to overwrite Hammer's estimations. Here are some images that illustrate this problem.

Figure 1

Say you have a simple default primitive. This is a cylinder with 32 sides.

Shape 1

Figure 2

In default Hammer, this is what you'd see if you zoom in on such primitive after loading a map of one iteration.

Shape 1 zoom default

Figure 3

Here's the same shape but when saved and loaded with HammerPatch. It is the exact same vertices as it was created with.

Shape 1 zoom HammerPatch

Figure 4

This problem gets more problematic on advanced shapes.

Shape 2

Figure 5

Again, this is what it looks like in default Hammer after one save iteration.

Shape 2 zoom default

Figure 6

The same map as saved and loaded by HammerPatch.

Shape 2 zoom HammerPatch

You can’t perform that action at this time.