qbsp − Compile a Quake BSP file from a MAP source file
qbsp [OPTION]... SOURCFILE [DESTFILE]
qbsp is a tool used in the creation of maps for the id Software game Quake. qbsp takes a .map file as input and produces a .bsp file playable in the Quake engine. If the DESTFILE argument is not supplied, the output filename will be chosen by stripping the file extension (if any) from SOURCEFILE and appending the .bsp extension.
Doesn’t perform outside filling
Doesn’t build clip hulls
Doesn’t remove faces using the ’skip’ texture
Only updates .map entities
Print out more .map information
Print out almost no information at all
Doesn’t combine sky and water faces into one large face
Computes portal information for transparent water (default)
Computes portal information for opaque water
Computes portal information for transparent sky
Use alternate texture alignment algorithm. The default is to use the original QBSP texture alignment algorithm, which required the -oldaxis switch in tyrutils-ericw v0.15.1 and earlier.
Force use of expensive processing for SolidBSP stage. Often results in a more optimal BSP file in terms of file size, at the expense of extra processing time.
Creates a .por file, used in the BSP editor
Create an old-style QBSP .PTS file (default is new)
Makes it a compile error if a leak is detected.
Prevents output of percent completion information
Create the output BSP file in BSP2 format. Allows the creation of much larger and more complex maps than the original BSP 29 format).
Create the output BSP file in 2PSB format. This an earlier version of the BSP2 format, supported by the RMQ engine (and thus is also known as the BSP2rmq or RMQe bsp format). original BSP 29 format).
Space between leakfile points (default 2)
Use different texture subdivision (default 240)
Search this directory for wad files (default is cwd)
Use old method of texturing rotate_ brushes where the mapper aligns textures for the object at (0 0 0).
Switch to the cheap spatial subdivion bsp heuristic when splitting nodes of this size (in any dimension). This gives much faster qbsp processing times on large maps and should generate better bsp trees as well. From txqbsp-xt, thanks rebb. (default 1024, 0 to disable)
Generate a hexen2 bsp.
(bspx) Includes a list of brushes for brush-based collision.
"-wrbrushes" combined with "-noclip" argument.
Write only placeholder textures, to depend upon replacements.
Detail brushes are omitted from the compile.
Convert a .MAP to a different .MAP format. fmt can be: quake, quake2, valve, bp (brush primitives). Conversions to "quake" or "quake2" format may not be able to match the texture alignment in the source map, other conversions are lossless. The converted map is saved to <source map name>-<fmt>.map.
The contents inside a brush depend on the texture name(s) assigned to it.
By default brush contents are solid unless they have a special name. Names beginning with an asterisk are liquids. A prefix of *slime indicates slime, *lava is for lava and anything else beginning with * will have contents as water.
All faces of a brush must have textures which indicate the same contents. Mixed content types will cause qbsp to print an error and exit.
Any surfaces assigned a texture name of skip will be compiled into the bsp as invisible surfaces. Solid surfaces will still be solid (e.g. the play can’t walk or shoot through them) but they will not be drawn. Water, slime and lava surfaces can be made invisible using the texture names *waterskip, *slimeskip and *lavaskip respectively.
Hint surfaces cause a bsp split and portal to be generated the on the surface plane, after which they are removed from the final bsp - they are neither visible, nor structural. Strategic placement of hint surfaces can be used by a map author to optimise the PVS calculations so as to limit overdraw by the engine (see also: vis(1)).
Use a texture with the name hintskip on any surfaces of a hint brush which you don’t want to generate bsp splits or portals. All surfaces of a hint brush must use either the hint or hintskip texture name.
This qbsp has a prefab system using a point entity named "misc_external_map". The idea is, each "misc_external_map" imports brushes from an external .map file, applies rotations specified by the "_external_map_angles" key, then translates them to the "origin" key of the "misc_external_map" entity. Finally, the classname of the "misc_external_map" is switched to the one provided by the mapper in the "_external_map_classname" key. (The "origin" key is also cleared to "0 0 0" before saving the .bsp).
The external .map file should consist of worldspawn brushes only, although you can use func_group for editing convenience. Brush entities are merged with the worldspawn brushes during import. All worldspawn keys, and any point entities are ignored. Currently, this means that the "wad" key is not handled, so you need to add any texture wads required by the external .map file to your main map.
Note that you
can set other entity keys on the
"misc_external_map" to configure the final entity
type. e.g. if you set "_external_map_classname" to
"func_door", you can also set a
"targetname" key on the
"misc_external_map", or any other keys for
Specifies the filename of the .map to import.
What entity you want the external map to turn in to. You can use internal qbsp entity types such as "func_detail", or a regular bmodel classname like "func_wall" or "func_door".
Rotation for the prefab, "pitch yaw roll" format. Negative pitch is down.
Short version of "_external_map_angles" for when you want to specify just a yaw rotation.
Scale factor for the prefab, defaults to 1. Either specify a single value or three scales, "x y z".
This version of qbsp supports detail brushes which are similar in concept to Quake 2’s detail brushes. They don’t seal the map (previous versions did).
To be compatible with existing Quake 1 mapping tools, detail brushes can be added by creating an entity with classname "func_detail". When qbsp reads the map file, it will add any brushes included in a func_detail entity into the worldspawn as details and remove the func_detail entity. Any number of func_detail entities can be used (useful for grouping) and all included brushes will be added to the worldspawn.
Here is an example entity definition suitable to add the the .QC files used by BSP Editor:
func_detail (0.5 0.5 0.9) ?
Detail brushes add visual details to
the world, but do not block visibility.
func_detail entities are merged into
the worldspawn entity by the qbsp compiler
and do not appear as separate entities in
the compiled bsp.
For WorldCraft in .FGD format (untested):
@SolidClass color(128 128 230) = func_detail: "Detail" 
For Radiant in .ENT format:
name="func_detail" color="0 .5 .8">
Detail brushes add visual details to the world, but do not
block visibility. func_detail entities are merged into the
worldspawn entity by the qbsp compiler and do not appear as
separate entities in the compiled bsp.
What should be written to the .map file is a simple entity with one or more brushes. E.g.:
( -176 80 0 ) ( -208 80 0 ) ( -208 48 0 ) COP1_1 0 0 0 1.0 1.0
( -192 -80 64 ) ( -208 -80 0 ) ( -192 -64 64 ) COP1_1 0 0 0 1.0 1.0
( -176 -80 0 ) ( -192 -80 64 ) ( -176 -64 0 ) COP1_1 0 0 0 1.0 1.0
( -16 48 0 ) ( -16 64 64 ) ( 0 48 0 ) COP1_1 0 0 0 1.0 1.0
( -16 64 64 ) ( -16 80 0 ) ( 0 64 64 ) COP1_1 0 0 0 1.0 1.0
When qbsp detects detail brushes, it outputs a modified portal file format with the header PRT2 (default is PRT1). This portal file contains extra information needed by vis to compute the potentially visible set (PVS) for the map/bsp. So you will also need a vis util capable of processing the PRT2 file format.
func_detail variant with no collision (players / monsters / gunfire) and doesn’t split world faces. Doesn’t cast shadows unless enabled with "_shadow" "1". Useful for hanging vines. Still creates BSP leafs, which is unavoidable without a new .bsp file format.
func_detail variant that doesn’t split world faces. Useful for when you want a decoration touching a floor or wall to not split the floor/wall faces (you’ll get some overdraw instead.) If it completely covers up a world face, that face will get clipped away, so it’s not suitable for fence textures; see func_detail_fence instead.
Similar to func_detail_wall except it’s suitable for fence textures, never clips away world faces. Useful for fences, grates, etc., that are solid and block gunfire.
Generates an LMSHIFT bspx lump for use by a light util. Note that both scaled and unscaled lighting will normally be used.
Set to 1 to save mirrored inside faces for bmodels, so when the player view is inside the bmodel, they will still see the faces. (e.g. for func_water, or func_illusionary)
For creating vis-blocking illusionary brushes (similar to "func_detail_illusionary" or "func_illusionary". The player can walk through them.) This gives the same effect as water brushes when the "-notranswater" flag is used, except the interior of these brushes are saved as CONTENTS_EMPTY. One thing to be aware of is, if the player’s view is very close to the faces of these brushes, they might be able to see into the void (depending on the engine). Fitzquake family engines have a workaround for this that is enabled if the brushes are textured with a water texture ("*" prefix).
In addition to standard Quake 1 .map files, ericw-tools QBSP is compatible with:
Floating point brush coordinates and texture alignments
Valve’s 220 map format as produced by the Hammer editor
Extended texture positioning as supported by the QuArK editor
Standard Quake 2 map format (leading paths in texture names are stripped and any extra surface properties are ignored)
Brush Primitives produce by Radiant editors (normally a Quake 3 format)
Kevin Shanahan (aka Tyrann) - http://disenchant.net
Based on source provided by id Software and Greg Lewis
Please post bug
reports at https://github.com/ericwa/ericw-tools/issues.
Improvements to the documentation are welcome and encouraged.
2017 Eric Wasylishen
Copyright (C) 2013 Kevin Shanahan
Copyright (C) 1997 Greg Lewis
Copyright (C) 1997 id Software
License GPLv2+: GNU GPL version 2 or later
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
light(1) vis(1) bspinfo(1) bsputil(1) quake(6)