Difference between revisions of "Lighting"

From Valve Developer Community
Jump to: navigation, search
m (Static light sources)
m (See also: Fixed link)
Line 110: Line 110:
* [[HL2 light props]]
* [[HL2 light props]]
* [[Color theory (level design)]]
* [[Color theory (level design)]]
* [[List_of_entities#Light_Entities|Light entities]] - A list of light entities.
* [[List_of_entities#Light_entities|Light entities]] - A list of light entities.
== External links ==
== External links ==

Revision as of 15:55, 13 September 2009



Static light sources

Tip:Static lighting is compiled into Lightmaps, which illuminate brushes and models, and Cubemaps, which provide static reflections. It is free to render, as additional static lights only alter that which is already being processed.
A static, omni-directional point light source. (e.g. a naked light bulb or flame.)
A static, uni-directional point light source. (e.g. a torch or flashlight) The conical beam angle cannot exceed 90°.
Provides two linked light sources:
  • A diffuse 'ambient' light (representing reflected light from clouds and the atmosphere in general) that emits from all skybox surfaces
  • A directional 'brightness' light (representing sunlight or moonlight) that is only cast in a single direction.
Both are emitted from the toolsskybox material wherever it is used on a map. See also Skybox.
Illuminates particles produced by env_smokestack. Particles are not affected by normal lighting. Use (no more than) two of these to make (only) env_smokestack particles appear to reflect ambient lighting.
Glowing Textures
Brush surfaces with a light-emitting material (as defined in game_dir/lights.rad) applied will cast volumetric light in a 180° cone.

Static light receivers

This Hammer Face Edit Dialog tool 'Lightmap Scale' can be used to control how sharp or diffuse the lightmap of a brush surface will be - an effect most noticeable between areas of high contrast, e.g. shadows. Note that while adding extra light sources will not affect performance, decreasing lightmap scale (i.e. increasing resolution) will.
Unlike other model entities, prop_static are lit statically: a lighting value is stored for every vertex, and the model's collision mesh (or, optionally, reference mesh) is used to calculate lightmap shadows.
There are the following options:
  • disableshadows - Do not cast lightmap shadows
  • disablevertexlighting - Only store a single lighting value for the entire model
  • disableselfshadowing - Prevents the entity from casting shadows on itself
  • ignorenormals - Unknown

Dynamic light sources

Tip:Dynamic lighting is calculated at runtime, which makes it expensive to render.
env_projectedtexture shines from a doorway.
A simple, uni-directional dynamic light that can be moved, turned, and adjusted.
A dynamic spotlight beam effect, with an optional dynamic light source where it hits a surface.
A spotlight NPC, similar to point_spotlight but with the capability of tracking targets.
A dynamic light that lights with a texture rather than a solid colour, and which also 'subtracts' realistic dynamic shadows. Affects all surfaces that can accept lighting, and is used for the player flashlight in Episode Two.

Dynamic shadows

Tip:Dynamic Shadows are cast only by world models (NPCs, phys-props, etc), and only onto brush surfaces (from both Static and Dynamic light sources). They are calculated at runtime, so they are quite crude and relatively expensive to render.

Warning: Dynamic Shadows can sometimes project through walls and floors, giving away the location of players or objects. Use info_no_dynamic_shadow to workaround this problem if you encounter it.

Note:Dynamic Shadows do not merge with each other or with Lightmaps when they overlap. This can produce undesirable 'doubling up' effects when, for instance, phys props are placed on a phys prop table. You can enable and disable shadows on dynamic entities to work around this.
Point entity used to control Dynamic Shadow projections for the entire map, including maximum distance cast, direction cast, and sharpness/diffuseness.
Point entity used to list Brush surfaces that should not receive Dynamic Shadows.
prop_physics entities 
have a "shadowcastdist" keyvalue to override how far this object casts Dynamic Shadows.
prop_dynamic entities 
have a "disableshadows" keyvalue, and "enableshadows" and "disableshadows" inputs to control Dynamic Shadows cast by them.
NPC entities 
have the prop_dynamic shadow controls, plus a "disablereceiveshadows" To do: to prevent...?

Tyndall effects

Tyndall effects are caused by light scattering on suspended (colloid) particles in a transparent medium. Eg car headlights in fog.

  • Halo (Glow Sprite) effects :
  • env_sprite - entity used to create omni-directional glow or flare effects.
  • env_lightglow - an asymmetrical glow (for areas of contrasting light).
  • env_sun - adds a bright haloed spot to the Skybox to represent the position of the Sun or Moon.
  • Brush texture : models/effects/vol_light001
  • Brush texture : models/effects/vol_light002
  • Model : models/Effects/vol_light.mdl - use with prop_static.
  • See also Render Modes for sprites, particularly World Space Glow.

Common values

City 17 day
Brightness 237 218 143 800
Ambience 190 201 220 100
Ravenholm night
Brightness 175 230 239 50
Ambience 43 45 57 5
Combine lamp
Brightness 147 226 240 3000
Ambience N/A
Tungsten bulb
Brightness 254 216 146
Ambience N/A
Fluorescent bulb
Brightness 159 237 215
Ambience N/A

For values to accompany the stock skybox materials, see Sky List.


  • Naming a light makes it more expensive. Only name lights when you need to. Multiple lights sharing the same name are cheaper than lights with separate names.
  • light_dynamic is especially expensive, and will not even show up on some systems
  • The basic light entities do not come with a visible representation (e.g. a lightbulb). For that you need a prop. See HL2 light props for a list.
  • The basic light entities do not come with a "glow" as you'd expect to see in a foggy or misty area. To provide this, either compile and run the map with HDR enabled, or add a point_spotlight (with dynamic lighting off unless needed) or env_lightglow entity.
  • Maps will not be lit unless you run vrad (or equivalent). Vrad will not run properly and will not calculate realistic light bounces unless the level is free of leaks.
  • Several textures provide their own light & can do so using lights.rad in a mod's directory or the one in sourcesdk/bin.
  • Moving brushed-based objects will not change the way they are lit. Their lighting will be calculated only according to their positions in Hammer. (e.g. a brush in a dark room will not become bright if it is brought into a bright room.)

Console commands

mat_fullbright 2. The bright white physics props seem to be a bug; they are lit correctly when in motion.
mat_fullbright <0-2>
0 is normal lighting.
1 is 'full bright' lighting, where everything is 100% lit.
2 has been introduced with the Orange Box and is 'lighting only'. It replaces all textures' images with a colourless monotone, allowing you to see exactly what is lit, where, and probably how.

See also

External links