Search results

{{This is a|internal=1|point entity|name=info_texlights|game=ZHLT|game1=VHLT|nocat=1}} :{{Important|In VHLT, lights from info_texlights with color set to {{code|255 255 255}} will use

In [[VHLT]] and derivatives, the KV {{code|zhlt_noclip}} can be used to disable gener ...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

...ty, faster vis times, switchable texture based lighting, support for brush entities casting shadows, removal of "sticky" edges, support for 64-bit processors, ...th February 2006. Its official sequel, developed by Vluzacn, is known as [[VHLT]].

..._spread}}, added with [[ZHLT]], and {{code|_diffuse_light2}}, added with [[VHLT]].}} [[Category:Half-Life Entities]]

...GoldSrc)|alt=cycler}} can be used to streamline this process, ensuring the entities are defined in the correct order in the compiled BSP.}}}}

* {{LCategory|Counter-Strike entities|反恐精英实体列表}} * {{LCategory|Counter-Strike: Condition Zero entities|零点行动实体列表}}

* [[:Category:Counter-Strike entities|List of Counter-Strike entities]] ...ter-Strike: Condition Zero entities|List of Counter-Strike: Condition Zero entities]]

* {{gldsrc|4}} - [[VHLT|VHLT v34]] or VHLT forks * Ability to hide triggers and unknown entities

* For brush entities which should be unlit, use [[VHLT]]'s {{code|zhlt_striprad}} KV to strip lightmaps from the entity after RAD

...tools]] and add {{code|_splitturb 0}} to worldspawn. For [[func_water]], [[VHLT]]'s {{code|zhlt_striprad}} can be used.}} }} ...l textures in this set in sequence (at roughly 10 FPS). If tied to certain entities, such as {{ent|func_wall (GoldSrc)|alt=func_wall}} or {{ent|func_button (Go

...be rendering related keyvalues and inputs available only to specific brush entities{{confirm}} and those would be listed on their pages. ...ty will cast baked [[lightmap]] shadows.<br>Recommended for "static" brush entities that don't move, toggle, or get deleted. Can be useful for [[func_door|door

...LT.WAD]]}}, as it contains all necessary tool textures used by [[ZHLT]], [[VHLT]], and derivatives.}} | Used for [[trigger]] brush entities. {{note|The version of this texture found in {{code|XENO.WAD}} uses a [[:Fi

In [[HLBSP]] ([[ZHLT]]/[[VHLT]]), it will generate this error: probably should not be deleted. Some complex rotating objects entities need

...ary; it might be set after CSG, but will be dropped after BSP || Used by [[VHLT]]; set if {{code|zhlt_hidden}} is set. Tells HLBSP to not add the face to a Entities are always CONTENTS_SOLID; in {{goldsrc|2}}, the {{code|skin}} KV to overri

{{this is a|point entity|name=light_surface|internal=1|game=VHLT}} It is used to create a [[texlight]] that can be toggled or animated like ...ter entity classname|classname|Only cast this texlight from brush faces on entities with this [[classname]].}}

* Use [[VHLT]], not the original HL1 compile tools. The official maps were compiled with ...g|Use Day of Defeats FGD in pair with Half-Life FGD, or you won't see most entities!}}

[[FGD]] for [[VHLT]], containing compiler-specific entities. // It makes all entities visible from this place. This is useful for overview mode (dev_overview 1).

...h|brush entities]]. However, since {{src2|1}} engine, BSP (including brush entities) has been replaced with Meshes (and [[mesh entity]]) for geometry. Early Go ...} compilers !! Original {{gldsrc|4.1}} compilers !! {{gldsrc}} [[ZHLT]], [[VHLT]], and derivatives !! {{source|4.1}} compilers !! {{source2|4.1}} compilers

Dans {{L|HLBSP}} ({{L|ZHLT}}/{{L|VHLT}}), cela générera l'erreur suivante: probably should not be deleted. Some complex rotating objects entities need

...and the optimization features provided by [[ZHLT]] and the now-standard [[VHLT]] are not mentioned.}} ...that [[displacement]]s, [[Point entity|point]] and [[Brush entity|brush]] entities (including [[#Detail_brushes|detail brushes]]) don't affect leaves. Create