VRAD

VRAD is the command-line tool that takes a compiled BSP map and embeds lighting data into it. VRAD's static and pre-compiled light is bounced around the world with a radiosity algorithm.

VRAD will:

• Generate lightmaps
• Generate ambient samples
• Generate per-object or per-vertex prop_static and detail prop lighting

VRAD is generally the slowest of the three compilers due to the many, many calculations it must perform. Lighting optimization can help, as can ensuring your map is free of leaks.

Tip:If you are watching the compile dialog and it looks like it has hung at 9... this is usually because VRAD takes longer with each light bounce calculation.

Warning:VRAD will take up a lot of CPU during conversion of trying to make light.

Bug:Ep1 and L4D users seeing crashes when VRAD compiles HDR lighting should read VRAD HDR Crash Fix.  [todo tested in ?]

Bug:In pre-L4D branch games, .mdl files that don't have .dx80.vtx files with them will lead to VRAD skipping lighting for that prop. Copying the .dx90.vtx file and renaming it to a .dx80.vtx will fix the issue.  [todo tested in ?]

A windows batch file to do this automatically has been created here: [1] (place above model folder and run .bat)

Bug:Additionally, .mdl files that have the IDST1 header will fail to load for VBSP, and will give a error message stating the prop failed to load; this can be fixed by changing the header to IDST0 in a Hex Editor, or by recompiling the prop in a non-L4D branch Studiomdl application such as Source 2013.  [todo tested in ?]

Bug:As of around 5-10 years ago up until at least October, 2017 all known copies of VRAD have a thread sharing bug which causes performance to scale poorly to multiple threads, particularly on outdoor scenes with -final set (despite showing 100% CPU usage). The fix to this bug for Source 2013 is available here and edited DLLs are available here. Valve also released a patch for CSGO's VRAD that fixes this issue.  [todo tested in ?]

Bug:Randomly causes corrupt lightmaps that look like "ink spills".  [todo tested in ?]

Tip:Source Engine BSP Lightmap Editor can be used to manually correct a .bsp lightmap data.

Syntax

vrad [options...] <bsp file>

For example:

"Half-Life 2\bin\vrad.exe" -both -StaticPropLighting sdk_trainstation_01

This will generate and embed both standard and High Dynamic Range lighting data, at per-vertex detail for prop_static entities.

Options

Use these in combination with expert compile mode or a batch file.

Effects

-ldr

-hdr

-both

Whether to compile standard or High Dynamic Range lighting, or both.

Note:In , you MUST compile with -hdr in order have proper lighting, as LDR isn't supported.

-fast

Quick and dirty lighting. Don't ship with this.

Note:-fast will cause random and miscolored splotching to appear in darker areas.

-final

Increases the quality of light_environment and indirect lighting by spending more time firing rays.

-extrasky <integerRedirectInput/integer>

Trace N times as many rays for indirect light and sky ambient.

(-final is equivalent to -extrasky 16; normal is equivalent to -extrasky 1)

-lights <filename>.rad

Load a custom lights file in addition to lights.rad and the map-specific lights file. Include the file extension in the parameter.

-bounce <integerRedirectInput/integer>

Set the maximum number of light ray bounces. (default: 100).

-smooth <integerRedirectInput/integer>

Set the threshold for smoothing groups, in degrees (default: 45).

-luxeldensity <normal>

Scale down all luxels. Default (and maximum) value is 1.

-softsun <floatRedirectInput/float>

Treat the sun as an area light source of this many degrees. Produces soft shadows. Recommended values are 0-5, default is 0. Identical to the SunSpreadAngle parameter for light_environment, use that instead.

-StaticPropLighting  (in all games since )

Generate per-vertex lighting on prop_statics; always enabled for light_spot entities. Disables info_lighting entities on props without bump maps. Does not work on props with bump maps, except in .

Warning:This can increase your map's filesize substantially. Disable vertex lighting for props that don't need it to keep filesize low.

Note:In , in order to get proper lighting on your static props, you will need to run VRAD with this command.

-StaticPropPolys  (in all games since )

Use the actual meshes of static props to generate shadows instead of using their collision meshes. This results in far more accurate shadowing.

-TextureShadows  (in all games since )

Generates lightmap shadows from $translucent surfaces of models (NOT brushes) that are specified in a lights file and being used with prop_static. Usually requires -StaticPropPolys to have any effect.

Note:A surface will need a low lightmap scale for most texture shadows to be recognisable.

Note:For some strange reason this will not work if a translucent texture's VMT file contains the .vtf file ending in the basetexture lines.

-aoscale <floatRedirectInput/float> (in all games since )

Scales the intensity of VRAD's simulated ambient occlusion. 1.0 is default.

Tip:Valve uses 1.5 for the new Dust 2.

-aoradius <floatRedirectInput/float> (only in )

Set the radius of VRAD's simulated ambient occlusion.

Todo: Figure out what exactly this does.

-aosamples <integerRedirectInput/integer> (only in )

How many samples to use for VRAD's simulated ambient occlusion.

-StaticPropBounce <integerRedirectInput/integer> (only in )

Number of static prop light bounces to simulate. The default is 0.

Tip:Valve uses 3 static prop bounces for the new Dust 2.

Note:Any static props that you want light to bounce off of must also have their "Enable Bounced Lighting" keyvalue set.

