Search results

{{LanguageBar|title=ericw-tools}} '''ericw-tools''', also colloquially referred to as '''EricW's tools''', is a set of compi

...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

...GoldSrc)|alt=cycler}} can be used to streamline this process, ensuring the entities are defined in the correct order in the compiled BSP.}}}} ...ight, because they cannot inherit lighting info from the world.{{tip|Use [[ericw-tools]] and compile with {{code|-dirtdebug}} to apply some generic ambient occlus

...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 At its core, the format consists of several [[entities]], each of which is optionally capable of storing one or more [[brush]]es,

...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

* {{quake|4}} (and {{hexen2|4}}) - [[ericw-tools]] * Ability to hide triggers and unknown entities

{{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

..."special" in {{newbspguy|4.1}}, then recompiling RAD. Alternatively, use [[ericw-tools]] and add {{code|_splitturb 0}} to worldspawn. For [[func_water]], [[VHLT]] ...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

Some compilers, such as [[ericw-tools]], treat it as an alias for a combination of CONTENTS_MIST and CONTENTS_WIN | {{not|Vanilla}} Blocks moving entities using CONTENTS_PROJECTILE. No effect on hitscan weapons.

...to account for maximum lightmap size (15x15 luxels, or 240x240 texels). [[ericw-tools]] additionally uses this on surfaces textured with {{code|TRIGGER}}. Entities are always CONTENTS_SOLID; in {{goldsrc|2}}, the {{code|skin}} KV to overri

...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.

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

...]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.

All [[lightmap]]ped [[brush entities]], as well as [[worldspawn]], support the {{code|_minlight}} [[KV]] ("Minim {{note|Psuedo-entities which collapse to {{ent|worldspawn}}, such as {{ent|func_detail}} and (in g

...s dialog box will only display the VisGroup tab. Information on individual entities can be found in the entity list. These brushes can be converted to [[func_d ===== Entities =====