Animated static objects - Revision history

Baddcog: /* On to animated objects */

2007-09-02T20:23:11Z

On to animated objects

← Older revision		Revision as of 20:23, 2 September 2007
Line 23:		Line 23:
	A drawback to animated objects is that they don't have collision data, the player can walk through them, arrows can be shot through them. This however can be remedied (?) by adding data to the objects .def file. Below is an example of the grandfather clocks .def file.		A drawback to animated objects is that they don't have collision data, the player can walk through them, arrows can be shot through them. This however can be remedied (?) by adding data to the objects .def file. Below is an example of the grandfather clocks .def file.

	~~"combat model~~=1" will make the engine use all polys on a model to calculate collision data. This takes alot of processing power. Using a simple AF model is a better choice, you would use ~~"combat model~~=0" in that instance.		''CombatModel=1'' will make the engine use all polys on a model to calculate collision data. This takes alot of processing power. Using a simple AF model is a better choice, you would use ''CombatModel=0'' in that instance.

	== Code ==		== Code ==

Baddcog: /* On to animated objects */

2007-09-02T20:22:32Z

On to animated objects

← Older revision		Revision as of 20:22, 2 September 2007
Line 22:		Line 22:

	A drawback to animated objects is that they don't have collision data, the player can walk through them, arrows can be shot through them. This however can be remedied (?) by adding data to the objects .def file. Below is an example of the grandfather clocks .def file.		A drawback to animated objects is that they don't have collision data, the player can walk through them, arrows can be shot through them. This however can be remedied (?) by adding data to the objects .def file. Below is an example of the grandfather clocks .def file.

			"combat model=1" will make the engine use all polys on a model to calculate collision data. This takes alot of processing power. Using a simple AF model is a better choice, you would use "combat model=0" in that instance.

	== Code ==		== Code ==

Baddcog: /* Description of object files */

2007-09-02T20:18:39Z

Description of object files

← Older revision		Revision as of 20:18, 2 September 2007
Line 8:		Line 8:
	Static objects whether animated or not need several files to define them.		Static objects whether animated or not need several files to define them.
	*A non-animated object uses an ''.ase'' file (3ds max native) or ''.lwo'' file (Lightwave native) to describe the mesh and which material shader/s it contains. This also contains shadow meshes and collison meshes.		*A non-animated object uses an ''.ase'' file (3ds max native) or ''.lwo'' file (Lightwave native) to describe the mesh and which material shader/s it contains. This also contains shadow meshes and collison meshes.
	*An animated object uses the above mentioned ''.md5mesh'' file for this purpose. (~~wether or not it can contain~~ a shadow ~~or collison~~ data ~~is not yet confirmed - my next project~~)		*An animated object uses the above mentioned ''.md5mesh'' file for this purpose. (I believe a shadow mesh must be weighted to the bones if used; collision models aren't supported, an AF file must be created for collision data)
	*A .mtr file which contains the material shader descriptions (this is referenced by the md5mesh, ase or lwo file)		*A .mtr file which contains the material shader descriptions (this is referenced by the md5mesh, ase or lwo file)
	*Some objects will also have ''[[.def files]]''. This is a deffinition of the object. It defines characteristics such as frobability (can player use it, pick it up?), a list of animations, sounds an object makes, and a bounding box for the object among many other options. If an object has a .def file it will need to be created as an entity in the editor, not a model, although its model can still be referenced in the model viewer.		*Some objects will also have ''[[.def files]]''. This is a deffinition of the object. It defines characteristics such as frobability (can player use it, pick it up?), a list of animations, sounds an object makes, and a bounding box for the object among many other options. If an object has a .def file it will need to be created as an entity in the editor, not a model, although its model can still be referenced in the model viewer.
			*An AF (Articulated Figure) file is required for collision data on an md5.mesh (animated object). AF files are created in the in game console. Go into game mode, hit '''~''', type '''editafs'''. This allows you to attach basic objects (cube, cylinder, ect) to each bone for collision data. You also need to set links and joint types for the AF. The AF editor will create the af file.

	== On to animated objects ==		== On to animated objects ==

Domarius: /* Description of object files */

2007-08-22T07:52:02Z

Description of object files

← Older revision		Revision as of 07:52, 22 August 2007
Line 4:		Line 4:
	Animations can be done in a 3d program such as 3dsMax, [http://www.blender.org/ Blender], Lightwave or Maya and exported to ''md5mesh'' files along with ''md5anim'' files.		Animations can be done in a 3d program such as 3dsMax, [http://www.blender.org/ Blender], Lightwave or Maya and exported to ''md5mesh'' files along with ''md5anim'' files.

	An ~~md5.mesh~~ file contains the object and bones info. Objects need to be an edit mesh with a skin modifier. The skin modifier attaches the bones to the mesh (object). The ~~md5.anim~~ file contains the animation keyframes. Each animation file has it's own ~~md5.anim~~. This is the same as AI use. For instance a city guard would have a city_guard.md5mesh (containing the AI's data and joints [bones]) and many md5anims such as city_guard_attack1.md5anim (which would obviously be an attack anim). Scripts can be used to call up these anims.		An md5mesh file contains the object and bones info. Objects need to be an edit mesh with a skin modifier. The skin modifier attaches the bones to the mesh (object). The md5anim file contains the animation keyframes. Each animation file has it's own md5anim. This is the same as AI use. For instance a city guard would have a city_guard.md5mesh (containing the AI's data and joints [bones]) and many md5anims such as city_guard_attack1.md5anim (which would obviously be an attack anim). Scripts can be used to call up these anims.

	Static objects whether animated or not need several files to define them.		Static objects whether animated or not need several files to define them.

Greebo: formatting

2007-06-03T10:10:43Z

formatting

Show changes

