MDX - Revision history

FREDZ: /* SFX ENTRY */

2025-04-09T19:12:37Z

SFX ENTRY

← Older revision		Revision as of 19:12, 9 April 2025
Line 241:		Line 241:
	</syntaxhighlight>		</syntaxhighlight>

	'''SfxFrames[128]''': contains ~~'''~~1024 bits / 128 bytes~~'''~~, which correspond to ~~'''~~1024 animation frames maximum~~'''~~. Each bit represents a single animation frame:		'''SfxFrames[128]''': contains 1024 bits / 128 bytes, which correspond to 1024 animation frames maximum. Each bit represents a single animation frame:

	* If a bit is set to ~~'''~~1~~'''~~, the SFX will be shown in that frame.		* If a bit is set to 1, the SFX will be shown in that frame.
	* If a bit is set to ~~'''~~0~~'''~~, the SFX will not be shown.		* If a bit is set to 0, the SFX will not be shown.

	For example:		For example:
	* To display the SFX in ~~'''~~all 1024 animation frames~~'''~~, set all ~~'''~~1024 bits~~'''~~ to ~~'''~~1~~'''~~.		* To display the SFX in all 1024 animation frames, set all 1024 bits to 1.
	* To disable the SFX entirely, set all ~~'''~~1024 bits~~'''~~ to ~~'''~~0~~'''~~.		* To disable the SFX entirely, set all 1024 bits to 0.

	While setting individual bits is simple, encoding and decoding the ~~'''~~char~~'''~~ array to determine the exact frame range where the SFX will be shown can be complex. This process isn’t necessary for importing ~~'''~~.mdx~~'''~~ files, but it is ~~'''~~essential~~'''~~ for exporting them.		While setting individual bits is simple, encoding and decoding the char array to determine the exact frame range where the SFX will be shown can be complex. This process isn’t necessary for importing .mdx files, but it is essential for exporting them.

	== BOUNDING BOX LIST ==		== BOUNDING BOX LIST ==

FREDZ: /* SFX ENTRY */

2025-04-09T00:24:59Z

SFX ENTRY

