Exporting a model/XSI: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(→‎Freeze transforms and history: some people still need to do this)
No edit summary
Line 11: Line 11:
:'''To learn about UV mapping in general, see [[XSI Texturing]].'''
:'''To learn about UV mapping in general, see [[XSI Texturing]].'''


[[Image:Xsi addimage.jpg|thumb|180px|The ‘Textures’ dialogue.]]
[[Image:Xsi addimage.jpg|thumb|180px|The 'Textures' dialogue.]]


In the third group of left-hand menu buttons you will find ‘Textures’. Select your mesh(es) and click the button and choose the first sub-option, ‘Image’. There are two parts of this dialogue we are interested in: ‘Image -> New’ and ‘Texture Projection -> New’.
In the third group of left-hand menu buttons you will find 'Textures'. Select your mesh(es) and click the button and choose the first sub-option, 'Image'. There are two parts of this dialogue we are interested in: 'Image -> New' and 'Texture Projection -> New'.


The filename of the image you import into XSI defines the name of the [[Valve Texture Format|VTF]] file Source will try to apply to the model in-game ([[$cdmaterials|though not its location]]). To avoid confusion, try to keep the texture name the same as the model name. If you don’t want to worry about textures yet you can stick with XSI’s default, but your model will be covered in Source’s purple “missing material” checkerboard when you try to use it.
The filename of the image you import into XSI defines the name of the [[Valve Texture Format|VTF]] file Source will try to apply to the model in-game ([[$cdmaterials|though not its location]]). To avoid confusion, try to keep the texture name the same as the model name. If you don't want to worry about textures yet you can stick with XSI's default, but your model will be covered in Source's purple "missing material" checkerboard when you try to use it.


Next is the texture projection, or [[UV map]]. The XSI [[Studio Model Data|SMD]] exporter will decide what to export by looking at what has UV data, rather than what is hidden and what is visible, even if the mesh is intended for [[collision mesh|collision]], so don't forget this step!
Next is the texture projection, or [[UV map]]. The XSI [[Studio Model Data|SMD]] exporter will decide what to export by looking at what has UV data rather than what is hidden and what is visible, even if the mesh is intended for [[collision mesh|collision]], so don't forget this step!


{{tip|The second and third sections of the Texture toolbar contain shortcuts for applying UV maps.}}
{{tip|The second and third sections of the Texture toolbar contain shortcuts for applying UV maps.}}
Line 23: Line 23:
== Disable automatic discontinuity ==
== Disable automatic discontinuity ==


It isn’t clear why this next step is required – it may be a bug in the SMD exporter. Nevertheless:
It isn't clear why this next step is required – it may be a bug in the SMD exporter. Nevertheless:


#Open the ‘Explorer’ view. Find it in the Views section of the upper toolbar, or press {{key|8}}
#Open the 'Explorer' view. Find it in the Views section of the upper toolbar, or press {{key|8}}
#Expand any of your meshes
#Expand any of your meshes
#Double-click on ‘Geometry Approximation’
#Double-click on 'Geometry Approximation'
#Choose ‘no’ when prompted to make a local copy of the data
#Choose 'no' when prompted to make a local copy of the data
#Click on the ‘Polygon Mesh’ tab of the new dialogue
#Click on the 'Polygon Mesh' tab of the new dialogue
#Un-check ‘Discontinuity -> Automatic’
#Un-check 'Discontinuity -> Automatic'


You may see your meshes’ lighting change slightly when you un-check the box.
You may see your meshes' lighting change slightly when you un-check the box.


{{warning|Neglecting to change this setting will result in any collision meshes being merged into a single shape!}}
{{warning|Neglecting to change this setting will result in any collision meshes being merged into a single shape!}}
Line 38: Line 38:
==Freeze transforms and history==
==Freeze transforms and history==


