VVIS: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (→‎See also: Added navbox)
(how VIS works, courtesy of GDC)
Line 5: Line 5:
VVIS will:
VVIS will:


* Test visibility between [[visleaf|visleaves]]
* Test visibility between [[visleaf|visleaves]] by [http://www.gdcvault.com/play/1014234/Excerpt-Quake-Postmortem-Optimizing-Level clipping their view planes].
* Enforce a maximum visibility distance, if configured to
* Enforce a maximum visibility distance, if configured to.
 
== Syntax ==
== Syntax ==



Revision as of 05:51, 30 December 2011

VVIS is the command-line tool that takes a compiled BSP map and embeds visibility data into it. VVIS tests which visleaves can see each other, and which cannot. See Visibility optimization for a more detailed explanation.

VVIS will:

Syntax

vvis [options...] <bsp file>

For example:

"%sourcesdk%\bin\orangebox\bin\vvis" -tmpout sdk_trainstation_01

This will generate and embed a visibility chart, writing portal data out to .\tmp\sdk_trainstation_01.prt.

Options

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

Functions

-fast
Only do a quick first pass. Does not actually test visibility.
-radius_override <int>
Force a maximum vis radius, in units, regardless of whether an env_fog_controller specifies one.
-nosort
Don't sort (an optimization) portals.
-tmpin
Read portals from \tmp\<mapname>.
-tmpout
Write portals to \tmp\<mapname>.

General

-low
Run as an idle-priority process.
-threads
Control the number of threads used. Defaults to the # of processors (times 2 for Hypertreading/SMT CPU's) on your machine.
-v
-verbose
Turn on verbose output
-novconfig
Don't bring up graphical UI on vproject errors.
-mpi
Use VMPI to distribute computations.
-mpi_pw <string>
Use a password to choose a specific set of VMPI workers.
-vproject <string>
-game <string>
Override the VPROJECT environment variable.

See also