| BSP - Binary Space Partition Updated 31 Mar 2001 | Upper levels: - QuArK Information Base - 2. Map editing - 2.7. Map compiling errors

2.7.2. BSP - Binary Space Partition | [ Prev - Up - Next ]

This page lists various encountered errors, that may occur during the BSP map-compiling phase. All QuArK supported games, are know to use a BSP map-compiling phase:
Game | Possible program-names
--- | ---

Quake-1 | QBSP.EXE, TXQBSP.EXE

Hexen-2 | QBSP.EXE, HXBSP06.EXE

Quake-2 | QBSP3.EXE, TXQBSP39.EXE

Heretic-2 | QBSP3.EXE, TXQBSP39.EXE

Half-Life | BSP.EXE, HLBSP.EXE

Sin | QBSP3.EXE

Kingpin | KPBSP.EXE

Soldier of Fortune | SOFBSP.EXE

Quake-3:Arena | Q3MAP.EXE

Star Trek:Voyager - Elite Force | Q3MAP.EXE

Index

- - Parsing error (14 Feb 2001)
- - New portal was clipped away (30 Mar 2001)
- - Point off plane (30 Mar 2001)

Parsing error | Decker - 14 Feb 2001 | [ Top ]

    Error: parsing entity 3, brush 0, side 2 : expecting '(' got '32'
Getting an error similar to the above, usually means that the .MAP file isn't in the correct format, for the build-tool to understand. Please check: Are you using the correct build-tool for the correct game? For instance, it is of no use, to have a Quake-1 build-tool compile a Quake-3:Arena .MAP file, as the internal structure in the Quake-3:Arena .MAP file can't be understood by the Quake-1 build-tool. Have you set up QuArK to the proper game-mode? Make sure that you have selected the correct game-mode, for the game you want to make maps for. Did you try to convert a game-A .MAP file to a game-B .MAP file, using QuArK? QuArK can't always do a useful conversion of .MAP files, from some game to a different game. When doing this, you should experiment alot to see what can and what can not work.

New portal was clipped away | Andy / Armin (?) - 30 Mar 2001 | [ Top ]

I don't know why this message sometimes pops up, resulting in large gray areas in Quake. My modest experience on it seemed to reveal that this error sometimes occurs when you stick a polyhedron into another one, if one face on a polyhedron ends up completely inside the other polyhedron, and if this face is not axis-aligned, i.e. it has a slope or orientation of something else than 0, 90, 180 or 270 degree. I got the above error after I slightly moved a polyhedron into another one to avoid a small gap between them, and all three conditions were suddenly met. The problem disappeared when I put the polyhedron back outside the over one.

Point off plane | Andy / Armin (?) - 30 Mar 2001 | [ Top ]

This is not a map error : it is just a bug of QBSP ! For some strange reason, although a .map file only contains definitions of planes, QBSP ends up with vertexes out of their plane... This is not an error in your maps. Just use a version of QBSP that only issues warnings instead of crashing when it runs into the point off plane problem. There is nothing more to do about it - out of maybe rewriting parts of QBSP itself. But it works anyway. Someone said that "point off plane" occurs when you have a polyhedron with a side which vertexes are not all in the same plane. This is absolutely wrong. .map files on which QBSP works can only contain plane definitions and no vertex coordinates. Map editors that let the user create such strange polyhedron are just a hack in the sense that if you save your work in a .map file and open it again, the strange polyhedrons are flattened out. Of course, because the map editor had to arbitrarily choose a plane to write in the .map file. I don't know how it can choose a plane when there is none containing all the vertexes ! They probably just compute the plane containing the first three points and drop the other ones.

GNU General Public License by The QuArK (Quake Army Knife) Community - http://www.planetquake.com/quark | [ Prev - Top - Next ]