-StaticPropLightingFinal  (only in )

Compiles higher quality lighting for static props.

-StaticPropLightingOld  (only in )

Will use the old lighting algorithm on props, light affects them much more.

-choptexlights  (only in )

Enables chopping of texture lights generated from a lights file. Control texture light quality with lightmap density in Hammer. Dramatically increases both texture light quality and compile time.

-extratransfers  (only in )

Enable overscaling of light transfers.

-transferscale <floatRedirectInput/float> (only in )

This is the scale factor of light transfers. Increased values make surfaces transfer extra light (scale of 2-4 suggested). Default 1.0.

-satthresh <floatRedirectInput/float> (only in )

This is the threshold that checks how saturated a material color is. Used with -satthreshscale. Default 0.4.

-satthreshscale <floatRedirectInput/float> (only in )

The amount to scale light transfers from surfaces that pass the saturation threshold. Default 3.0.

Performance

-low

Run as a low-priority process.

-threads <integerRedirectInput/integer>

Override the number of CPU threads used. Maximum is 16 threads. With a patched vrad_dll you can use 32 threads.

-mpi

Use VMPI to distribute computations.

-mpi_pw <stringRedirectInput/string>

Use a password to choose a specific set of VMPI workers.

-noextra

Disable supersampling. This will lead to blockier, more inaccurate lighting.

-chop <integerRedirectInput/integer>

Smallest number of luxel widths for a bounce patch, used on edges. (Default: 4)

-maxchop <integerRedirectInput/integer>

Coarsest allowed number of luxel widths for a patch, used in face interiors. (Default: 4)

-dispchop <integerRedirectInput/integer>

Smallest acceptable luxel width of displacement patch face. (Default: 8)

-LargeDispSampleRadius

This can be used if there are splotches of bounced light on terrain. The compile will take longer, but it will gather light across a wider area.

-compressconstant <integerRedirectInput/integer>

Compress lightmaps whose color variation is less than this many units.

-fastambient

Uses low quality per-leaf ambient sampling to save compute time.

-noao  (only in )

Disables compiling simulated ambient occlusion for lightmaps.

-StaticPropSampleScale <integerRedirectInput/integer> (only in )

Regulates the generated per-vertex prop_static lighting.

slow: 16 (high quality); default: 4 (normal); fast: 0.25 (low quality)

Note:-final is the equivalent of having -StaticPropLightingScale 16.

Debugging

-rederrors

Emit red light when "a luxel has no samples".

-vproject <directory>

-game <directory>

Override the VPROJECT environment variable.

-insert_search_path <directory>

Todo: What does this do?

-v

-verbose

Turn on verbose output.

-novconfig

Don't bring up graphical UI on vproject errors.

-dump

Dump patches to debug files.

-dumpnormals

Write normals to debug .txt files.

-debugextra

Places debugging data in lightmaps to visualize supersampling.

-dlightmap

Force direct lighting into different lightmap than radiosity.

-stoponexit

Wait for a keypress on exit.

-nodetaillight

Don't light detail props.

-centersamples

Move sample centers.

-loghash

Log the sample hash table to samplehash.txt.

-onlydetail

Only light detail props and per-leaf lighting.

-maxdispsamplesize <integerRedirectInput/integer>

Set max displacement sample size (default: 512).

-FullMinidump

Write large minidumps on crash.

-OnlyStaticProps

Only perform direct static prop lighting.

-StaticPropNormals

When lighting static props, just show their normal vector.

-noskyboxrecurse

Turn off recursion into 3d skybox (skybox shadows on world).

-nossprops

Globally disable self-shadowing on static props.

-dumppropmaps  (only in )

Dump computed prop lightmaps.

Lights files

A light file is a plain text file that can be used to manipulate the way VRAD handles given materials when compiling static lighting. All lights files must have the .rad file extension and must be in the same folder as your gameinfo.txt.

There are:

1. lights.rad, the global file.
2. An auto-loaded map light file, using the format <map name>.rad. The file must be placed in the same folder as <map name>.vmf.
3. Any number of additional lights files that can be added with the -lights parameter.

Rules

Lights files perform these functions, one rule per line:

<material> <red> <green> <blue> <intensity> <hdr_red> <hdr_green> <hdr_blue> <hdr_intensity>

Makes the material emit the given light value when applied to a brush face (hdr_ values are optional). Texture scale has an effect on final intensity.

Note:The material does not truly emit light, but instead, a light entity is generated every four luxels across a brush face using a lit material. It may be smarter and cheaper to instead manually place light entities near the material.

Note:Materials that aren't in a folder must have a slash before their name.

Warning:A func_detail with an emissive material applied on a face may randomly cause VRAD to fail computing lighting for the face.

noshadow <material name>

Prevents the named material from casting shadows.

forcetextureshadow <model path>.mdl

Enables translucency shadow testing for a model when VRAD is run with -TextureShadows. Path is relative to the models folder.

ldr:

hdr:

Prefixes to make any rule only apply to LDR or HDR lighting.

hdr:ldr:

Lines beginning with both tags (in that order) will always be ignored by VRAD. Can be used to add comments or quickly disable some entries.

See also

• Map Compiling Theory
• HDR Lighting Basics
• VRAD HDR Crash Fix
• Static Props show up black