Hosting and domain costs until October 2024 have been generously sponsored by dumptruck_ds. Thank you!
Editing QBSP
From Quake Wiki
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 2: | Line 2: | ||
'''QBSP''' is the first stage of [[Map_compiling|map compiling]]. It is the process that reads the [[Quake file formats|map file]] and generates the [[Quake file formats|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 [[Quake file formats|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 (map compiling)|Light]] and [[Vis]]. | '''QBSP''' is the first stage of [[Map_compiling|map compiling]]. It is the process that reads the [[Quake file formats|map file]] and generates the [[Quake file formats|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 [[Quake file formats|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 (map compiling)|Light]] and [[Vis]]. | ||
| − | ==How QBSP Does | + | ==How QBSP Does== |
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|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. | 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|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. | ||