Hosting and domain costs until October 2024 have been generously sponsored by dumptruck_ds. Thank you!

Difference between revisions of "QBSP"

From Quake Wiki

Line 1: Line 1:
'''QBSP''' is the first stage of [[map compiling]]. It is the process that reads the [[map file]] and generates the [[bsp file]], and in doing so calculates all of the geometry and collision data for the level. It also extracts any needed textures from the associated [[wad files]] and repackages them into the bsp file. After this step, the level can be loaded into the game engine. However, it will not have any lighting or visibility data until you run [[Light]] and [[Vis]].
+
'''QBSP''' is the first stage of [[map compiling]]. It is the process that reads the [[map file]] and generates the [[bsp file]], and in doing so calculates all of the geometry and collision data for the level. It also extracts any needed textures from the associated [[wad file]] (or files) and repackages them into the bsp file. After this step, the level can be loaded into the game engine. However, it will not have any lighting or visibility data until you run [[Light]] and [[Vis]].
  
 
==What QBSP Does==   
 
==What QBSP Does==   
Using the [[brushes]] from the map file's [[worldspawn]] entity, it calculates the [[bsp tree]] that stores all visible surfaces in the game.  It also generates the [[collision hulls]], which are also bsp trees but do not have any visible surfaces, and are only used for collision detection.  For each additional [[entity]] that has brushes, it generates a [[submodel]] which also has its own [[collision hulls]].
+
Using the [[brush|brushes]] from the map file's [[worldspawn]] entity, it calculates the [[bsp tree]] that stores all visible surfaces in the game.  It also generates the [[collision hull|collision hulls]], which are also bsp trees but do not have any visible surfaces, and are only used for collision detection.  For each additional [[entity]] that has brushes, it generates a [[submodel]] which also has its own collision hulls.
  
 
Any textures needed by the level are copied into the bsp file from the associated wad files. At runtime, the engine will load textures from the bsp, not the wad files.
 
Any textures needed by the level are copied into the bsp file from the associated wad files. At runtime, the engine will load textures from the bsp, not the wad files.
Line 9: Line 9:
  
 
==Using QBSP==
 
==Using QBSP==
QBSP is a command-line tool, generally named qbsp.exe.  You can invoke it from a command prompt, via a shortcut or batch file, or from the "compile" or "build" menus of some [[level editors]].
+
QBSP is a command-line tool, generally named qbsp.exe.  You can invoke it from a command prompt, via a shortcut or batch file, or from the "compile" or "build" menus of some [[level editor|level editors]].
  
 
===Command-line options===
 
===Command-line options===
Line 18: Line 18:
  
 
===Updated Versions===
 
===Updated Versions===
In addition to [[id Software]]'s official QBSP, there have been various unofficial versions that improve on the original or add additional features.  For a list of QBSP variants, see [[Compiling Tools]].
+
In addition to [[id Software]]'s official QBSP, there have been various unofficial versions that improve on the original or add additional features.  For a list of QBSP variants, see [[mapping tools]].

Revision as of 09:05, 11 January 2010

QBSP is the first stage of map compiling. It is the process that reads the map file and generates the bsp file, and in doing so calculates all of the geometry and collision data for the level. It also extracts any needed textures from the associated wad file (or files) and repackages them into the bsp file. After this step, the level can be loaded into the game engine. However, it will not have any lighting or visibility data until you run Light and Vis.

What QBSP Does

Using the brushes from the map file's worldspawn entity, it calculates the bsp tree that stores all visible surfaces in the game. It also generates the collision hulls, which are also bsp trees but do not have any visible surfaces, and are only used for collision detection. For each additional entity that has brushes, it generates a submodel which also has its own collision hulls.

Any textures needed by the level are copied into the bsp file from the associated wad files. At runtime, the engine will load textures from the bsp, not the wad files.

QBSP also generates a prt file containing the portal information necessary for Vis to run. The prt file is not needed or used by the game engine. If a map has a leak, QBSP will generate a pointfile instead of a prt file. This file can be used by the game engine to display a visual trail of particles showing you where the leak is. If a map has multiple leaks, QBSP will only find the first one.

Using QBSP

QBSP is a command-line tool, generally named qbsp.exe. You can invoke it from a command prompt, via a shortcut or batch file, or from the "compile" or "build" menus of some level editors.

Command-line options

TODO

Error Messages and Warnings

TODO

Updated Versions

In addition to id Software's official QBSP, there have been various unofficial versions that improve on the original or add additional features. For a list of QBSP variants, see mapping tools.