Brush: Difference between revisions
Jump to navigation
Jump to search
Confirm:However, nodraw faces do not.
Tip:It is possible to compile a custom build of VBSP with these limits changed or removed, but who knows how the engine would respond?
TomEdwards (talk | contribs) (link to w:CSG) |
TomEdwards (talk | contribs) |
||
Line 18: | Line 18: | ||
# For each individual brush model, only faces that touch a visleaf are compiled. Some of the results of this process can be seen below:<p>[[File:Brushes compiled.png|750px|Brushes and their compiled equivalents]]</p> | # For each individual brush model, only faces that touch a visleaf are compiled. Some of the results of this process can be seen below:<p>[[File:Brushes compiled.png|750px|Brushes and their compiled equivalents]]</p> | ||
# If some parts of a brush face | # If some parts of a brush face touch visleaves and others do not, the face will be chopped up accordingly. | ||
There are two exceptions to these rules: | There are two exceptions to these rules: | ||
* Although | * Although they are discrete entities in Hammer, [[func_detail]]s are all merged into one during compile. You do not need to [[nodraw]] hidden 'detail-to-detail' faces (but you ''do'' need to nodraw world-to-detail and detail-to-world). | ||
* Faces with [[$translucent|translucent]] materials applied are never chopped. Don't apply them to internal or hidden surfaces unless you really mean to. | * Faces with [[$translucent|translucent]] materials applied are never chopped. Don't apply them to internal or hidden surfaces unless you really mean to. | ||
Revision as of 06:00, 14 April 2010
A brush is a convex 3D shape created with Hammer's Block Tool. Brushes are used by level designers define the shape of the world (which defines visibility) and to create brush entities.
When a map is compiled VBSP converts brush faces that touch a visleaf to groups of polygons. The resulting 'brush models' are stored within the BSP file and can be claimed by entities (e.g. the world, or your brush entity). The original brushes are retained in the BSP, though the benefits of this are not clear.
In comparison to models, brushes are:
Compilation
- For each individual brush model, only faces that touch a visleaf are compiled. Some of the results of this process can be seen below:
- If some parts of a brush face touch visleaves and others do not, the face will be chopped up accordingly.
There are two exceptions to these rules:
- Although they are discrete entities in Hammer, func_details are all merged into one during compile. You do not need to nodraw hidden 'detail-to-detail' faces (but you do need to nodraw world-to-detail and detail-to-world).
- Faces with translucent materials applied are never chopped. Don't apply them to internal or hidden surfaces unless you really mean to.
Limits
VBSP enforces these limits:
- 8192 brushes
- 128 faces on a single brush
- 65536 faces overall
Invisible brushes like triggers and even hint brushes count toward the limit.

