Releases · theanine3D/source-engine-collision-tools

16 May 04:52

a7d1a84

v1.3 Latest

Latest

Added a new QC override system that allows the user to customize the resulting generated QC files, with custom QC commands (such as $scale, $surfaceprop, etc.) You can add overrides to your split-up collision objects in Blender via Custom Properties. Any string-based Custom Property that has a name starting with "$" will be treated as a QC override.

Because Blender doesn't have a built-in way in its UI to copy or add Custom Properties to multiple objects at the same time, the addon also now has a "Copy QC Overrides" button which will let you copy all of the QC overrides from the current active object to all other selected objects. There is also a "Clear QC Overrides" button if you want to clear them all out for all currently selected objects.

Custom Properties for $scale, $opaque, and $surfaceprop (added via the Object Properties panel)

When exported, the overrides are added to the QC. Certain commands like $scale and $surfaceprop are added near the top, while the rest will be added at the bottom of the file.

Another major update in v1.3 is that most of the addon's operators now have multi-object support. You can generate collision for all selected mesh objects now, and cleanup tools like Force Convex will also work on all selected mesh objects. However, the Recommended Settings button still only supports the current active object. Keep that in mind when you use it while multiple objects are selected. If you get poorly generated collision, it might be because the wrong "recommended" settings were being applied. Because of this, generating collision for a single object at a time is still the recommended method.

Assets 3

13 May 06:02

theanine3D

1.2

093d8c1

v1.2

This release has two new features along with some bugfixes:

New features

Post-Merge - a new toggle button that causes the resulting coillision mesh to have one more "merge" operation run on it at the very end, resulting in drastically reduced collision hull counts. This is ideal for smaller individual props. Do not use it for rooms, scenes, and basically any object with an interior cavity that the player should be able to enter. It doesn't work for those because the floor, ceiling, and walls all get merged into one single hull.
Dissolve - another toggle setting that lets you choose between optimization vs. accuracy. If enabled (which is the default. recommended setting), the Generate Collision Mesh operator will dissolve triangles into quads wherever possible, resulting in many less hulls being generated at the end. However, this dissolving can result in loss of accuracy, so if you prefer an extemely accurate collision mesh (even if it's less optimized), you can disable this.

Bugfixes:

Fixed a bug in the Update VMF operator that was preventing partitioned collison meshes (ie. "part_000") from being added to a VMF if they had any upper case letters in their name.
Fixed a bug that was occurring when the Generate Fractured Collision operator was used on an existing collision mesh (with _phys in its name). The resulting collision mesh (based on another collision mesh) was being linked to 2 separate collections, which was incorrect behavior. Now the resulting new (fractured) collision mesh is linked only to the correct single collection bearing its name.

Assets 3

31 Jan 04:40

theanine3D

1.1

451b1d7

v1.1

This is a major update that changes the file/folder structure of the addon. It is now installed via a ZIP file instead of the .py file. This was necessary in order to add a dependency (PyVMF), which leads me to the following changes:

An "Export VMF" operator has been added. It allows you to export the currently selected collision mesh to a specified folder as a .VMF file that can be opened in Hammer. This was made possible by the PyVMF module, which is now packed with the addon.
You may customize the Hammer tool texture that is assigned in the converted VMF brushes. By default, it's set to NODRAW.

Note that your collision hulls must be large enough and snapped to grid to not trigger errors after importing into Hammer. The operator will attempt to snap vertices to the grid for you automatically, but Hammer might still complain upon import if your collision model was too complex or too small. For example, I was able to import a complex collision mesh of Suzanne (the Blender monkey) into Hammer successfully without any errors, only after I scaled up my collision mesh of Suzanne by 10 in Blender first.