Search results

* [[Brush]]es (except those used by [[Brush entity|entities]]) {{KV|Targetname|intn=targetname|target_source|Name which other entities use to send [[#Inputs|inputs]] to this entity.}}

{{Source topicon}} {{vbsp|4}} is the tool that compiles a raw [[VMF]] file into [[BSP (Source)|Source 1's BSP format]]. It is generally followed by [[VVIS]] and [[VRAD]].

...ource2|3.1}} and {{strata|3.1}} games shows the text in orange color, with Source 2 games being in a slightly different font, and {{cof|3.1}} shows up as red * [[Non-FGD features|Missing entities]] from the [[FGD]](s) that are placed on a map in {{hammer|3.1}} will appea

{{source topicon}}{{csgo topicon}} | forks = {{Strata|2}}

...d ''prop'' in the Source is generally synonymous with code-simulated model entities. There are various prop entity categories, each representing models with sp ...cs mesh for such a prop, although the sphere size can only be defined in {{strata}}.

{{this is a|model entity|name=linked_portal_door|game=Portal 2|game1=Strata Source|icon=Portal 2}} It is a special type of [[prop_portal|portal]] without any ...ty]] in close proximity to the portal causes it to close. Non-moving brush entities and animated or moving [[prop]]s are okay though.

...efault) 1:16 scale. 3D skyboxes are non-interactive – the player and other entities cannot move into the 3D skybox space. ...ed in many of the maps for official Source games such as [[Counter-Strike: Source]].

{{This is a|point entity|name=env_projectedtexture|since=Source 2007}} .... env_Projectedtexture does not light the world similarly that other light entities which are ray-traced when you compile the map. This light however is real-t

...The vast majority of models in a typical map are <code>prop_static</code> entities. ...c</code> provided it has a [[collision mesh]], and, unlike all other model entities, can be lit per-vertex and cast shadows onto [[lightmap]]s.

{{Source topicon}} ...Space Partition|бинарного разделения пространства}} формата [[BSP (Source)|Source 1's BSP]]. После этого обычно используются {{L|

{{Tabs|VRAD|source=1|source2=1|main=source}} {{vrad|4}} is the [[command-line]] tool for {{source|4|}} that takes a compiled BSP map and embeds lighting data into it. VRAD's

{{Source topicon}} | title = Source

...h|info about Source SDK Base 2013, and how to setting up & compiling SDK|[[Source SDK Base 2013]]|}} </span> | title = Source 2013 engine branch

En versiones del motor anteriores a {{L|CSGO}} de {{csgobranch}} y {{strata|2}}, si algún material en el modelo del prop usa mapeo normal ({{ent|$bump ...} limita el número máximo de entidades en un mapa, incluyendo {{L|internal entities|entidades internas}}, y debido a que los <code>prop_static</code> cuentan p

...me Data''') is a plain-text file format used to define all of the [[entity|entities]] of a game for a map editor, allowing mappers can select them from within ...er. If you do not include <code>@include "base.fgd"</code> at the top of a Source 1 or 2 FGD and it is loaded before <code>base.fgd</code>, you will encounte

{{Source topicon}}{{subpage|[[BSP]]}} .../web/20050426034532/http://www.geocities.com/cofrdrbob/bspformat.html "The Source Engine BSP File Format" from October 2005], retrieved from Geocities before

{{LanguageBar|title = Bita Spaco Partigo (Source 1)}} {{Source topicon}}{{subpage|[[BSP]]}}

...d by the game as soon as it starts, and [[GoldSrc|all]] [[Source|Valve]] [[Source 2|engines]] inherit this syntax. These command-line parameters will work with any Source engine games ({{hl2|4}}, {{css|4}}, etc.).

{{LanguageBar|title=Porting GoldSrc content to Source}} {{Gldsrc topicon}}{{Xash3D topicon}}{{Source topicon}}

...) é um formato de arquivo de texto simples usado para definir todas as {{L|entities|entidades}} de um jogo para um editor de mapas, permitindo que os mapeadore == Entities ==