Friday, June 16, 2006

As the CDK has an important relationship with models, I have learned a bit, not just about models, but how important the communication is between modelmakers and the CDK programmer. I have started this list as a means of allowing the modelmaker and the programmer to identify differences before they become a problem.
It is not complete, by any means, for high-end games with huge budgets and many teams.
However, I hope it is a starting point for CDK level projects. I look forward to hearing suggestions.
MODEL MAKING PROJECT SHEET
Company:
Project name:
Project number:
Project leader/Project team/contact info:
Model name:
Model(s) to be completed by:
Model use:
Description: Drawings/sketches/photos:
First importation test:
Trials:
Debugging schedule:
Detail: hi, medium low:
Texture/Skin/Mesh information:
Polygon count:
Engine to be used:
Operating system:
Engine supports vertex color: yes/no
Model making software to be used:
Drawings/sketches/photos:
First importation test:
Trials/ debugging schedule:
Detail: hi, medium low:
Texture/Skin/Mesh information:
Polygon count:
Game engine to be used:
Operating system:
Physics engine to be used:
Programmer/Modelmaker testing schedule:
Engine supports vertex color: yes/no
Model making software to be used:
Who is responsible for editing model parameters?
Contact info: Model interacts with other models?
Notes on editing parameters:
Who is responsible for animations?
Model interacts with other models?
If so, describe interaction:
Number of animations:
Animation to be completed by:
First animation test:
Animation trial/debugging schedule:
Who is responsible for editing model parameters?
Contact info: Model interacts with other models?
Notes on editing parameters:
Who is responsible for animations?
Model interacts with other models?
If so, please describe interaction Number of animations:
Animation to be completed by:
First animation test:
Animation trial/debugging schedule:
Scaling issues
Examples
Finished models belong to:
Notes: