MD5 - Revision history

Corbin at 21:06, 25 May 2016

2016-05-25T21:06:37Z

Corbin: updated for 2.0.0 release

2015-03-12T05:18:56Z

updated for 2.0.0 release

Corbin: Created page with "The MD5 model format comes from id Software's Doom 3 first person shooter, released in August 2004. The mesh data and animation data are separated in distinct files. These are..."

2015-01-27T07:23:39Z

Created page with "The MD5 model format comes from id Software's Doom 3 first person shooter, released in August 2004. The mesh data and animation data are separated in distinct files. These are..."

New page

The MD5 model format comes from id Software's Doom 3 first person shooter, released in August 2004. The mesh data and animation data are separated in distinct files. These are ASCII files and are human readable. Here are some generalities about the MD5 format:

* Model's geometric data are stored in *.md5mesh files;
* Animations are stored in *.md5anim files;
* Supports Skeletal Animation;
* Supports Vertex Skinning;
* Uses quaternions for orientation (in epi/m_quaternion).

MD5 is a work-in-progress and will be available starting with 3DGE 2.x. More information will be covered here as the format becomes available. MD5 will ultimately replace [[MD3]].

Also see [[MD2]] and [[MD3]].

@@ Line 9: / Line 9: @@
 MD5 is a work-in-progress and will be available starting with 3DGE 2.x. More information will be covered here as the format becomes available. MD5 will ultimately replace [[MD3]].
-As of 3DGE 2.0.0, MD5 models are supported, though this release there are a few limitations to adhere to:
+As of 3DGE 2.0.4, MD5 models are fully supported.
-  -this is still sort of incomplete, as there is no MD5 support for weapons (yet)
    +MD2 and MD3 models are still supported as of this release!
-To load MD5 models, just import the MD5mesh and MD5anim into a WAD. DDF naming convention is the same as before. Name both the md5mesh and md5anim the same way (4 letter followed by MD5).
+To load MD5 models, just import the MD5mesh and MD5anim into a WAD. DDF naming convention is the same as before. Name both the md5mesh and md5anim the same way (4 letter followed by MD5). All grouped images need to be defined in [[DDFIMAGES]].
 The models animation system is affected by the interpolation - turning it off will give you choppy animations and other weirdness that is not yet documented.
-Also see [[MD2]] and [[MD3]].
+Also see [[MD2]], [[MD3]], and [[MDL]].

← Older revision		Revision as of 05:18, 12 March 2015
Line 8:		Line 8:

	MD5 is a work-in-progress and will be available starting with 3DGE 2.x. More information will be covered here as the format becomes available. MD5 will ultimately replace [[MD3]].		MD5 is a work-in-progress and will be available starting with 3DGE 2.x. More information will be covered here as the format becomes available. MD5 will ultimately replace [[MD3]].
		+
		+	As of 3DGE 2.0.0, MD5 models are supported, though this release there are a few limitations to adhere to:
		+	-this is still sort of incomplete, as there is no MD5 support for weapons (yet)
		+	-the MD5 loader cannot process skin_img yet, but the engine will warn you about the skins
		+	+MD2 and MD3 models are still supported as of this release!
		+
		+	To load MD5 models, just import the MD5mesh and MD5anim into a WAD. DDF naming convention is the same as before. Name both the md5mesh and md5anim the same way (4 letter followed by MD5).
		+
		+	The models animation system is affected by the interpolation - turning it off will give you choppy animations and other weirdness that is not yet documented.
		+

	Also see [[MD2]] and [[MD3]].		Also see [[MD2]] and [[MD3]].