BSP data structure - Revision history

Asteroth: /* 1 - DEFPOINTS */

2022-04-23T03:13:20Z

1 - DEFPOINTS

← Older revision		Revision as of 03:13, 23 April 2022
Line 26:		Line 26:
	+20 n_verts*char norm_counts		+20 n_verts*char norm_counts
	+offset vertex_data // Each vertex n is a point followed by norm_counts[n] normals.</pre></blockquote>		+offset vertex_data // Each vertex n is a point followed by norm_counts[n] normals.</pre></blockquote>
	** Note: DEFPOINTS is the only type of chunk on bsp_data that could be unaligned. The offset to vertex data must be divisible by 4. This is a ~~mayor~~ cause of bus errors on ARM arch.		** Note: DEFPOINTS is the only type of chunk on bsp_data that could be unaligned. The offset to vertex data must be divisible by 4. This is a major cause of bus errors on ARM arch.

	===2 - FLATPOLY===		===2 - FLATPOLY===

Asteroth at 03:12, 23 April 2022

2022-04-23T03:12:49Z

← Older revision		Revision as of 03:12, 23 April 2022
Line 65:		Line 65:
	===4 - SORTNORM===		===4 - SORTNORM===
	Sortnorms are planes that split the model recursively		Sortnorms are planes that split the model recursively
	* All offsets must lead to EOF, another SORTNORM, or BOUNDBOX		* All offsets must lead to EOF, another SORTNORM, SORTNORM2, or BOUNDBOX
	<blockquote><pre>+ 0 int id = 4		<blockquote><pre>+ 0 int id = 4
	+ 4 int size		+ 4 int size
Line 108:		Line 108:

	===7 - SORTNORM2===		===7 - SORTNORM2===
	Recursively splits into TMAP2POLY or more SORTNORM2, more space efficient than SORTNORM		Recursively splits into TMAP2POLY or more SORTNORM2/SORTNORM, more space efficient than SORTNORM
	* Offsets must lead to another SORTNORM2 or a single TMAP2POLY		* Offsets must lead to another SORTNORM2, SORTNORM, or a single TMAP2POLY
	<blockquote><pre>+ 0 int id = 7		<blockquote><pre>+ 0 int id = 7
	+ 4 int size		+ 4 int size

Asteroth at 06:32, 21 April 2022

2022-04-21T06:32:56Z

← Older revision		Revision as of 06:32, 21 April 2022
Line 78:		Line 78:
	+56 vector min_bounding_box_point // of all polys under here		+56 vector min_bounding_box_point // of all polys under here
	+68 vector max_bounding_box_point // of all polys under here</pre></blockquote>		+68 vector max_bounding_box_point // of all polys under here</pre></blockquote>
	5 - BOUNDBOX - Bounding boxes are used to speed up lighting and collision calculations.
			===5 - BOUNDBOX===
			Bounding boxes are used to speed up lighting and collision calculations.
	* May be followed by any number of TMAPPOLY or FLATPOLY, punctuated with EOF		* May be followed by any number of TMAPPOLY or FLATPOLY, punctuated with EOF
	<blockquote><pre>+ 0 int id = 5		<blockquote><pre>+ 0 int id = 5

Asteroth at 06:31, 21 April 2022

2022-04-21T06:31:52Z

← Older revision		Revision as of 06:31, 21 April 2022
Line 6:		Line 6:
	This document was written by John Slagel from Volition Inc., with revisions and bugfixing from Garry Knudson and Francis "Pastel" Avila.		This document was written by John Slagel from Volition Inc., with revisions and bugfixing from Garry Knudson and Francis "Pastel" Avila.

	~~==3D model data==~~		The first byte defines the block now following (0-7, see below). After a block the following byte defines the data of the next block, etc.
	The first byte defines the block now following (0-5, see below). After a block the following byte defines the data of the next block, etc.
	[[Media:Bsp_chunk.png]]		[[Media:Bsp_chunk.png]]

	0 - EOF - Means end of ~~tree~~ reached		===0 - EOF===
			Means end of a local data structure reached
			* Must follow every SORTNORM
			* Must end a series of TMAPPOLY
	<blockquote><pre>+ 0 int id = 0		<blockquote><pre>+ 0 int id = 0
	+ 4 int size</pre></blockquote>		+ 4 int size</pre></blockquote>
	** Note: EOF chunk lacks the size int after the ID, it should be considered as size 4 due to the rule of other chunks.

	1 - DEFPOINTS - Defines the vertices		===1 - DEFPOINTS===
			Defines the vertices and normals
			* Must be the first chunk in bsp data and may not be included more than once
	<blockquote><pre>+ 0 int id = 1		<blockquote><pre>+ 0 int id = 1
	+ 4 int size		+ 4 int size
Line 24:		Line 27:
	+offset vertex_data // Each vertex n is a point followed by norm_counts[n] normals.</pre></blockquote>		+offset vertex_data // Each vertex n is a point followed by norm_counts[n] normals.</pre></blockquote>
	** Note: DEFPOINTS is the only type of chunk on bsp_data that could be unaligned. The offset to vertex data must be divisible by 4. This is a mayor cause of bus errors on ARM arch.		** Note: DEFPOINTS is the only type of chunk on bsp_data that could be unaligned. The offset to vertex data must be divisible by 4. This is a mayor cause of bus errors on ARM arch.
	2 - FLATPOLY - Flat (non-textured) polygon
			===2 - FLATPOLY===
			Flat (non-textured) polygon
			* May be listed several times in a row, after a BOUNDBOX, and punctuated with EOF
	<blockquote><pre>+ 0 int id = 2		<blockquote><pre>+ 0 int id = 2
	+ 4 int size		+ 4 int size
Line 39:		Line 45:
	short normnum[i]		short normnum[i]
	}</pre></blockquote>		}</pre></blockquote>
	3 - TMAPPOLY - Textured polygons
			===3 - TMAPPOLY===
			Textured polygons
			* May be listed several times in a row, after a BOUNDBOX, and punctuated with EOF
	<blockquote><pre>+ 0 int id = 3		<blockquote><pre>+ 0 int id = 3
	+ 4 int size		+ 4 int size
Line 53:		Line 62:
	float v[i]		float v[i]
	}</pre></blockquote>		}</pre></blockquote>
	4 - SORTNORM - Sortnorms are planes that split the model recursively
			===4 - SORTNORM===
			Sortnorms are planes that split the model recursively
			* All offsets must lead to EOF, another SORTNORM, or BOUNDBOX
	<blockquote><pre>+ 0 int id = 4		<blockquote><pre>+ 0 int id = 4
	+ 4 int size		+ 4 int size
Line 67:		Line 79:
	+68 vector max_bounding_box_point // of all polys under here</pre></blockquote>		+68 vector max_bounding_box_point // of all polys under here</pre></blockquote>
	5 - BOUNDBOX - Bounding boxes are used to speed up lighting and collision calculations.		5 - BOUNDBOX - Bounding boxes are used to speed up lighting and collision calculations.
			* May be followed by any number of TMAPPOLY or FLATPOLY, punctuated with EOF
	<blockquote><pre>+ 0 int id = 5		<blockquote><pre>+ 0 int id = 5
	+ 4 int size		+ 4 int size
	+ 8 vector min_point		+ 8 vector min_point
	+20 vector max_point</pre></blockquote>		+20 vector max_point</pre></blockquote>
	6 - TMAP2POLY - Textured polygons with increased vertex limit
	<blockquote><pre>+ 0 int id = 3		==Version 2300 or Higher==

			===6 - TMAP2POLY===
			Textured polygons with increased vertex limit
			* Is ''not'' preceded by BOUNDBOX, ended with EOF, or listed in a series.
			<blockquote><pre>+ 0 int id = 6
	+ 4 int size		+ 4 int size
	+ 8 vector ~~normal~~		+ 8 vector min_bounding_box_point
	+20 ~~uint nverts~~		+ 20 vector max_bounding_box_point
	+24 int tmap_num		+ 32 vector normal
	+28 for each vertex, i {		+ 44 int tmap_num
			+ 48 uint nverts
			for each vertex, i {
	uint vertnum[i]		uint vertnum[i]
	uint normnum[i]		uint normnum[i]
Line 83:		Line 103:
	float v[i]		float v[i]
	}</pre></blockquote>		}</pre></blockquote>
	** Note: TMAP2POLY increases the vertex and normal limit for subobjects, which is the main distinction from TMAPPOLY.		** Note: TMAP2POLY increases the vertex and normal limit for subobjects and includes bounding box info, which is the main distinction from TMAPPOLY.

			===7 - SORTNORM2===
			Recursively splits into TMAP2POLY or more SORTNORM2, more space efficient than SORTNORM
			* Offsets must lead to another SORTNORM2 or a single TMAP2POLY
			<blockquote><pre>+ 0 int id = 7
			+ 4 int size
			+ 8 int front_offset // Only recurse into this if non-zero.
			+ 12 int back_offset // Only recurse into this if non-zero.
			+ 16 vector min_bounding_box_point
			+ 28 vector max_bounding_box_point </pre></blockquote>

	[[Category:File Types]]		[[Category:File Types]]

DahBlount at 18:07, 16 April 2022

2022-04-16T18:07:13Z

@@ Line 71: / Line 71: @@
 + 8 vector min_point
 +20 vector max_point</pre></blockquote>
 [[Category:File Types]]

