Search results

...{code|zhlt_noclip}} can be used to disable generation of clipnodes for any brush entity (including [[func_detail (GoldSrc)|func_detail]] and [[func_group (G ...s]], the {{code|_hulls}} KV can be used to disable clipnodes on real brush entities only (not [[func_detail (GoldSrc)|func_detail]] or [[func_group (GoldSrc)|f

...ree]]; there is a bmodel for [[worldspawn]], as well as bmodels for each [[brush entity]]. ...GoldSrc)|alt=cycler}} can be used to streamline this process, ensuring the entities are defined in the correct order in the compiled BSP.}}}}

{{TabsBar|main=Brush entity rendering properties}} ...be rendering related keyvalues and inputs available only to specific brush entities{{confirm}} and those would be listed on their pages.

...4.1}}, {{idtech2|4.1}}, {{idtech3|4.1}}, and {{idtech4|4.1}}, which stores entities and level geometry in a format which can be understood by the map compilers ...[[entities]], each of which is optionally capable of storing one or more [[brush]]es, {{only|{{idtech3}}{{idtech4}}}} [[#Patch meshes|patch meshes]], and {{

...ield]]s, indicating information about a brush's face (surface flags) and a brush's contents (content flags). The third metadata value is an integer value, t Surface flags on different faces of a brush generally do not need to match. If two or more conflicting flags are assign

.... Some prefixes also affect [[BSP_flags_(Quake_and_GoldSrc)#Contents_types|brush contents]]; mixing contents will result in compile errors. :{{workaround|If the liquid brush doesn't need to move, use an entity that supports the {{code|angles}} KV, s

{{todo|More info; see {{fte|2}} and [[Ericw-tools]] source codes}} Compile with [[ericw-tools]] using {{code|_world_units_per_luxel}} KV in [[worldspawn]] or {{code|-wor

...to account for maximum lightmap size (15x15 luxels, or 240x240 texels). [[ericw-tools]] additionally uses this on surfaces textured with {{code|TRIGGER}}. ...ID; in {{goldsrc|2}}, the {{code|skin}} KV to override the contents of any brush entity that inherits [[CBaseAnimating (GoldSrc)|CBaseAnimating]], but the e

...h|brush entities]]. However, since {{src2|1}} engine, BSP (including brush entities) has been replaced with Meshes (and [[mesh entity]]) for geometry. Early Go [[ericw-tools]] uses the same nomenclature as the original Quake compilers.

...]s).<br>Some source ports (such as KMQuake2) support translucency on brush entities, but exhibit the same alpha sorting issues as GoldSrc. ...as map compilers. Provided for reference only; third party tools such as [[ericw-tools]] were used for the 2023 remaster.

所有 [[lightmap]] 灯光贴图的 [[brush entities]] 以及 [[worldspawn]] 都支持 {{code|_minlight}} [[KV]] （某些 [[FGD ...定制编译器可以通过在 BSP 旁边写入额外的元数据来规避此限制，该元数据由定制的 VRAD 读取。像 {{idtech2}}{{goldsrc}}{{ericw-tools}} 这样的方法也可以轻松为 [[vhv|每顶点光照]] 和 [[ppl|光�

For glowing textures on '''models or brush faces''': For glowing textures on '''brush faces''' only:

...are usually split further. Consequently, decompilers must reconstruct the brush from scratch, resulting in noticeable discrepancies between the original an {{goldsrc|4}} does not store original brush geometry in its [[BSP|BSPs]] like {{src|4}} does. As a result decompiles wi