Springheel's Rigging Workflow - Revision history

Thebigh: /* Create the model */ -typo

2024-11-11T21:17:10Z

Create the model: -typo

← Older revision		Revision as of 21:17, 11 November 2024
Line 5:		Line 5:
	== Create the model ==		== Create the model ==

	I use Lightwave 8.0 to work on character meshes. I'm not a proficient enough modeler to make high poly characters from scratch, so I wind up using a lot of bits and pieces of existing models (Oddity's and D3). Each character is roughly 4000-5000 ~~ploys~~ with a shadowmesh that is half that. Each character has about seven or eight different submeshes (divided by layers in LW).		I use Lightwave 8.0 to work on character meshes. I'm not a proficient enough modeler to make high poly characters from scratch, so I wind up using a lot of bits and pieces of existing models (Oddity's and D3). Each character is roughly 4000-5000 polys with a shadowmesh that is half that. Each character has about seven or eight different submeshes (divided by layers in LW).

	'''Important things to remember''': The md5mesh format is less forgiving than regular .lwo models, so a few extra things need to be done. A character model can (and usually does) have multiple layers. A single layer can reference only one UVmap. A single poly or vert cannot be mapped onto two different UVmaps, or the texture will be distorted. Verts can only appear in one spot on the UVmap. If you have three verts welded together, and they're at different coordinates, textures will be smeared. Unweld the verts and then weld the verts at each coordinate separately. You'll still see a bit of a seam but it won't be as bad. Meshes that meet at sharp angles may need to be on separate layers to avoid strange black shadows in game.		'''Important things to remember''': The md5mesh format is less forgiving than regular .lwo models, so a few extra things need to be done. A character model can (and usually does) have multiple layers. A single layer can reference only one UVmap. A single poly or vert cannot be mapped onto two different UVmaps, or the texture will be distorted. Verts can only appear in one spot on the UVmap. If you have three verts welded together, and they're at different coordinates, textures will be smeared. Unweld the verts and then weld the verts at each coordinate separately. You'll still see a bit of a seam but it won't be as bad. Meshes that meet at sharp angles may need to be on separate layers to avoid strange black shadows in game.

Petike: typo

2018-10-21T00:49:09Z

typo

← Older revision		Revision as of 00:49, 21 October 2018
Line 46:		Line 46:

	[[Category:Animation]]		[[Category:Animation]]
	[[Category:Animation ~~Tutorial~~]]		[[Category:Animation Tutorials]]

Petike: adding category tag

2018-10-20T05:11:39Z

adding category tag

← Older revision		Revision as of 05:11, 20 October 2018
Line 44:		Line 44:

	addoptions -keep right_knee_dummy left_knee_dummy (etc)		addoptions -keep right_knee_dummy left_knee_dummy (etc)

			[[Category:Animation]]
			[[Category:Animation Tutorial]]

Springheel: /* Exporting to Md5Mesh */

2011-08-25T14:22:12Z

Exporting to Md5Mesh

← Older revision		Revision as of 14:22, 25 August 2011
Line 40:		Line 40:

	Error "expecting to find weight but found }" generally means that the mesh references a non-existent joint. This can easily happen when copying character partss that are weighted for a different skeleton.		Error "expecting to find weight but found }" generally means that the mesh references a non-existent joint. This can easily happen when copying character partss that are weighted for a different skeleton.

			Maya will cull any joints that have nothing weighted to them during the export process. You need to add a line to the def file telling it to keep those joints:

			addoptions -keep right_knee_dummy left_knee_dummy (etc)

Springheel: /* Weighting */

2011-08-22T20:44:29Z

Weighting

← Older revision		Revision as of 20:44, 22 August 2011
Line 26:		Line 26:
	Once the skeleton is complete, Delete History and Freeze Transformation on it as well.		Once the skeleton is complete, Delete History and Freeze Transformation on it as well.

	=== Weighting ===		== Weighting ==

	=== Weighting in Maya ===		=== Weighting in Maya ===

Springheel at 20:44, 22 August 2011

2011-08-22T20:44:11Z

← Older revision		Revision as of 20:44, 22 August 2011
Line 11:		Line 11:
	== Create the skeleton ==		== Create the skeleton ==

	''If using an existing skeleton (like the default humanoid skeleton used for most characters), skip this section.''		''If using an existing skeleton (like the default humanoid skeleton used for most characters), skip this section and go to Weighting.''

	TDM human characters share the same skeleton so they can also share animations. Same with heads. New creatures, like ravens or steambeasts, need their own skeleton.		TDM human characters share the same skeleton so they can also share animations. Same with heads. New creatures, like ravens or steambeasts, need their own skeleton.
Line 25:		Line 25:

	Once the skeleton is complete, Delete History and Freeze Transformation on it as well.		Once the skeleton is complete, Delete History and Freeze Transformation on it as well.

			=== Weighting ===

			=== Weighting in Maya ===

			If I'm creating a new skeleton, I have to weight the rig in Maya. This is generally done by using a paint tool, though you can select individual verts and use the Component Editor to give them specific values (if you know Maya better than I do this can probably be just as fast as LW).


			=== Weighting in LW ===

			In LW, weighting is done by selecting verts and assigning them to a specific joint with the New Weight option.

	== Exporting to Md5Mesh ==		== Exporting to Md5Mesh ==

	Error "expecting to find weight but found }" generally means that the mesh references a non-existent joint. This can easily happen when copying character partss that are weighted for a different skeleton.		Error "expecting to find weight but found }" generally means that the mesh references a non-existent joint. This can easily happen when copying character partss that are weighted for a different skeleton.

Springheel: /* Importing Model */

2011-08-22T20:38:05Z

Importing Model

← Older revision		Revision as of 20:38, 22 August 2011
Line 18:		Line 18:

	=== Importing Model ===		=== Importing Model ===
	First, I have to save the .lwo model into a format Maya can read. DO NOT use the built-in Lightwave exporter. It doesn't export the UVmap, which will mess things up later (you'll get an odd error when trying to export the model to md5mesh format). Instead, I use Deep Exploration to save the model with UVmap intact. If the model is just for visual reference, I usually compress the model into a single layer at this point~~. For something simple like the raven~~, ~~I didn~~'t ~~bother~~.		First, I have to save the .lwo model into a format Maya can read. DO NOT use the built-in Lightwave exporter. It doesn't export the UVmap, which will mess things up later (you'll get an odd error when trying to export the model to md5mesh format). Instead, I use Deep Exploration to save the model with UVmap intact. If the model is just for visual reference, I usually compress the model into a single layer at this point for easier selection, though this isn't actually necessary.

	The model needs to be resting on the XZ plane, facing X, with Y up. Once you've rotated the model the way you want it, you need to Delete History and Freeze Transformations. The latter is particularly important, because if the mesh has any rotation values, it will mess up its position when you load it in game (I had a raven that was sideways for the longest time before finding out the problem).		The model needs to be resting on the XZ plane, facing X, with Y up. Once you've rotated the model the way you want it, you need to Delete History and Freeze Transformations. The latter is particularly important, because if the mesh has any rotation values, it will mess up its position when you load it in game (I had a raven that was sideways in game for the longest time before finding out the problem).

	At this point I start creating the chains in the skeleton. Don't forget an origin bone that rests exactly at 0,0,0. The origin needs to be at the top of the join hierarchy. Follow the Maya tutorials for making joint chains.		At this point I start creating the chains in the skeleton. Don't forget an origin bone that rests exactly at 0,0,0. The origin needs to be at the top of the join hierarchy. Follow the Maya tutorials for making joint chains. Give some thought to which chains will belong to the leg channel, and which to the torso.

	Once the skeleton is complete, Delete History and Freeze Transformation on it as well.		Once the skeleton is complete, Delete History and Freeze Transformation on it as well.

Springheel: /* Importing Model */

2011-08-22T20:36:26Z

Importing Model

← Older revision		Revision as of 20:36, 22 August 2011
Line 18:		Line 18:

	=== Importing Model ===		=== Importing Model ===
	First, I have to save the .lwo model into a format Maya can read. DO NOT use the built-in Lightwave exporter. It doesn't export the UVmap, which will mess things up later. Instead, I use Deep Exploration to save the model with UVmap intact. If the model is just for visual reference, I usually compress the model into a single layer at this point. For something simple like the raven, I didn't bother.		First, I have to save the .lwo model into a format Maya can read. DO NOT use the built-in Lightwave exporter. It doesn't export the UVmap, which will mess things up later (you'll get an odd error when trying to export the model to md5mesh format). Instead, I use Deep Exploration to save the model with UVmap intact. If the model is just for visual reference, I usually compress the model into a single layer at this point. For something simple like the raven, I didn't bother.

	The model needs to be resting on the XZ plane, facing X, with Y up. Once you've rotated the model the way you want it, you need to Delete History and Freeze Transformations. The latter is particularly important, because if the mesh has any rotation values, it will mess up its position when you load it in game (I had a raven that was sideways for the longest time before finding out the problem).		The model needs to be resting on the XZ plane, facing X, with Y up. Once you've rotated the model the way you want it, you need to Delete History and Freeze Transformations. The latter is particularly important, because if the mesh has any rotation values, it will mess up its position when you load it in game (I had a raven that was sideways for the longest time before finding out the problem).

Springheel: /* Create the model */

2011-08-22T20:35:30Z

Create the model

← Older revision		Revision as of 20:35, 22 August 2011
Line 5:		Line 5:
	== Create the model ==		== Create the model ==

	I use Lightwave 8.0 to work on character meshes. I'm not a proficient enough modeler to make high poly characters from scratch, so I ~~usually put together~~ bits and pieces ~~scavenged from Doom3~~ and ~~models created for TDM~~ by ~~Oddity~~.		I use Lightwave 8.0 to work on character meshes. I'm not a proficient enough modeler to make high poly characters from scratch, so I wind up using a lot of bits and pieces of existing models (Oddity's and D3). Each character is roughly 4000-5000 ploys with a shadowmesh that is half that. Each character has about seven or eight different submeshes (divided by layers in LW).

	'''Important things to remember''': The md5mesh format is less forgiving than regular .lwo models, so a few extra things need to be done. A character model can (and usually does) have multiple layers. A single layer can reference only ~~one material and~~ one UVmap. A single poly or vert cannot be mapped onto two different UVmaps, or the texture will be distorted. Meshes that meet at sharp angles may need to be on separate layers to avoid strange black shadows in game.		'''Important things to remember''': The md5mesh format is less forgiving than regular .lwo models, so a few extra things need to be done. A character model can (and usually does) have multiple layers. A single layer can reference only one UVmap. A single poly or vert cannot be mapped onto two different UVmaps, or the texture will be distorted. Verts can only appear in one spot on the UVmap. If you have three verts welded together, and they're at different coordinates, textures will be smeared. Unweld the verts and then weld the verts at each coordinate separately. You'll still see a bit of a seam but it won't be as bad. Meshes that meet at sharp angles may need to be on separate layers to avoid strange black shadows in game.

	== Create the skeleton ==		== Create the skeleton ==

Springheel: /* Create the skeleton */

2011-08-16T21:22:04Z

Create the skeleton

← Older revision		Revision as of 21:22, 16 August 2011
Line 17:		Line 17:
	I use Maya 7.0 to create skeletons.		I use Maya 7.0 to create skeletons.

	First, I have to save the .lwo model into a format Maya can read. DO NOT use the built-in Lightwave exporter. It doesn't export the UVmap, which will mess things up later. Instead, I use Deep Exploration to save the model with UVmap intact. I usually compress the model into a single layer at this point.		=== Importing Model ===
			First, I have to save the .lwo model into a format Maya can read. DO NOT use the built-in Lightwave exporter. It doesn't export the UVmap, which will mess things up later. Instead, I use Deep Exploration to save the model with UVmap intact. If the model is just for visual reference, I usually compress the model into a single layer at this point. For something simple like the raven, I didn't bother.

			The model needs to be resting on the XZ plane, facing X, with Y up. Once you've rotated the model the way you want it, you need to Delete History and Freeze Transformations. The latter is particularly important, because if the mesh has any rotation values, it will mess up its position when you load it in game (I had a raven that was sideways for the longest time before finding out the problem).

			At this point I start creating the chains in the skeleton. Don't forget an origin bone that rests exactly at 0,0,0. The origin needs to be at the top of the join hierarchy. Follow the Maya tutorials for making joint chains.

			Once the skeleton is complete, Delete History and Freeze Transformation on it as well.

	== Exporting to Md5Mesh ==		== Exporting to Md5Mesh ==

	Error "expecting to find weight but found }" generally means that the mesh references a non-existent joint. This can easily happen when copying character partss that are weighted for a different skeleton.		Error "expecting to find weight but found }" generally means that the mesh references a non-existent joint. This can easily happen when copying character partss that are weighted for a different skeleton.