ShivanSpS: /* 3D model data */

2022-02-23T21:48:28Z

3D model data

← Older revision		Revision as of 21:48, 23 February 2022
Line 13:		Line 13:
	<blockquote><pre>+ 0 int id = 0		<blockquote><pre>+ 0 int id = 0
	+ 4 int size</pre></blockquote>		+ 4 int size</pre></blockquote>
	** Note: EOF size ~~is read~~ as ~~0, but is actually 8 (id+~~size).		** Note: EOF chunk lacks the size int after the ID, it should be considered as size 4 due to the rule of other chunks.

	1 - DEFPOINTS - Defines the vertices		1 - DEFPOINTS - Defines the vertices

ShivanSpS: /* 3D model data */

2019-12-06T01:37:36Z

3D model data

← Older revision		Revision as of 01:37, 6 December 2019
Line 8:		Line 8:
	==3D model data==		==3D model data==
	The first byte defines the block now following (0-5, see below). After a block the following byte defines the data of the next block, etc.		The first byte defines the block now following (0-5, see below). After a block the following byte defines the data of the next block, etc.
			[[Media:Bsp_chunk.png]]

	0 - EOF - Means end of tree reached		0 - EOF - Means end of tree reached
	<blockquote><pre>+ 0 int id = 0		<blockquote><pre>+ 0 int id = 0
	+ 4 int size</pre></blockquote>		+ 4 int size</pre></blockquote>
			** Note: EOF size is read as 0, but is actually 8 (id+size).

	1 - DEFPOINTS - Defines the vertices		1 - DEFPOINTS - Defines the vertices
	<blockquote><pre>+ 0 int id = 1		<blockquote><pre>+ 0 int id = 1
Line 20:		Line 23:
	+20 n_verts*char norm_counts		+20 n_verts*char norm_counts
	+offset vertex_data // Each vertex n is a point followed by norm_counts[n] normals.</pre></blockquote>		+offset vertex_data // Each vertex n is a point followed by norm_counts[n] normals.</pre></blockquote>
			** Note: DEFPOINTS is the only type of chunk on bsp_data that could be unaligned. The offset to vertex data must be divisible by 4. This is a mayor cause of bus errors on ARM arch.
	2 - FLATPOLY - Flat (non-textured) polygon		2 - FLATPOLY - Flat (non-textured) polygon
	<blockquote><pre>+ 0 int id = 2		<blockquote><pre>+ 0 int id = 2

The E: Slight correction to reflect actual usage, as opposed to the theory

2010-08-02T18:34:40Z

Slight correction to reflect *actual* usage, as opposed to the theory

← Older revision		Revision as of 18:34, 2 August 2010
Line 44:		Line 44:
	+40 int tmap_num		+40 int tmap_num
	for each vertex, i {		for each vertex, i {
	~~short~~ vertnum[i]		ushort vertnum[i]
	~~short~~ normnum[i]		ushort normnum[i]
	float u[i]		float u[i]
	float v[i]		float v[i]

TopAce: /* Introduction */ style

2010-04-21T21:13:59Z

Introduction: style

← Older revision		Revision as of 21:13, 21 April 2010
Line 2:		Line 2:

	==Introduction==		==Introduction==
	The BSP data in FreeSpace in ~~kinda~~ similar to the Descent 1-3 BSP data (also called IDTA~~). Many deja-vu's here and there :~~). In FreeSpace the BSP data is located in the POF files.		The BSP data in FreeSpace in similar to the Descent 1-3 BSP data (also called IDTA). In FreeSpace, the BSP data is located in the POF files.

	This document was written by John Slagel from Volition Inc., with revisions and bugfixing from Garry Knudson and Francis "Pastel" Avila.		This document was written by John Slagel from Volition Inc., with revisions and bugfixing from Garry Knudson and Francis "Pastel" Avila.

Goober5000: categorize

2009-10-30T02:23:31Z

categorize

← Older revision		Revision as of 02:23, 30 October 2009
Line 67:		Line 67:
	+ 8 vector min_point		+ 8 vector min_point
	+20 vector max_point</pre></blockquote>		+20 vector max_point</pre></blockquote>

			[[Category:File Types]]

BSP data structure - Revision history

Asteroth: /* 1 - DEFPOINTS */

Asteroth at 03:12, 23 April 2022

Asteroth at 06:32, 21 April 2022

Asteroth at 06:31, 21 April 2022

DahBlount at 18:07, 16 April 2022

ShivanSpS: /* 3D model data */

ShivanSpS: /* 3D model data */

The E: Slight correction to reflect *actual* usage, as opposed to the theory

TopAce: /* Introduction */ style

Goober5000: categorize

The E: Slight correction to reflect actual usage, as opposed to the theory