← Older revision		Revision as of 00:24, 9 April 2025
Line 237:		Line 237:
	int define_no;		int define_no;
	int vertexindex;		int vertexindex;
	char SfxFrames[~~1024~~];		char SfxFrames[128];
	} SfxEntry_t;		} SfxEntry_t;
	</syntaxhighlight>		</syntaxhighlight>

	* '''SfxFrames[~~1024~~]''': contains ~~512~~ bits/64 bytes which correspond to ~~512~~ animation frames maximum. If a bit ~~in those 512 bits~~ is set to 1 the ~~sfx~~ will be shown on that frame. If ~~the~~ bit is set to 0 the ~~sfx~~ will not be shown. For example ~~if you wanted to show~~ the ~~sfx~~ in all ~~512~~ animation frames ~~you would~~ set all ~~the 512~~ bits to 1. ~~If you don't want to show any sfx then you would~~ set all ~~512~~ bits to ~~zero~~. ~~Simple. The hard bit~~ is encoding and decoding the char array ~~so that we know~~ the frame range ~~for which~~ the ~~sfx~~ will be shown ~~for~~. This ~~is not neccessary~~ for importing mdx files but it is essential for exporting them.		'''SfxFrames[128]''': contains '''1024 bits / 128 bytes''', which correspond to '''1024 animation frames maximum'''. Each bit represents a single animation frame:

			* If a bit is set to '''1''', the SFX will be shown in that frame.
			* If a bit is set to '''0''', the SFX will not be shown.

			For example:
			* To display the SFX in '''all 1024 animation frames''', set all '''1024 bits''' to '''1'''.
			* To disable the SFX entirely, set all '''1024 bits''' to '''0'''.

			While setting individual bits is simple, encoding and decoding the '''char''' array to determine the exact frame range where the SFX will be shown can be complex. This process isn’t necessary for importing '''.mdx''' files, but it is '''essential''' for exporting them.

	== BOUNDING BOX LIST ==		== BOUNDING BOX LIST ==

FREDZ: /* SFX ENTRY */

2025-04-08T23:46:11Z

SFX ENTRY

← Older revision		Revision as of 23:46, 8 April 2025
Line 237:		Line 237:
	int define_no;		int define_no;
	int vertexindex;		int vertexindex;
	char SfxFrames[64];		char SfxFrames[1024];
	} SfxEntry_t;		} SfxEntry_t;
	</syntaxhighlight>		</syntaxhighlight>

	* '''SfxFrames[64]''': contains 512 bits/64 bytes which correspond to 512 animation frames maximum. If a bit in those 512 bits is set to 1 the sfx will be shown on that frame. If the bit is set to 0 the sfx will not be shown. For example if you wanted to show the sfx in all 512 animation frames you would set all the 512 bits to 1. If you don't want to show any sfx then you would set all 512 bits to zero. Simple. The hard bit is encoding and decoding the char array so that we know the frame range for which the sfx will be shown for. This is not neccessary for importing mdx files but it is essential for exporting them.		* '''SfxFrames[1024]''': contains 512 bits/64 bytes which correspond to 512 animation frames maximum. If a bit in those 512 bits is set to 1 the sfx will be shown on that frame. If the bit is set to 0 the sfx will not be shown. For example if you wanted to show the sfx in all 512 animation frames you would set all the 512 bits to 1. If you don't want to show any sfx then you would set all 512 bits to zero. Simple. The hard bit is encoding and decoding the char array so that we know the frame range for which the sfx will be shown for. This is not neccessary for importing mdx files but it is essential for exporting them.

	== BOUNDING BOX LIST ==		== BOUNDING BOX LIST ==

FREDZ: /* MAXIMUMS */

2025-04-08T23:43:22Z

MAXIMUMS

← Older revision		Revision as of 23:43, 8 April 2025
Line 275:		Line 275:
	* [[#TRIANGLES\|Triangles]]: 4096		* [[#TRIANGLES\|Triangles]]: 4096
	* Vertices: 2048		* Vertices: 2048
	* [[#FRAMES\|Frames]]: ~~512~~		* [[#FRAMES\|Frames]]: 1024
	* [[#SKINS\|Skins]]: 32		* [[#SKINS\|Skins]]: 32

	Kingpin is a trademark of [http://www.gmistudios.com/ Xatrix/Gray Matter]. All trademarks are properties of their respective owners.		Kingpin is a trademark of [http://www.gmistudios.com/ Xatrix/Gray Matter]. All trademarks are properties of their respective owners.

FREDZ at 12:24, 21 March 2025

2025-03-21T12:24:14Z

← Older revision		Revision as of 12:24, 21 March 2025
Line 138:		Line 138:

	== GL COMMANDS ==		== GL COMMANDS ==
	At offsetGlCommands bytes into the file, there is the gl command list, which is made up of a series of numGlCommands int's and float's, organized into groups. Each group starts with an int (TrisTypeNum).		At offsetGlCommands bytes into the file, there is the gl command list, which is made up of a series of numGlCommands int's and float's, organized into groups. Each group starts with an int (TrisTypeNum).
	* If it is positive, it is followed by another int (SubObjectID) and that (first int) many glCommandVertex_t structures, which form a triangle strip.
	* If it is negative, it is followed by another int (SubObjectID) and -x glCommandVertex_t structures, which form a triangle fan.		* If it is positive, it is followed by another int (SubObjectID) and that (first int) many glCommandVertex_t structures, which form a triangle strip.
			* If it is negative, it is followed by another int (SubObjectID) and -x glCommandVertex_t structures, which form a triangle fan.
	* A 0 indicates the end of the list.		* A 0 indicates the end of the list.

FREDZ: /* MAXIMUMS */

2025-03-21T02:10:47Z

MAXIMUMS

← Older revision		Revision as of 02:10, 21 March 2025
Line 273:		Line 273:
	Kingpin has some pre-defined limits, so that dynamic memory does not need to be used. You can use these to your advantage to speed up loading if you want.		Kingpin has some pre-defined limits, so that dynamic memory does not need to be used. You can use these to your advantage to speed up loading if you want.
	* [[#TRIANGLES\|Triangles]]: 4096		* [[#TRIANGLES\|Triangles]]: 4096
	* ~~[[#FRAMES\|~~Vertices]]: 2048		* Vertices: 2048
	* [[#FRAMES\|Frames]]: 512		* [[#FRAMES\|Frames]]: 512
	* [[#SKINS\|Skins]]: 32		* [[#SKINS\|Skins]]: 32

	Kingpin is a trademark of [http://www.gmistudios.com/ Xatrix/Gray Matter]. All trademarks are properties of their respective owners.		Kingpin is a trademark of [http://www.gmistudios.com/ Xatrix/Gray Matter]. All trademarks are properties of their respective owners.

FREDZ: /* MAXIMUMS */

2025-03-21T02:09:55Z

MAXIMUMS

← Older revision		Revision as of 02:09, 21 March 2025
Line 273:		Line 273:
	Kingpin has some pre-defined limits, so that dynamic memory does not need to be used. You can use these to your advantage to speed up loading if you want.		Kingpin has some pre-defined limits, so that dynamic memory does not need to be used. You can use these to your advantage to speed up loading if you want.
	* [[#TRIANGLES\|Triangles]]: 4096		* [[#TRIANGLES\|Triangles]]: 4096
	* [[#~~triangleVertex~~\|Vertices]]: 2048		* [[#FRAMES\|Vertices]]: 2048
	* [[#FRAMES\|Frames]]: 512		* [[#FRAMES\|Frames]]: 512
	* [[#SKINS\|Skins]]: 32		* [[#SKINS\|Skins]]: 32

	Kingpin is a trademark of [http://www.gmistudios.com/ Xatrix/Gray Matter]. All trademarks are properties of their respective owners.		Kingpin is a trademark of [http://www.gmistudios.com/ Xatrix/Gray Matter]. All trademarks are properties of their respective owners.

FREDZ at 01:46, 21 March 2025

2025-03-21T01:46:35Z

← Older revision		Revision as of 01:46, 21 March 2025
Line 1:		Line 1:
	<center>~~'''~~<~~big~~>.mdx File Format Specification</~~big~~>~~'''~~</~~center~~>		<p style="text-align: center;" align="center"><span style="font-size: x-large;"><strong>.mdx File Format Specification</strong></span><br>
	<~~center~~>'''by''' [mailto:tical@kingpin.com '''TiCaL''']</~~center~~>		'''by''' [mailto:tical@kingpin.com '''TiCaL''']</p>

	== INTRO ==		== INTRO ==

FREDZ: /* GL COMMANDS */

2025-03-21T01:44:22Z

GL COMMANDS

← Older revision		Revision as of 01:44, 21 March 2025
Line 138:		Line 138:

	== GL COMMANDS ==		== GL COMMANDS ==
	At ~~[[#model_offsetGlCommands\|~~offsetGlCommands]] bytes into the file, there is the GL command list, which is made up of a series of ~~[[#model_numGlCommands\|~~numGlCommands~~]] ints~~ and ~~floats~~, organized into groups. Each group starts with an int (TrisTypeNum).		At offsetGlCommands bytes into the file, there is the gl command list, which is made up of a series of numGlCommands int's and float's, organized into groups. Each group starts with an int (TrisTypeNum).
	* If positive, it is followed by another int (SubObjectID) and that (first int) many ~~[[#glCommandVertex\|~~glCommandVertex_t]] structures, which form a triangle strip.		* If it is positive, it is followed by another int (SubObjectID) and that (first int) many glCommandVertex_t structures, which form a triangle strip.
	* If negative, it is followed by another int (SubObjectID) and -x ~~[[#glCommandVertex\|~~glCommandVertex_t]] structures, which form a triangle fan.		* If it is negative, it is followed by another int (SubObjectID) and -x glCommandVertex_t structures, which form a triangle fan.
	* A 0 indicates the end of the list.		* A 0 indicates the end of the list.

	The list is an optimized way of issuing commands when rendering with [http://www.opengl.org OpenGL].		The list is an optimized way of issuing commands when rendering with [http://www.opengl.org OpenGL].
Line 164:		Line 164:
	</syntaxhighlight>		</syntaxhighlight>

	* '''s, t''': These two floats are used to map a vertex onto a skin. The range for ~~'''~~s~~'''~~ and ~~'''~~t~~'''~~ is 0.0 to 1.0. Note that the ranges ~~differ from those~~ in the ~~[[#textureCoordinate\|~~textureCoordinate_t]] structure. They are stored as floats because that's ~~how~~ Kingpin passes them to OpenGL.		* '''s, t''': These two floats are used to map a vertex onto a skin. The horizontal axis position is given by s, and the vertical axis position is given by t. The range for s and for t is 0.0 to 1.0. Note that the ranges are different than in the textureCoordinate_t structure. They are stored as floats here because that's the way Kingpin passes them to [http://www.opengl.org OpenGL].
	* '''SubObjectID''': Integer possibly specifying the sub-object's ID.		* '''SubObjectID''': Integer possibly specifying the sub-object's ID.
	* '''vertexIndex''': Index into the array of ~~[[#frame_vertices\|~~vertices]] stored in each ~~[[#~~frame~~\|frame]]~~.		* '''vertexIndex''': Index into the array of vertices stored in each frame.

	== VERTEX INFO ==		== VERTEX INFO ==

FREDZ: /* VERTEX INFO */

2025-03-21T01:40:25Z

VERTEX INFO

← Older revision		Revision as of 01:40, 21 March 2025
Line 169:		Line 169:

	== VERTEX INFO ==		== VERTEX INFO ==
	At ~~[[#model_offsetVertexInfo\|~~offsetVertexInfo]] bytes into the file, there is the vertex info list, which is made up of a series of ~~[[#model_numVertices\|~~numVertices~~]] ints~~, all grouped by the sub-object they belong to.		At offsetVertexInfo bytes into the file, there is the vertex info list, which is made up of a series of numVertices int's, all of which are grouped by the sub-object they belong to. If a vertex is in sub-object 1 then its marked as 1, if its in sub-object 2 then its marked as 2 etc etc. First all the vertices from the first sub-object are marked then the rest or the vertices from other sub-objects follow. For example if the first sub-object has 4 vertices and the second sub-object has 2 vertices the HEX code in the mdx would look like this:

	~~For example, if the first sub-object has 4 vertices and the second sub-object has 2 vertices, the HEX code in the MDX would look like this:~~
	'''0100 0000 0100 0000 0100 0000 0100 0000 0200 0000 0200 0000'''		'''0100 0000 0100 0000 0100 0000 0100 0000 0200 0000 0200 0000'''

			This shows there are 4 one's and 2 two's integers specifying that the first for vertices are part of sub-object 1 and that the last 2 vertices are part of sub-object 2. Lets say there are 4 sub-objects who all have 2 vertices each. Then the HEX code would look like this.

			'''0100 0000 0100 0000 0200 0000 0200 0000 0300 0000 0300 0000 0400 0000 0400 0000'''

	<syntaxhighlight lang="c">		<syntaxhighlight lang="c">
Line 180:		Line 183:
	} SubObjectsVerts_t;		} SubObjectsVerts_t;
	</syntaxhighlight>		</syntaxhighlight>
			* '''Object[numVertexInObject]''': is an array of int's where numVertexInObject is the number of vertices in the sub-object. All the values (int's) in one array should all have the same value which corresponds to the sub-object number.
	<syntaxhighlight lang="c">		<syntaxhighlight lang="c">
	typedef struct		typedef struct
Line 187:		Line 190:
	} VertexInfo_t;		} VertexInfo_t;
	</syntaxhighlight>		</syntaxhighlight>
			* '''VertexInfo[numSubObjects]''': is an array of SubObjectsVerts_t structs defined above. The number of structs in the VertexInfo array corresponds to the numSubObjects.

	~~The `VertexInfo[numSubObjects]` array groups vertex info for each sub-object. All values in~~ an ~~array correspond~~ to ~~the sub-object number~~.		I'm not sure if there is an easier way to define this structure....i have a complicated mind ;)

	== SFX DEFINITION LIST ==		== SFX DEFINITION LIST ==