Baddcog at 20:56, 2 June 2007

2007-06-02T20:56:46Z

← Older revision		Revision as of 20:56, 2 June 2007
Line 14:		Line 14:
	*An animated object uses the above mentioned ''.md5mesh'' file for this purpose. (wether or not it can contain a shadow or collison data is not yet confirmed - my next project)		*An animated object uses the above mentioned ''.md5mesh'' file for this purpose. (wether or not it can contain a shadow or collison data is not yet confirmed - my next project)
	*A .mtr file which contains the material shader descriptions (this is referenced by the md5mesh, ase or lwo file)		*A .mtr file which contains the material shader descriptions (this is referenced by the md5mesh, ase or lwo file)
	*Some objects will also have a ''[[.def files]]'' ~~file~~. This is a deffinition of the object. It defines characteristics such as frobability (can player use it, pick it up?), a list of animations, sounds an object makes, and a bounding box for the object among many other options. If an object has a .def file it will need to be created as an entity in the editor, not a model, although its model can still be referenced in the model viewer.		*Some objects will also have ''[[.def files]]''. This is a deffinition of the object. It defines characteristics such as frobability (can player use it, pick it up?), a list of animations, sounds an object makes, and a bounding box for the object among many other options. If an object has a .def file it will need to be created as an entity in the editor, not a model, although its model can still be referenced in the model viewer.

Baddcog at 20:56, 2 June 2007

2007-06-02T20:56:26Z

← Older revision		Revision as of 20:56, 2 June 2007
Line 14:		Line 14:
	*An animated object uses the above mentioned ''.md5mesh'' file for this purpose. (wether or not it can contain a shadow or collison data is not yet confirmed - my next project)		*An animated object uses the above mentioned ''.md5mesh'' file for this purpose. (wether or not it can contain a shadow or collison data is not yet confirmed - my next project)
	*A .mtr file which contains the material shader descriptions (this is referenced by the md5mesh, ase or lwo file)		*A .mtr file which contains the material shader descriptions (this is referenced by the md5mesh, ase or lwo file)
	*Some objects will also have a ''[[.def]]'' file. This is a deffinition of the object. It defines characteristics such as frobability (can player use it, pick it up?), a list of animations, sounds an object makes, and a bounding box for the object among many other options. If an object has a .def file it will need to be created as an entity in the editor, not a model, although its model can still be referenced in the model viewer.		*Some objects will also have a ''[[.def files]]'' file. This is a deffinition of the object. It defines characteristics such as frobability (can player use it, pick it up?), a list of animations, sounds an object makes, and a bounding box for the object among many other options. If an object has a .def file it will need to be created as an entity in the editor, not a model, although its model can still be referenced in the model viewer.

Baddcog at 20:54, 2 June 2007

2007-06-02T20:54:36Z

← Older revision		Revision as of 20:54, 2 June 2007
Line 14:		Line 14:
	*An animated object uses the above mentioned ''.md5mesh'' file for this purpose. (wether or not it can contain a shadow or collison data is not yet confirmed - my next project)		*An animated object uses the above mentioned ''.md5mesh'' file for this purpose. (wether or not it can contain a shadow or collison data is not yet confirmed - my next project)
	*A .mtr file which contains the material shader descriptions (this is referenced by the md5mesh, ase or lwo file)		*A .mtr file which contains the material shader descriptions (this is referenced by the md5mesh, ase or lwo file)
	*Some objects will also have a ''.def'' file. This is a deffinition of the object. It defines characteristics such as frobability (can player use it, pick it up?), a list of animations, sounds an object makes, and a bounding box for the object among many other options. If an object has a .def file it will need to be created as an entity in the editor, not a model, although its model can still be referenced in the model viewer.		*Some objects will also have a ''[[.def]]'' file. This is a deffinition of the object. It defines characteristics such as frobability (can player use it, pick it up?), a list of animations, sounds an object makes, and a bounding box for the object among many other options. If an object has a .def file it will need to be created as an entity in the editor, not a model, although its model can still be referenced in the model viewer.

Baddcog at 19:09, 2 June 2007

2007-06-02T19:09:25Z

← Older revision		Revision as of 19:09, 2 June 2007
Line 106:		Line 106:
	== Other info ==		== Other info ==

	The clocks material file has wood as a material type. The description of wood in the .~~mrt~~ file is what		The clocks material file has wood as a material type. The description of wood in the .mtr file is what
	causes arrows to stick to it and to sound like wood.		causes arrows to stick to it and to make it sound like wood.

	Go in game, pull down console and type		Go in game, pull down console and type

Baddcog at 19:04, 2 June 2007

2007-06-02T19:04:37Z

← Older revision		Revision as of 19:04, 2 June 2007
Line 106:		Line 106:
	== Other info ==		== Other info ==

	~~the~~ clocks material file has wood ~~of course~~. The description of wood in the .mrt file is ~~waht~~ causes arrows to stick to it and to sound like wood.		The clocks material file has wood as a material type. The description of wood in the .mrt file is what
			causes arrows to stick to it and to sound like wood.

			Go in game, pull down console and type
			g_showcollisionmodels

			The red box drawn around the object is the player collision model, the blue box is the combat model.

	Der_tons md5 model exporter[http://www.doom3world.org/phpbb2/viewtopic.php?t=5474&sid=b60f18bf1d3f2fbe8f6fafa138683f35] works great for exporting the model/anim. He has several versions. I have only used the 3dsMax one. There are other useful tools in that list.		Der_tons md5 model exporter[http://www.doom3world.org/phpbb2/viewtopic.php?t=5474&sid=b60f18bf1d3f2fbe8f6fafa138683f35] works great for exporting the model/anim. He has several versions. I have only used the 3dsMax one. There are other useful tools in that list.