{{note|This doesn't always seem to be necessary. Best to do it anyway, to be on the safe side.}}
If you have any non-enveloped meshes, which to say if the model isn't animating, you must freeze them before ''each'' export operation. Enveloped meshes should have been frozen before their envelope was applied!


If you have any non-enveloped meshes, which to say if the model isn't animating, you must freeze their transforms (i.e. scale, translate, rotate) before each export operation. Enveloped meshes should have been frozen before their envelope was applied!
Freezing 'bakes' your geometry, turning it from a series of manipulations on primitives (i.e. the cubes or spheres you began with) to a literal representation of where each polygon is located. Much like disabling automatic discontinuity, the fact that this step is required seems to be no more than a limitation of the XSI SMD exporter; unfortunately it's destructive and can really bugger you up if you aren't careful.


To freeze, first select all of your meshes. Then click the section header for ‘Transform’, on the right-hand menu, and choose ‘Freeze All Transforms’, which is directly beneath the first divider. This will ‘bake’ the translation you performed on your first cube. If you try to transform it after freezing, you will notice that the tri-directional arrows now appear the centre of the world rather than the centre of the mesh.
To freeze, first select all of your meshes. Then click the section header for 'Transform', on the right-hand menu, and choose 'Freeze All Transforms', which is directly beneath the first divider. Then choose 'Freeze History -> Modeling' from the right-hand menu.


You will also notice if you try that that the texture projection box has moved to the centre of the world as well. To bake that, and perform various other tidying-up operations, choose ‘Freeze History -> Modeling’ from the right-hand menu.
{{tip|Since you'll probably be freezing transforms quite a lot, you may want to place its button in a more accessible location. Right-click on some empty space under the 'Freeze History' heading and choose 'Customize toolbar'. You can then search the list for 'Freeze All Transforms' and drag it onto the menu.}}
 
You should do this before every export. Much like disabling automatic discontinuity, the fact that this step is required seems to be no more than a limitation of the XSI SMD exporter. You ''can'' sometimes get away with skipping it, but it’s best to get into the habit for all of the times when you can’t!
 
{{tip|Since you’ll probably be freezing transforms quite a lot, you may want to place its button in a more accessible location. Right-click on some empty space under the ‘Freeze History’ heading and choose ‘Customize toolbar’. You can then search the list for ‘Freeze All Transforms’ and drag it onto the menu.}}


== Merge meshes ==
== Merge meshes ==
Line 54: Line 50:
If your model has or will have animations you must merge all of its geometry into the same mesh. This would happen on Export anyway, but the automated version of the process destroys most envelope data.
If your model has or will have animations you must merge all of its geometry into the same mesh. This would happen on Export anyway, but the automated version of the process destroys most envelope data.


Choose ‘Mesh -> Merge’ from the left-hand menu. This has created a new ‘polymsh’ object that contains some, but not all, of the data from your existing meshes. To merge the last few pieces of information in, open Explorer with {{key|8}} and double-click on ‘polymsh -> Polygon Mesh -> Merge Meshes’. Look in the lower half of the new dialogue for two buttons labelled ‘Merge’ and press them, then press the ‘Delete’ button in the top half to remove the old input meshes.
Select everything and choose 'Mesh -> Merge' from the left-hand menu. This has created a new 'polymsh' object that contains some, but not all, of the data from your existing meshes. To merge the last few pieces of information in, open Explorer with {{key|8}} and double-click on 'polymsh -> Polygon Mesh -> Merge Meshes'. Look in the lower half of the new dialogue for two buttons labelled 'Merge' and press them, then press the 'Delete' button in the top half to remove the old input meshes.


{{todo|What if you need to envelope part of a previously-merged mesh? A vertex cluster doesn’t help...}}
{{todo|What if you need to envelope part of a previously-merged mesh? A vertex cluster doesn't help...}}


== Export SMDs ==
== Export SMDs ==


Your model is now ready for export to SMD. The export dialogue can be found from the main menu, under ‘ValveSource -> Export SMD...’.
Your model is now ready for export to SMD. The export dialogue can be found from the main menu, under 'ValveSource -> Export SMD...'.
{{tip|Uncheck ‘Remove all unused bones’ if you are exporting an animated collision model. Otherwise you can usually leave the checkboxes alone.}}
{{tip|Uncheck 'Remove all unused bones' if you are exporting an animated collision model. Otherwise you can usually leave the checkboxes alone.}}
<!--
<!--
// move /integrate the following info to the [[Model Creation Overview]] ... this is general workflow info, not app-specific. It needs to be covered fully, explaining the purpose of each type of SMD and the specification for each : eg ref.smd contains skeleton, a single UV mapped deformable mesh, etc whereas phys.smd must be made of convex meshes, etc, etc. Models for skyboxes, viewmodels, etc don't need a collisionmodel ... etc
// move /integrate the following info to the [[Model Creation Overview]] ... this is general workflow info, not app-specific. It needs to be covered fully, explaining the purpose of each type of SMD and the specification for each : eg ref.smd contains skeleton, a single UV mapped deformable mesh, etc whereas phys.smd must be made of convex meshes, etc, etc. Models for skyboxes, viewmodels, etc don't need a collisionmodel ... etc
Line 67: Line 63:
There are four types of SMD to choose from:
There are four types of SMD to choose from:


#[[Reference mesh]] (called ‘Model’ here)
#[[Reference mesh]] (called 'Model' here)
#[[Collision mesh]]
#[[Collision mesh]]
#[[Skeletal animation]]
#[[Skeletal animation]]
#[[Vertex animation]] (for facial expressions)
#[[Vertex animation]] (for facial expressions)


Every model needs at least one reference mesh and even if it isn't actually animated at least one skeletal animation (traditionally called ‘idle’). Generally, except for idle animations which can be created from the reference mesh, each SMD will be exported from its own XSI file.
Every model needs at least one reference mesh and even if it isn't actually animated at least one skeletal animation (traditionally called 'idle'). Generally, except for idle animations which can be created from the reference mesh, each SMD will be exported from its own XSI file.


It's recommended that you follow a naming convention and use these suffixes on your SMDs:
It's recommended that you follow a naming convention and use these suffixes on your SMDs:
Line 79: Line 75:
*<code>phys</code> for the collision mesh
*<code>phys</code> for the collision mesh
*<code><animation name></code> for each skeletal animation
*<code><animation name></code> for each skeletal animation
*{{todo|What for vertex animations?}}
*<code>expressions</code> for vertex animations


So you might save ‘mymodel-ref.smd’, for example.
So you might save 'mymodel-ref.smd', for example.


== Compile! ==
== Compile! ==

Revision as of 14:53, 3 January 2009

Mod Tool logo

This tutorial will show you how to export a model from the XSI Mod Tool for compiling with studiomdl.

To learn about the general usage of XSI, see the XSI Beginner Tutorial.

Add a texture and UV map

To learn about UV mapping in general, see XSI Texturing.
The 'Textures' dialogue.

In the third group of left-hand menu buttons you will find 'Textures'. Select your mesh(es) and click the button and choose the first sub-option, 'Image'. There are two parts of this dialogue we are interested in: 'Image -> New' and 'Texture Projection -> New'.

The filename of the image you import into XSI defines the name of the VTF file Source will try to apply to the model in-game (though not its location). To avoid confusion, try to keep the texture name the same as the model name. If you don't want to worry about textures yet you can stick with XSI's default, but your model will be covered in Source's purple "missing material" checkerboard when you try to use it.

Next is the texture projection, or UV map. The XSI SMD exporter will decide what to export by looking at what has UV data rather than what is hidden and what is visible, even if the mesh is intended for collision, so don't forget this step!

Tip.pngTip:The second and third sections of the Texture toolbar contain shortcuts for applying UV maps.

Disable automatic discontinuity

It isn't clear why this next step is required – it may be a bug in the SMD exporter. Nevertheless:

  1. Open the 'Explorer' view. Find it in the Views section of the upper toolbar, or press 8
  2. Expand any of your meshes
  3. Double-click on 'Geometry Approximation'
  4. Choose 'no' when prompted to make a local copy of the data
  5. Click on the 'Polygon Mesh' tab of the new dialogue
  6. Un-check 'Discontinuity -> Automatic'

You may see your meshes' lighting change slightly when you un-check the box.

Warning.pngWarning:Neglecting to change this setting will result in any collision meshes being merged into a single shape!

Freeze transforms and history

If you have any non-enveloped meshes, which to say if the model isn't animating, you must freeze them before each export operation. Enveloped meshes should have been frozen before their envelope was applied!

Freezing 'bakes' your geometry, turning it from a series of manipulations on primitives (i.e. the cubes or spheres you began with) to a literal representation of where each polygon is located. Much like disabling automatic discontinuity, the fact that this step is required seems to be no more than a limitation of the XSI SMD exporter; unfortunately it's destructive and can really bugger you up if you aren't careful.

To freeze, first select all of your meshes. Then click the section header for 'Transform', on the right-hand menu, and choose 'Freeze All Transforms', which is directly beneath the first divider. Then choose 'Freeze History -> Modeling' from the right-hand menu.

Tip.pngTip:Since you'll probably be freezing transforms quite a lot, you may want to place its button in a more accessible location. Right-click on some empty space under the 'Freeze History' heading and choose 'Customize toolbar'. You can then search the list for 'Freeze All Transforms' and drag it onto the menu.

Merge meshes

If your model has or will have animations you must merge all of its geometry into the same mesh. This would happen on Export anyway, but the automated version of the process destroys most envelope data.

Select everything and choose 'Mesh -> Merge' from the left-hand menu. This has created a new 'polymsh' object that contains some, but not all, of the data from your existing meshes. To merge the last few pieces of information in, open Explorer with 8 and double-click on 'polymsh -> Polygon Mesh -> Merge Meshes'. Look in the lower half of the new dialogue for two buttons labelled 'Merge' and press them, then press the 'Delete' button in the top half to remove the old input meshes.

Todo: What if you need to envelope part of a previously-merged mesh? A vertex cluster doesn't help...

Export SMDs

Your model is now ready for export to SMD. The export dialogue can be found from the main menu, under 'ValveSource -> Export SMD...'.

Tip.pngTip:Uncheck 'Remove all unused bones' if you are exporting an animated collision model. Otherwise you can usually leave the checkboxes alone.

There are four types of SMD to choose from:

  1. Reference mesh (called 'Model' here)
  2. Collision mesh
  3. Skeletal animation
  4. Vertex animation (for facial expressions)

Every model needs at least one reference mesh and even if it isn't actually animated at least one skeletal animation (traditionally called 'idle'). Generally, except for idle animations which can be created from the reference mesh, each SMD will be exported from its own XSI file.

It's recommended that you follow a naming convention and use these suffixes on your SMDs:

  • ref for the reference mesh
  • phys for the collision mesh
  • <animation name> for each skeletal animation
  • expressions for vertex animations

So you might save 'mymodel-ref.smd', for example.

Compile!

With a reference mesh SMD and skeletal animation SMD exported, you are ready to compile your model.

Retrieved from "https://developer.valvesoftware.com/w/index.php?title=Exporting_a_model/XSI&oldid=89666"