Difference between revisions of "OldSiteResourcesQuake3ModelManual"
(Talk) |
EricChadwick (Talk | contribs) (cleanup: template, headings, indents, category) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Template:Archive}} | |
| − | + | ||
| − | + | ||
| − | + | = Putting New Models in Quake III Arena = | |
| − | + | ||
| + | : Based on original notes by Paul Steed | ||
| + | : Edited by Paul Jaquays | ||
| + | : Edited 12/22/99 by ps | ||
The purpose of this document is to explain how to set up a model for Quake 3 Arena, create the necessary animation and conversion files, and then export it into the MD3 format required by the game. It is intended to be informative only and not a tutorial on building or animating models. | The purpose of this document is to explain how to set up a model for Quake 3 Arena, create the necessary animation and conversion files, and then export it into the MD3 format required by the game. It is intended to be informative only and not a tutorial on building or animating models. | ||
| Line 10: | Line 11: | ||
The player models for Quake III Arena were built using the commercial modeling software, 3D Studio Max R2.5 (3ds Max) by Kinetix. These models were then animated using Physique and Biped, components of a plugin for 3dsMax called Character Studio (also by Kinetix). The following instructions assume that you will model and animate with 3dsMax and Character Studio. | The player models for Quake III Arena were built using the commercial modeling software, 3D Studio Max R2.5 (3ds Max) by Kinetix. These models were then animated using Physique and Biped, components of a plugin for 3dsMax called Character Studio (also by Kinetix). The following instructions assume that you will model and animate with 3dsMax and Character Studio. | ||
| − | + | == 1. Setting up the Files == | |
Begin in your ''Quake3'' directory. If you don’t have one already, create a ''baseq3'' directory. Inside the ''baseq3'' directory, create a ''models'' directory. Inside the models directory, create a players directory. Inside the players directory, create a directory with the name of your model (we will use [character] in this document to represent information requiring the name of the model). It is generally a good idea to create a ‘work’ directory under [character] so that the [character] directory itself remains uncluttered. Place all versions of your model and temp textures here, saving the [character] directory purely for the finished model files. | Begin in your ''Quake3'' directory. If you don’t have one already, create a ''baseq3'' directory. Inside the ''baseq3'' directory, create a ''models'' directory. Inside the models directory, create a players directory. Inside the players directory, create a directory with the name of your model (we will use [character] in this document to represent information requiring the name of the model). It is generally a good idea to create a ‘work’ directory under [character] so that the [character] directory itself remains uncluttered. Place all versions of your model and temp textures here, saving the [character] directory purely for the finished model files. | ||
| − | + | == 2. Building and Naming the Mesh == | |
The mesh should be built keeping in mind the game engine needs three distinct body part grouping: the head, the upper body, and the lower body. These groupings can consist of different parts or sub-objects, but keep in mind too many sub-objects does impact performance and game play speed. A good rule of thumb is to consolidate your objects (i.e. attach them to each other) as long as they remain a part of a major group. For example, you decide to create a character that has its arms as separate objects for easier animation. Unless the arms or torso has different textures assigned to them go ahead and attach the arms to the torso. It may be more difficult to assign the vertices to the biped skeleton later on, but the efficiency of the model is much better. However, if you must keep the limbs detached for unique shader assignment then keep the following naming conventions in mind: | The mesh should be built keeping in mind the game engine needs three distinct body part grouping: the head, the upper body, and the lower body. These groupings can consist of different parts or sub-objects, but keep in mind too many sub-objects does impact performance and game play speed. A good rule of thumb is to consolidate your objects (i.e. attach them to each other) as long as they remain a part of a major group. For example, you decide to create a character that has its arms as separate objects for easier animation. Unless the arms or torso has different textures assigned to them go ahead and attach the arms to the torso. It may be more difficult to assign the vertices to the biped skeleton later on, but the efficiency of the model is much better. However, if you must keep the limbs detached for unique shader assignment then keep the following naming conventions in mind: | ||
| − | = 2.1 Head Geometry = | + | === 2.1 Head Geometry === |
All head geometry needs to begin with lower case 'H_' (h_head, h_glasses, h_hat, etc...). Keep in mind that the head has no animations itself other than to respond to player mouse-look input. | All head geometry needs to begin with lower case 'H_' (h_head, h_glasses, h_hat, etc...). Keep in mind that the head has no animations itself other than to respond to player mouse-look input. | ||
| − | = 2.2 Upper Body Geometry = | + | === 2.2 Upper Body Geometry === |
All upper body geometry needs to begin with lower case 'U_' (u_torso, u_arms, u_abdomen, etc.) This is your model’s torso and arms. The individual animations for the upper body are listed below. | All upper body geometry needs to begin with lower case 'U_' (u_torso, u_arms, u_abdomen, etc.) This is your model’s torso and arms. The individual animations for the upper body are listed below. | ||
| − | = 2.3 Lower Body Geometry = | + | === 2.3 Lower Body Geometry === |
All lower body geometry begins with lower case 'L_' (l_hips, l_legs, l_lfoot, l_rfoot, etc...). This is your model’s buttocks, legs and feet. The individual animations for the upper body are listed below. | All lower body geometry begins with lower case 'L_' (l_hips, l_legs, l_lfoot, l_rfoot, etc...). This is your model’s buttocks, legs and feet. The individual animations for the upper body are listed below. | ||
| − | = 2.4 Tags = | + | === 2.4 Tags === |
Tags are connection points for other model parts and represent the limited hierarchical system of the game. They include links between the three character body parts and the weapons. Keep in mind that these tags are representations of geometry so they can be animated to represent that geometry. For example, tag_head represents the head, tag_torso represents the torso and tag_weapon represents the weapon. This is important to understand since for example, any time the character is performing a locomotive animation, the upper body can and will animate independently of the lower body, using the relative position of the tag as a base or ‘home’ position. The tags for the body parts and weapons are named tag_weapon, tag_torso and tag_head. | Tags are connection points for other model parts and represent the limited hierarchical system of the game. They include links between the three character body parts and the weapons. Keep in mind that these tags are representations of geometry so they can be animated to represent that geometry. For example, tag_head represents the head, tag_torso represents the torso and tag_weapon represents the weapon. This is important to understand since for example, any time the character is performing a locomotive animation, the upper body can and will animate independently of the lower body, using the relative position of the tag as a base or ‘home’ position. The tags for the body parts and weapons are named tag_weapon, tag_torso and tag_head. | ||
| − | + | == 3. Texturing == | |
Once you finish building your character go ahead and attach it to your biped and do some basic test animations to make certain the mesh doesn’t deform in weird ways. Turn edges, ad faces, whatever you need to do to make sure that while animating, the character retains its mesh integrity. Handing the mesh over to another artist to assign UVW’s or assigning and texturing yourself without testing the animation integrity of the mesh is very risky. Major modifications after UV assignment can cost you valuable time resulting in re-assigning not just the UV’s, but re-attaching the mesh to your biped as well. Once your model is ready, go ahead and apply the texture to it. Typically the textures used in Q3A consist of one 256 x 256 texture for the body and one 128 x 128 texture for the head. Keep in mind that it’s best to consolidate your texture on a single page rather than break it up into smaller pages. Also some video cards cannot process a texture size larger than 256, so making a high-rez 1024 x 512 texture just won’t be seen since the card will knock it down to 256 x 128 to digest it. | Once you finish building your character go ahead and attach it to your biped and do some basic test animations to make certain the mesh doesn’t deform in weird ways. Turn edges, ad faces, whatever you need to do to make sure that while animating, the character retains its mesh integrity. Handing the mesh over to another artist to assign UVW’s or assigning and texturing yourself without testing the animation integrity of the mesh is very risky. Major modifications after UV assignment can cost you valuable time resulting in re-assigning not just the UV’s, but re-attaching the mesh to your biped as well. Once your model is ready, go ahead and apply the texture to it. Typically the textures used in Q3A consist of one 256 x 256 texture for the body and one 128 x 128 texture for the head. Keep in mind that it’s best to consolidate your texture on a single page rather than break it up into smaller pages. Also some video cards cannot process a texture size larger than 256, so making a high-rez 1024 x 512 texture just won’t be seen since the card will knock it down to 256 x 128 to digest it. | ||
| − | + | == 4. Set Up for Animation == | |
| − | + | ||
Once the character is textured or skinned, bring the mesh back into 3dsMax (2.5) and attach it to an adjusted Biped using the Character Studio plug-in. As a rule of thumb, it’s always better to just assign the mesh to the biped using the default settings and then manually assign vertices to appropriate skeletal ‘limbs’. | Once the character is textured or skinned, bring the mesh back into 3dsMax (2.5) and attach it to an adjusted Biped using the Character Studio plug-in. As a rule of thumb, it’s always better to just assign the mesh to the biped using the default settings and then manually assign vertices to appropriate skeletal ‘limbs’. | ||
| − | + | == 5. Animation == | |
| − | + | When animating the character, keep all animations in one file. It's crucial that the animations adhere to a specific order that pertains to the separate body parts as this supports our current tag system. | |
| − | Basically the order of animations goes: full body (animations that combine both upper and lower), upper body, and lower body. Each character file has the following animations in them and for now that's all the modeler is allowed. The division is basically death (all body parts), extraneous upper body, and dedicated locomotive animations. That way all the upper body animations can be performed at any time, separate from whatever it is that that lower body animations may be doing. There is a set number of animation types which are (in order): | + | |
| − | + | Basically the order of animations goes: full body (animations that combine both upper and lower), upper body, and lower body. Each character file has the following animations in them and for now that's all the modeler is allowed. The division is basically death (all body parts), extraneous upper body, and dedicated locomotive animations. That way all the upper body animations can be performed at any time, separate from whatever it is that that lower body animations may be doing. There is a set number of animation types which are (in order): | |
| − | + | ||
| + | - death1 (approx. 30 frames) - death2 (approx. 30 frames) - death3 (approx. 30 frames) | ||
| + | |||
| + | - taunt (approx. 45 frames) - weapon attack (exactly 6 frames) - melee attack (exactly 6 frames) - change weapon (exactly 9 frames) - weapon idle (exactly 1 frame) - melee idle (exactly 1 frame) | ||
-crouched walk (approx. 10 frames) | -crouched walk (approx. 10 frames) | ||
| − | - walk (approx. 15 frames) | + | |
| − | + | - walk (approx. 15 frames) | |
| − | + | ||
| − | + | - run (approx. 12 frames) | |
| − | + | ||
| − | + | - backpedal (approx. 10 frames) | |
| − | + | ||
| − | + | - swim (approx. 10 frames) | |
| − | + | ||
| − | + | - jump forward (approx. 10 frames) | |
| − | + | ||
| + | - jump forward-land (approx. 6 frames) | ||
| + | |||
| + | - jump backward (approx. 10 frames) | ||
| + | |||
| + | - jump backward-land (approx. 6 frames) | ||
| + | |||
| + | - standing idle (approx. 10 frames) | ||
| + | |||
| + | - crouched idle (approx. 10 frames) | ||
| + | |||
| + | - turn in place (approx. 8 frames) | ||
A good rule of thumb is to create an idle pose at the frame right after the final death frame. Keep this pose for the entire lower body and center of mass of the biped up through melee idle frame since any animation by the lower body during these frames will not register during the grab process. Similarly, once the animations for the lower body start, copy the pose for the upper body at the weapon idle frame to the first frame of the crouched walk animation and don’t animate the upper body at all after that frame. This allows you to more closely approximate what happens during the game where the upper body is basically just along for the ride as the lower body carries it along via the tag_torso. | A good rule of thumb is to create an idle pose at the frame right after the final death frame. Keep this pose for the entire lower body and center of mass of the biped up through melee idle frame since any animation by the lower body during these frames will not register during the grab process. Similarly, once the animations for the lower body start, copy the pose for the upper body at the weapon idle frame to the first frame of the crouched walk animation and don’t animate the upper body at all after that frame. This allows you to more closely approximate what happens during the game where the upper body is basically just along for the ride as the lower body carries it along via the tag_torso. | ||
| Line 58: | Line 72: | ||
Keep in mind that an animation.cfg has to be generated for each character that is a direct reflection of your animation file above. | Keep in mind that an animation.cfg has to be generated for each character that is a direct reflection of your animation file above. | ||
| − | + | == 6. Setting up Tags == | |
| − | + | After the modeler is satisfied with the animations for the character, it’s time to bring in the tags that up until now, have kept in a separate file. This is milestone mark that lets the modeler know that the character is nearly complete. ‘Merge’ the tags into your scene. Turn off 'inherit scale' for the tags under the hierarchy/link command panel in Max. Then, assign a Physique modifier (Character Studio), linking them to specific areas in the biped: | |
| − | + | ||
| + | tag_torso is linked to the Biped 'pelvis' | ||
| − | + | tag_head is linked to the Biped 'head'. | |
| − | = 6.1 Animate Body Tags = | + | tag_weapon is linked to the right ‘hand’. |
| + | |||
| + | === 6.1 Animate Body Tags === | ||
Now, go in and actually animate the tag_torso so that it matches the default position (established previously at approximately the standing idle frame- from the top view it looks like a perfect 90 degree triangle with the base half as wide as the length, pointing forward) when appropriate. “Appropriate” means that as the character goes through the lower body animations, if the triangle is pointing anywhere else but forward, the upper body will point that way as well since to the code the upper body IS the tag. This works out to the modeler’s advantage, though because even if the upper body LOOKS crazy in the animation you simply rely on the tag representation to compensate for it. | Now, go in and actually animate the tag_torso so that it matches the default position (established previously at approximately the standing idle frame- from the top view it looks like a perfect 90 degree triangle with the base half as wide as the length, pointing forward) when appropriate. “Appropriate” means that as the character goes through the lower body animations, if the triangle is pointing anywhere else but forward, the upper body will point that way as well since to the code the upper body IS the tag. This works out to the modeler’s advantage, though because even if the upper body LOOKS crazy in the animation you simply rely on the tag representation to compensate for it. | ||
| − | = 6.2 Handling Weapon Tags = | + | === 6.2 Handling Weapon Tags === |
| − | + | Tag_weapon is a bit different. Basically there is no difference between view model weapons (the weapon as seen by the player when it is in use by his or another player) and the world model weapons (weapons as they are found rotating in the maps) in Quake III Arena. However, for visually clarity and identification, they are doubled in scale when they become seen as world models. They are the same object. This reduces the number of models needed the game and creates an overall more efficient system. Unfortunately a drawback to the system is that there can be only one firing animation for the character. Thusly all weapons need to fit within the grip of the character regardless of size or geometry. This also makes it impossible to see hands on your weapons or otherwise perform vertex animation on the weapons other than barrel rotations vis the tag system (tag_barrel). | |
| − | + | Since the placement is always the same for the character's hands on the weapons , create the animations to the point where it begins the weapon attack sequence. Then merge one of the weapon models into the character file as a guide. The weapons have a nested triangle of same dimensions as the tag_head and tag_torso triangles (each weapon in the game has this triangle saved with it. Move the weapon into a horizontal firing position (using the side view) to about where the character would be holding the weapon correctly. Then move the character's hands into the appropriate position and link the weapon to the character's right hand. | |
| − | + | When you get to the point where you bring in the tags, make a snapshot of the weapon, hide the original and simply delete all the vertices and faces of the copy of the weapon object except for the nested triangle. Rename it tag_weapon, turn off the 'inherit scale' attributes (very important), and assign Physique to it (linking it to the 'right hand' of the biped) and voila. Ready to export. | |
| − | + | == 7. Level of Detail == | |
Each of the Quake III Arena player characters have a base model and two lower polygon versions of the model (to help with speed issues). For use in the game, the three levels of detail are file formatted as follows: | Each of the Quake III Arena player characters have a base model and two lower polygon versions of the model (to help with speed issues). For use in the game, the three levels of detail are file formatted as follows: | ||
| Line 85: | Line 102: | ||
Level of detail means you need to make three versions of your model to get the best performance during gameplay. Each version needs to have the same textures assigned and same animations assigned to them in order to work in the game. The numbers you need to shoot for are 800 faces for the highest level, 500 faces for next level and 300 for the lowest level. This works out roughly to be a 60% drop in each LOD, but your numbers will vary in order to maintain mesh integrity. Most LOD’s created in Q3A were done with the plugin called MRM (multiple resolution mesh) by Intel. The stock Optimize modifier or manual optimization techniques can be applied. | Level of detail means you need to make three versions of your model to get the best performance during gameplay. Each version needs to have the same textures assigned and same animations assigned to them in order to work in the game. The numbers you need to shoot for are 800 faces for the highest level, 500 faces for next level and 300 for the lowest level. This works out roughly to be a 60% drop in each LOD, but your numbers will vary in order to maintain mesh integrity. Most LOD’s created in Q3A were done with the plugin called MRM (multiple resolution mesh) by Intel. The stock Optimize modifier or manual optimization techniques can be applied. | ||
| − | + | == 8. Exporting == | |
Once the tags are in place (also with the Physique modifier attached to them) the model is ready to export to an ase(ascii) file.''' ''' To make the models available for use in Quake III Arena, the model was exported to a native 3dsMax ASCII format file called an ‘.ase’ file. This export option in Max has several check boxes to tweak and then just exports the character with its animation data (via Character Studio) to a huge ase/ascii file. Under ‘Output Options’ make sure the ‘Mesh Definition’, ‘Materials’, ‘Transform Animation Keys’, and ‘Animated Mesh’ boxes are checked. Under ‘Mesh Options’ and ‘Object Types’ make sure ‘Mapping Coordinates’ and ‘Geometric’ are the only boxes checked, respectively and let it run. Your ‘Time Configuration’ must reflect a ‘0’ starting point up through the last frame of your animation. The native Max exporter will rely on the time configuration as a guide on which frames to actually grab during the conversion process. Of course there will be better exporters available in the future…this is just how it was done for the characters in Q3A. | Once the tags are in place (also with the Physique modifier attached to them) the model is ready to export to an ase(ascii) file.''' ''' To make the models available for use in Quake III Arena, the model was exported to a native 3dsMax ASCII format file called an ‘.ase’ file. This export option in Max has several check boxes to tweak and then just exports the character with its animation data (via Character Studio) to a huge ase/ascii file. Under ‘Output Options’ make sure the ‘Mesh Definition’, ‘Materials’, ‘Transform Animation Keys’, and ‘Animated Mesh’ boxes are checked. Under ‘Mesh Options’ and ‘Object Types’ make sure ‘Mapping Coordinates’ and ‘Geometric’ are the only boxes checked, respectively and let it run. Your ‘Time Configuration’ must reflect a ‘0’ starting point up through the last frame of your animation. The native Max exporter will rely on the time configuration as a guide on which frames to actually grab during the conversion process. Of course there will be better exporters available in the future…this is just how it was done for the characters in Q3A. | ||
| − | + | == 9. Animation Config File == | |
The character's animations are controlled by an 'animation.cfg' file where the model maker specifies reference frames and frame rates. The animation.cfg file is a text file (originally created with MS Excel) which contains the frame and animation sequence data. Place this in the model’s directory. Note, when the modeler is testing the model in Quake III Arena, changes to the animation.cfg can be made without having to re-grab the model…just do a ‘vid_restart’ at the cvar command line prompt. | The character's animations are controlled by an 'animation.cfg' file where the model maker specifies reference frames and frame rates. The animation.cfg file is a text file (originally created with MS Excel) which contains the frame and animation sequence data. Place this in the model’s directory. Note, when the modeler is testing the model in Quake III Arena, changes to the animation.cfg can be made without having to re-grab the model…just do a ‘vid_restart’ at the cvar command line prompt. | ||
| Line 95: | Line 112: | ||
//////////////////////////////////////////////////////////////////////////////// | //////////////////////////////////////////////////////////////////////////////// | ||
| − | + | // animation config file | |
| − | // animation config file | + | sex m |
| − | + | headoffset 0 0 0 | |
| − | sex m | + | footsteps normal |
| − | + | // first frame, num frames, looping frames, frames per second | |
| − | headoffset 0 0 0 | + | 0 30 0 25 // BOTH_DEATH1 |
| − | + | 29 1 0 25 // BOTH_DEAD1 | |
| − | footsteps normal | + | 30 30 0 25 // BOTH_DEATH2 |
| − | + | 59 1 0 25 // BOTH_DEAD2 | |
| − | // first frame, num frames, looping frames, frames per second | + | 60 30 0 25 // BOTH_DEATH3 |
| − | + | 89 1 0 25 // BOTH_DEAD3 | |
| − | 0 30 0 25 // BOTH_DEATH1 | + | 90 40 0 20 // TORSO_GESTURE |
| − | + | 130 6 0 15 // TORSO_ATTACK (MUST NOT CHANGE -- hand animation is synced to this) | |
| − | 29 1 0 25 // BOTH_DEAD1 | + | 136 6 0 15 // TORSO_ATTACK2 (MUST NOT CHANGE -- hand animation is synced to this) |
| − | + | 142 5 0 20 // TORSO_DROP (MUST NOT CHANGE -- hand animation is synced to this) | |
| − | 30 30 0 25 // BOTH_DEATH2 | + | 147 4 0 20 // TORSO_RAISE (MUST NOT CHANGE -- hand animation is synced to this) |
| − | + | 151 1 0 15 // TORSO_STAND | |
| − | 59 1 0 25 // BOTH_DEAD2 | + | 152 1 0 15 // TORSO_STAND2 |
| − | + | 153 8 8 20 // LEGS_WALKCR | |
| − | 60 30 0 25 // BOTH_DEATH3 | + | 161 12 12 20 // LEGS_WALK |
| − | + | 173 9 9 18 // LEGS_RUN | |
| − | 89 1 0 25 // BOTH_DEAD3 | + | 182 10 10 20 // LEGS_BACK |
| − | + | 192 10 10 15 // LEGS_SWIM | |
| − | 90 40 0 20 // TORSO_GESTURE | + | 202 8 0 15 // LEGS_JUMP |
| − | + | 210 1 0 15 // LEGS_LAND | |
| − | 130 6 0 15 // TORSO_ATTACK (MUST NOT CHANGE -- hand animation is synced to this) | + | 211 8 0 15 // LEGS_JUMPB |
| − | + | 219 1 0 15 // LEGS_LANDB | |
| − | 136 6 0 15 // TORSO_ATTACK2 (MUST NOT CHANGE -- hand animation is synced to this) | + | 220 10 10 15 // LEGS_IDLE |
| − | + | 230 10 10 15 // LEGS_IDLECR | |
| − | 142 5 0 20 // TORSO_DROP (MUST NOT CHANGE -- hand animation is synced to this) | + | 240 7 7 15 // LEGS_TURN |
| − | + | ||
| − | 147 4 0 20 // TORSO_RAISE (MUST NOT CHANGE -- hand animation is synced to this) | + | |
| − | + | ||
| − | 151 1 0 15 // TORSO_STAND | + | |
| − | + | ||
| − | 152 1 0 15 // TORSO_STAND2 | + | |
| − | + | ||
| − | 153 8 8 20 // LEGS_WALKCR | + | |
| − | + | ||
| − | 161 12 12 20 // LEGS_WALK | + | |
| − | + | ||
| − | 173 9 9 18 // LEGS_RUN | + | |
| − | + | ||
| − | 182 10 10 20 // LEGS_BACK | + | |
| − | + | ||
| − | 192 10 10 15 // LEGS_SWIM | + | |
| − | + | ||
| − | 202 8 0 15 // LEGS_JUMP | + | |
| − | + | ||
| − | 210 1 0 15 // LEGS_LAND | + | |
| − | + | ||
| − | 211 8 0 15 // LEGS_JUMPB | + | |
| − | + | ||
| − | 219 1 0 15 // LEGS_LANDB | + | |
| − | + | ||
| − | 220 10 10 15 // LEGS_IDLE | + | |
| − | + | ||
| − | 230 10 10 15 // LEGS_IDLECR | + | |
| − | + | ||
| − | 240 7 7 15 // LEGS_TURN | + | |
| − | + | ||
////////////////////////////////////////////////////////////////// | ////////////////////////////////////////////////////////////////// | ||
| − | + | == 10. The Conversion Process == | |
The models need to be run through id’s custom md3 conversion/'grabber' program. The program uses the information in the Quake Data text file ([filename].qdt) to grab and convert the 3dsMax files. | The models need to be run through id’s custom md3 conversion/'grabber' program. The program uses the information in the Quake Data text file ([filename].qdt) to grab and convert the 3dsMax files. | ||
| − | = 10.1 The Conversion File = | + | === 10.1 The Conversion File === |
| − | + | Create a “Quake Data” text file for the model with the extension “.qdt”. The contents for our [character].qdt file would read something like: | |
$asecanimconvert models/players/[character]/[character].ase -playerparms 92 155 | $asecanimconvert models/players/[character]/[character].ase -playerparms 92 155 | ||
| − | |||
$asecanimconvert models/players/[character]/[character]_1.ase -lod 1 -playerparms 92 155 | $asecanimconvert models/players/[character]/[character]_1.ase -lod 1 -playerparms 92 155 | ||
| − | |||
$asecanimconvert models/players/[character]/[character]_2.ase -lod 2 -playerparms 92 155 | $asecanimconvert models/players/[character]/[character]_2.ase -lod 2 -playerparms 92 155 | ||
| − | == 10.1.1 “$asecanimconvert” == | + | ==== 10.1.1 “$asecanimconvert” ==== |
This is the grrabber program executable. | This is the grrabber program executable. | ||
| − | == 10.1.2 “models/players/[character]/[character].ase” == | + | ==== 10.1.2 “models/players/[character]/[character].ase” ==== |
This is the path to the model’s .ase file. The program looks for files starting in your Quake3\baseq3 directory. | This is the path to the model’s .ase file. The program looks for files starting in your Quake3\baseq3 directory. | ||
| Line 179: | Line 163: | ||
This tells the converter that this is the first level of reduced detail for the model. The value “-lod 2” is for the second, or lowest level of detail for the model. | This tells the converter that this is the first level of reduced detail for the model. The value “-lod 2” is for the second, or lowest level of detail for the model. | ||
| − | == 10.1.3 “-playerparms 92 155” == | + | ==== 10.1.3 “-playerparms 92 155” ==== |
This tells the converter which frame the upper body anims only start (first value) and which frame the lower body only anims start (second value). The numbers here are only used as examples | This tells the converter which frame the upper body anims only start (first value) and which frame the lower body only anims start (second value). The numbers here are only used as examples | ||
| − | + | === 10.2 Run the Conversion === | |
| + | |||
| + | When the qdt file is set up correctly, run the grabber by opening MSDOS command prompt, going to the quake3 directory containing the model files and typing in 'q3data [character].qdt' | ||
| − | + | == 11. Review the Model == | |
| − | + | Load up Quake 3 Arena. Go to map Q3DM0 (or any map containing a mirror). Bring down the console and type “\model [character name]”. Hit your Show Score key (default is TAB). You should see your new model here. Tweak the frame rates in your animation.cfg file and save them. Type in “\vid_restart” on the console and hit enter to see the changes. | |
| − | + | ---- | |
| + | [[Category:Quake3]] | ||
Latest revision as of 07:55, 17 November 2015
 This page is an archive. The information here is probably out of date or incorrect, and the links may not work. This archive is probably being kept for historical reasons. Please do not edit this page unless you know what you are doing.
|
Contents
- 1 Putting New Models in Quake III Arena
- 1.1 1. Setting up the Files
- 1.2 2. Building and Naming the Mesh
- 1.3 3. Texturing
- 1.4 4. Set Up for Animation
- 1.5 5. Animation
- 1.6 6. Setting up Tags
- 1.7 7. Level of Detail
- 1.8 8. Exporting
- 1.9 9. Animation Config File
- 1.10 10. The Conversion Process
- 1.11 10.1.3 “-lod 1” or “-lod 2”
- 1.12 11. Review the Model
Putting New Models in Quake III Arena
- Based on original notes by Paul Steed
- Edited by Paul Jaquays
- Edited 12/22/99 by ps
The purpose of this document is to explain how to set up a model for Quake 3 Arena, create the necessary animation and conversion files, and then export it into the MD3 format required by the game. It is intended to be informative only and not a tutorial on building or animating models.
The player models for Quake III Arena were built using the commercial modeling software, 3D Studio Max R2.5 (3ds Max) by Kinetix. These models were then animated using Physique and Biped, components of a plugin for 3dsMax called Character Studio (also by Kinetix). The following instructions assume that you will model and animate with 3dsMax and Character Studio.
1. Setting up the Files
Begin in your Quake3 directory. If you don’t have one already, create a baseq3 directory. Inside the baseq3 directory, create a models directory. Inside the models directory, create a players directory. Inside the players directory, create a directory with the name of your model (we will use [character] in this document to represent information requiring the name of the model). It is generally a good idea to create a ‘work’ directory under [character] so that the [character] directory itself remains uncluttered. Place all versions of your model and temp textures here, saving the [character] directory purely for the finished model files.
2. Building and Naming the Mesh
The mesh should be built keeping in mind the game engine needs three distinct body part grouping: the head, the upper body, and the lower body. These groupings can consist of different parts or sub-objects, but keep in mind too many sub-objects does impact performance and game play speed. A good rule of thumb is to consolidate your objects (i.e. attach them to each other) as long as they remain a part of a major group. For example, you decide to create a character that has its arms as separate objects for easier animation. Unless the arms or torso has different textures assigned to them go ahead and attach the arms to the torso. It may be more difficult to assign the vertices to the biped skeleton later on, but the efficiency of the model is much better. However, if you must keep the limbs detached for unique shader assignment then keep the following naming conventions in mind:
2.1 Head Geometry
All head geometry needs to begin with lower case 'H_' (h_head, h_glasses, h_hat, etc...). Keep in mind that the head has no animations itself other than to respond to player mouse-look input.
2.2 Upper Body Geometry
All upper body geometry needs to begin with lower case 'U_' (u_torso, u_arms, u_abdomen, etc.) This is your model’s torso and arms. The individual animations for the upper body are listed below.
2.3 Lower Body Geometry
All lower body geometry begins with lower case 'L_' (l_hips, l_legs, l_lfoot, l_rfoot, etc...). This is your model’s buttocks, legs and feet. The individual animations for the upper body are listed below.
2.4 Tags
Tags are connection points for other model parts and represent the limited hierarchical system of the game. They include links between the three character body parts and the weapons. Keep in mind that these tags are representations of geometry so they can be animated to represent that geometry. For example, tag_head represents the head, tag_torso represents the torso and tag_weapon represents the weapon. This is important to understand since for example, any time the character is performing a locomotive animation, the upper body can and will animate independently of the lower body, using the relative position of the tag as a base or ‘home’ position. The tags for the body parts and weapons are named tag_weapon, tag_torso and tag_head.
3. Texturing
Once you finish building your character go ahead and attach it to your biped and do some basic test animations to make certain the mesh doesn’t deform in weird ways. Turn edges, ad faces, whatever you need to do to make sure that while animating, the character retains its mesh integrity. Handing the mesh over to another artist to assign UVW’s or assigning and texturing yourself without testing the animation integrity of the mesh is very risky. Major modifications after UV assignment can cost you valuable time resulting in re-assigning not just the UV’s, but re-attaching the mesh to your biped as well. Once your model is ready, go ahead and apply the texture to it. Typically the textures used in Q3A consist of one 256 x 256 texture for the body and one 128 x 128 texture for the head. Keep in mind that it’s best to consolidate your texture on a single page rather than break it up into smaller pages. Also some video cards cannot process a texture size larger than 256, so making a high-rez 1024 x 512 texture just won’t be seen since the card will knock it down to 256 x 128 to digest it.
4. Set Up for Animation
Once the character is textured or skinned, bring the mesh back into 3dsMax (2.5) and attach it to an adjusted Biped using the Character Studio plug-in. As a rule of thumb, it’s always better to just assign the mesh to the biped using the default settings and then manually assign vertices to appropriate skeletal ‘limbs’.
5. Animation
When animating the character, keep all animations in one file. It's crucial that the animations adhere to a specific order that pertains to the separate body parts as this supports our current tag system.
Basically the order of animations goes: full body (animations that combine both upper and lower), upper body, and lower body. Each character file has the following animations in them and for now that's all the modeler is allowed. The division is basically death (all body parts), extraneous upper body, and dedicated locomotive animations. That way all the upper body animations can be performed at any time, separate from whatever it is that that lower body animations may be doing. There is a set number of animation types which are (in order):
- death1 (approx. 30 frames) - death2 (approx. 30 frames) - death3 (approx. 30 frames)
- taunt (approx. 45 frames) - weapon attack (exactly 6 frames) - melee attack (exactly 6 frames) - change weapon (exactly 9 frames) - weapon idle (exactly 1 frame) - melee idle (exactly 1 frame)
-crouched walk (approx. 10 frames)
- walk (approx. 15 frames)
- run (approx. 12 frames)
- backpedal (approx. 10 frames)
- swim (approx. 10 frames)
- jump forward (approx. 10 frames)
- jump forward-land (approx. 6 frames)
- jump backward (approx. 10 frames)
- jump backward-land (approx. 6 frames)
- standing idle (approx. 10 frames)
- crouched idle (approx. 10 frames)
- turn in place (approx. 8 frames)
A good rule of thumb is to create an idle pose at the frame right after the final death frame. Keep this pose for the entire lower body and center of mass of the biped up through melee idle frame since any animation by the lower body during these frames will not register during the grab process. Similarly, once the animations for the lower body start, copy the pose for the upper body at the weapon idle frame to the first frame of the crouched walk animation and don’t animate the upper body at all after that frame. This allows you to more closely approximate what happens during the game where the upper body is basically just along for the ride as the lower body carries it along via the tag_torso.
Keep in mind that an animation.cfg has to be generated for each character that is a direct reflection of your animation file above.
6. Setting up Tags
After the modeler is satisfied with the animations for the character, it’s time to bring in the tags that up until now, have kept in a separate file. This is milestone mark that lets the modeler know that the character is nearly complete. ‘Merge’ the tags into your scene. Turn off 'inherit scale' for the tags under the hierarchy/link command panel in Max. Then, assign a Physique modifier (Character Studio), linking them to specific areas in the biped:
tag_torso is linked to the Biped 'pelvis'
tag_head is linked to the Biped 'head'.
tag_weapon is linked to the right ‘hand’.
6.1 Animate Body Tags
Now, go in and actually animate the tag_torso so that it matches the default position (established previously at approximately the standing idle frame- from the top view it looks like a perfect 90 degree triangle with the base half as wide as the length, pointing forward) when appropriate. “Appropriate” means that as the character goes through the lower body animations, if the triangle is pointing anywhere else but forward, the upper body will point that way as well since to the code the upper body IS the tag. This works out to the modeler’s advantage, though because even if the upper body LOOKS crazy in the animation you simply rely on the tag representation to compensate for it.
6.2 Handling Weapon Tags
Tag_weapon is a bit different. Basically there is no difference between view model weapons (the weapon as seen by the player when it is in use by his or another player) and the world model weapons (weapons as they are found rotating in the maps) in Quake III Arena. However, for visually clarity and identification, they are doubled in scale when they become seen as world models. They are the same object. This reduces the number of models needed the game and creates an overall more efficient system. Unfortunately a drawback to the system is that there can be only one firing animation for the character. Thusly all weapons need to fit within the grip of the character regardless of size or geometry. This also makes it impossible to see hands on your weapons or otherwise perform vertex animation on the weapons other than barrel rotations vis the tag system (tag_barrel).
Since the placement is always the same for the character's hands on the weapons , create the animations to the point where it begins the weapon attack sequence. Then merge one of the weapon models into the character file as a guide. The weapons have a nested triangle of same dimensions as the tag_head and tag_torso triangles (each weapon in the game has this triangle saved with it. Move the weapon into a horizontal firing position (using the side view) to about where the character would be holding the weapon correctly. Then move the character's hands into the appropriate position and link the weapon to the character's right hand.
When you get to the point where you bring in the tags, make a snapshot of the weapon, hide the original and simply delete all the vertices and faces of the copy of the weapon object except for the nested triangle. Rename it tag_weapon, turn off the 'inherit scale' attributes (very important), and assign Physique to it (linking it to the 'right hand' of the biped) and voila. Ready to export.
7. Level of Detail
Each of the Quake III Arena player characters have a base model and two lower polygon versions of the model (to help with speed issues). For use in the game, the three levels of detail are file formatted as follows:
[character].[file extension] This is the highest detail model for close up viewing
[character]_1.[file extension] This is a slightly lower polygon model for mid distance viewing
[character]_2.[file extension] This is the lowest polygon model for long distance viewing.
Level of detail means you need to make three versions of your model to get the best performance during gameplay. Each version needs to have the same textures assigned and same animations assigned to them in order to work in the game. The numbers you need to shoot for are 800 faces for the highest level, 500 faces for next level and 300 for the lowest level. This works out roughly to be a 60% drop in each LOD, but your numbers will vary in order to maintain mesh integrity. Most LOD’s created in Q3A were done with the plugin called MRM (multiple resolution mesh) by Intel. The stock Optimize modifier or manual optimization techniques can be applied.
8. Exporting
Once the tags are in place (also with the Physique modifier attached to them) the model is ready to export to an ase(ascii) file. To make the models available for use in Quake III Arena, the model was exported to a native 3dsMax ASCII format file called an ‘.ase’ file. This export option in Max has several check boxes to tweak and then just exports the character with its animation data (via Character Studio) to a huge ase/ascii file. Under ‘Output Options’ make sure the ‘Mesh Definition’, ‘Materials’, ‘Transform Animation Keys’, and ‘Animated Mesh’ boxes are checked. Under ‘Mesh Options’ and ‘Object Types’ make sure ‘Mapping Coordinates’ and ‘Geometric’ are the only boxes checked, respectively and let it run. Your ‘Time Configuration’ must reflect a ‘0’ starting point up through the last frame of your animation. The native Max exporter will rely on the time configuration as a guide on which frames to actually grab during the conversion process. Of course there will be better exporters available in the future…this is just how it was done for the characters in Q3A.
9. Animation Config File
The character's animations are controlled by an 'animation.cfg' file where the model maker specifies reference frames and frame rates. The animation.cfg file is a text file (originally created with MS Excel) which contains the frame and animation sequence data. Place this in the model’s directory. Note, when the modeler is testing the model in Quake III Arena, changes to the animation.cfg can be made without having to re-grab the model…just do a ‘vid_restart’ at the cvar command line prompt.
Edit an animation.cfg file which matches the frame/animation sequences and place it in the character's directory. Each animation can have different frame rates that the modeler can tweak, save out in the animation.cfg, hit 'vid_restart' to see the change right away in the game (no need to re-grab the model). The file for visor is shown here below in it’s entirety. You may clip this portion of the file out and use it as the basis for your own animation files.
//////////////////////////////////////////////////////////////////////////////// // animation config file sex m headoffset 0 0 0 footsteps normal // first frame, num frames, looping frames, frames per second 0 30 0 25 // BOTH_DEATH1 29 1 0 25 // BOTH_DEAD1 30 30 0 25 // BOTH_DEATH2 59 1 0 25 // BOTH_DEAD2 60 30 0 25 // BOTH_DEATH3 89 1 0 25 // BOTH_DEAD3 90 40 0 20 // TORSO_GESTURE 130 6 0 15 // TORSO_ATTACK (MUST NOT CHANGE -- hand animation is synced to this) 136 6 0 15 // TORSO_ATTACK2 (MUST NOT CHANGE -- hand animation is synced to this) 142 5 0 20 // TORSO_DROP (MUST NOT CHANGE -- hand animation is synced to this) 147 4 0 20 // TORSO_RAISE (MUST NOT CHANGE -- hand animation is synced to this) 151 1 0 15 // TORSO_STAND 152 1 0 15 // TORSO_STAND2 153 8 8 20 // LEGS_WALKCR 161 12 12 20 // LEGS_WALK 173 9 9 18 // LEGS_RUN 182 10 10 20 // LEGS_BACK 192 10 10 15 // LEGS_SWIM 202 8 0 15 // LEGS_JUMP 210 1 0 15 // LEGS_LAND 211 8 0 15 // LEGS_JUMPB 219 1 0 15 // LEGS_LANDB 220 10 10 15 // LEGS_IDLE 230 10 10 15 // LEGS_IDLECR 240 7 7 15 // LEGS_TURN //////////////////////////////////////////////////////////////////
10. The Conversion Process
The models need to be run through id’s custom md3 conversion/'grabber' program. The program uses the information in the Quake Data text file ([filename].qdt) to grab and convert the 3dsMax files.
10.1 The Conversion File
Create a “Quake Data” text file for the model with the extension “.qdt”. The contents for our [character].qdt file would read something like:
$asecanimconvert models/players/[character]/[character].ase -playerparms 92 155 $asecanimconvert models/players/[character]/[character]_1.ase -lod 1 -playerparms 92 155 $asecanimconvert models/players/[character]/[character]_2.ase -lod 2 -playerparms 92 155
10.1.1 “$asecanimconvert”
This is the grrabber program executable.
10.1.2 “models/players/[character]/[character].ase”
This is the path to the model’s .ase file. The program looks for files starting in your Quake3\baseq3 directory.
10.1.3 “-lod 1” or “-lod 2”
This tells the converter that this is the first level of reduced detail for the model. The value “-lod 2” is for the second, or lowest level of detail for the model.
10.1.3 “-playerparms 92 155”
This tells the converter which frame the upper body anims only start (first value) and which frame the lower body only anims start (second value). The numbers here are only used as examples
10.2 Run the Conversion
When the qdt file is set up correctly, run the grabber by opening MSDOS command prompt, going to the quake3 directory containing the model files and typing in 'q3data [character].qdt'
11. Review the Model
Load up Quake 3 Arena. Go to map Q3DM0 (or any map containing a mirror). Bring down the console and type “\model [character name]”. Hit your Show Score key (default is TAB). You should see your new model here. Tweak the frame rates in your animation.cfg file and save them. Type in “\vid_restart” on the console and hit enter to see the changes.
