meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
expstaticmesh [2020/05/27 13:53] – croftexpstaticmesh [2023/11/07 09:31] (current) – steph.jorgensen
Line 1: Line 1:
-======Exporting Meshes======+======VFX export options======
  
-The SpeedTree Modeler can export the trees you create for use in other modeling/rendering applications. Depending on the format selected, these exports can support wind animations, growth animations, mesh unwrapping, and skeletal skinning.+Export high-detail models with the VFX export options. Based on the format selected, these exports can support wind animations, growth animations, mesh unwrapping, and skeletal skinning.
  
-{{ ::export_dialog.png?200 |export dialog}}+To export a model for VFX, select **File** > **Export to mesh** then choose the VFX export type.
  
 +For command line export options, refer to [[export_from_the_command_line|Export from the command line]].
  
->**Note:** Not all versions of the SpeedTree Modeler allow mesh exporting.+=====Export type=====
  
-=====Formats=====+^**Type**^**Description**^ 
 +|**Games**|Export a model with options optimized for games. Refer to [[expgame|Games export options]].| 
 +|**VFX**|Export a model with options optimized for VFX.|
  
-Currently, the SpeedTree Modeler can export meshes in Autodesk FBX, Wavefront OBJ, Alembic IO, and a raw XML format.+=====Preset=====
  
-FBX and OBJ are the most well-supported formats in a variety of third-party applications. Alembic is used more for exporting animations, especially growth animations where the topology changes over time. Wind animations can still end up being a smaller size in Alembic than in FBX, if that is a concern.+^**Preset**^**Description**^ 
 +|**Maya**|Optimize the export for Maya.| 
 +|**3D Studio Max**|Optimize the export for 3ds Max.| 
 +|**Houdini**|Optimize the export for Houdini.| 
 +|**Blender**|Optimize the export for Blender.| 
 +|**Cinema 4D**|Optimize the export for Cinema 4D.| 
 +|**FBX**|Export a generic .fbx model.| 
 +|**Alembic**|Export a generic Alembic model.| 
 +|**USD**|Export a generic .usd model.| 
 +|**Growth**|Export a generic Alembic model with growth animation.| 
 +|**Wind**|Export a generic .fbx model with wind animation.|
  
-Raw XML files are used only in custom pipelines that require extra vertex data from SpeedTree that is not available in other formats.+====Preset options====
  
 +^**Control**^**Description**^
 +|**Save new preset**|Save the current export settings as a new preset.|
 +|**Edit preset name**|Edit the name of the current preset.|
 +|**Delete preset**|Delete the current preset.|
 +|**Load options**|Load previously saved export options from an .ini file.|
 +|**Save options**|Save the current export options to an .ini file.|
 +
 +=====Options=====
 +
 +====File type====
 +
 +Currently, the SpeedTree Modeler can export meshes in Autodesk FBX, Wavefront OBJ, USD, Alembic IO, and a raw XML format.
 +
 +FBX and OBJ are the most well-supported formats in a variety of third-party applications. USD and Alembic are used more for exporting animations, especially growth animations where the topology changes over time. Wind animations can still end up being a smaller size than in FBX, if that is a concern.
 +
 +Raw XML files are used only in custom pipelines that require extra vertex data from SpeedTree that is not available in other formats.
  
-=====Group By=====+====Grouping====
  
-On export, the geometry in a tree can be grouped in different fashions, depending on how the final mesh will be used or modified in an external application. Grouping by material or by geometry type is self-explanatory.+On export, the geometry in a tree can be grouped in different fashions, depending on how the final mesh will be used or modified in an external application. 
  
-==Hierarchy==+====Hierarchy====
  
 Grouping by hierarchy sets the level in the tree under which the tree will be split apart. For example, a level of 0 means the entire mesh in one group. A level of 1 means the trunks of the tree will each be in different groups with their children (in most cases of simple trees, this will be identical to level 0 since there is only one trunk). With a level of 2, the trunk will be in one group and then each major branch will be in a group with all of its children.  Grouping by hierarchy sets the level in the tree under which the tree will be split apart. For example, a level of 0 means the entire mesh in one group. A level of 1 means the trunks of the tree will each be in different groups with their children (in most cases of simple trees, this will be identical to level 0 since there is only one trunk). With a level of 2, the trunk will be in one group and then each major branch will be in a group with all of its children. 
  
-{{ ::export_hierarchy.jpg?0x400 | Hierarchy levels }}+{{:export_hierarchy.jpg?nolink&600|}}
  
 When grouping by hierarchy, the pivots and bounding boxes will be set accordingly. Because of this, you can move and rotate a single branch and all of its children easily if you export grouped by hierarchy at level 2. When grouping by hierarchy, the pivots and bounding boxes will be set accordingly. Because of this, you can move and rotate a single branch and all of its children easily if you export grouped by hierarchy at level 2.
  
- +====Material====
-==Material==+
  
 Grouping by material will do just that, group the geometry by the material it uses. Unwrapping the mesh and using variations may change the final material associations, and thus the grouping. Grouping by material will do just that, group the geometry by the material it uses. Unwrapping the mesh and using variations may change the final material associations, and thus the grouping.
  
- +====Geometry type====
-==Geometry Type==+
  
 Grouping by geometry type will make mesh groups based on the type of tree geometry it is - branch, leaf, mesh, etc. Grouping by geometry type will make mesh groups based on the type of tree geometry it is - branch, leaf, mesh, etc.
  
 +====Generator====
  
 +Grouping by generator will group geometry by the generator used to create it. 
  
 =====Include===== =====Include=====
  
-There are a variety of extra things you may include in the mesh during export. The availability of these changes depending on the format chosen.+There are a variety of extra things you may include in the mesh during export.  
 + 
 +The availability of these options changes depending on the export format. 
 + 
 +====Geometry====
  
-==Geometry== 
 Includes the actual 3D geometry being exported. Disable this only if you need one of the other includes, like Spines, generated with different settings from the geometry itself. Includes the actual 3D geometry being exported. Disable this only if you need one of the other includes, like Spines, generated with different settings from the geometry itself.
  
-==Branch seam blending== +Available for FBX, Alembic, USD, and XML. 
-Includes the blending pieces used to hide branch intersections+ 
 +====Bones/skeleton====
  
-==Bones/Skeleton (FBX)== 
 Includes the skeleton created in the SpeedTree Modeler and smoothly skins the vertices to the correct bones.  Includes the skeleton created in the SpeedTree Modeler and smoothly skins the vertices to the correct bones. 
  
->**Note**: Enabling bones with hierarchy grouping will move the origin of each group to the origin. This is to prevent errors occurring with skeletal deformers in some 3rd party applications.+>**Note:** Enabling bones with hierarchy grouping will move the origin of each group to the origin. This is to prevent errors occurring with skeletal deformers in some 3rd party applications. 
 + 
 +Available for FBX and XML. 
 + 
 +====Leaf references====
  
-==Leaf references (FBX, ABC)== 
 This option includes null references in the correct position and orientation for each leaf. These can be used to populate the leaves with higher quality meshes at runtime. This option includes null references in the correct position and orientation for each leaf. These can be used to populate the leaves with higher quality meshes at runtime.
  
 +Available for FBX, Alembic, USD, and XML.
 +
 +====Branch spines====
  
-==Branch spines (FBX, ABC)== 
 Includes a spline down the center of the branch, useful in some kinds of skinning. Includes a spline down the center of the branch, useful in some kinds of skinning.
  
 +Available for FBX, Alembic, USD, and XML.
  
 +====Vertex blends====
  
-=====Transform=====+Vertex blending is used on small pieces of geometry that need to blend, such as the intersection of a branch to its parent or stitches to a parent mesh. This is done using vertex alphas to fade it out. 
  
-These options modify the output geometry, such as flipping and rotating it for a particular coordinate system.+Separating vertex blends pulls the blends out into a separate object. 
  
 +Available for FBX, Alembic, USD, XML.
 +
 +=====Transform=====
 +
 +These options modify the output size and geometry of your model. You can keep the current scene unit, convert to a different unit, change the scale, or flip and rotate the model for a particular coordinate system.
  
 =====Textures===== =====Textures=====
Line 77: Line 121:
  
 Additionally, a SpeedTree material file (.stmat) is saved next to the exported mesh that contains all the information about the materials coming from the SpeedTree Modeler. Different formats have different ways of specifying materials, and some do not have the options to fully recreate SpeedTree materials elsewhere. To combat this, importer scripts for Maya, Max, Houdini, etc. read the ".stmat" file and use that information to recreate the materials as closely as possible. Additionally, a SpeedTree material file (.stmat) is saved next to the exported mesh that contains all the information about the materials coming from the SpeedTree Modeler. Different formats have different ways of specifying materials, and some do not have the options to fully recreate SpeedTree materials elsewhere. To combat this, importer scripts for Maya, Max, Houdini, etc. read the ".stmat" file and use that information to recreate the materials as closely as possible.
- 
  
 =====Animation===== =====Animation=====
Line 83: Line 126:
 In formats that support it (FBX for wind, Alembic for wind and growth), you can include animation. This animation is saved as a point cache file. Depending on your tree's complexity and length of the animation, computing these caches may take a long time and create large files on disk. In formats that support it (FBX for wind, Alembic for wind and growth), you can include animation. This animation is saved as a point cache file. Depending on your tree's complexity and length of the animation, computing these caches may take a long time and create large files on disk.
  
 +==== Loop====
  
-=====Cache Options=====+SpeedTree wind tends to have many, many different parts moving independently at different frequencies. Due to this, it can be difficult to make a looping animation seamless. Starting in SpeedTree 9, a new "Loop" option is available that attempts to allow this by using geometry morphing/interpolation. An extra portion of wind animation is computed before the exported animation, and is then interpolated to  at the end of the export, providing a seamless loop transition.
  
-When exporting an animation, different cache formats have options that will appear in this section.+>**Note:** When wind speeds are very different at the start and end of the animation (due to use of [[windvfx#gusting|gusting]] or [[tooltimeline#wind|timeline wind]], the loop seam can be more noticeable. Maintain similar wind situations at the start and end of the animation for a more seamless transition.
  
 +{{:loop.png?nolink&600|}}
  
-=====Exporting From the Command Line===== +=====Format-specific=====
- +
-SpeedTree Cinema also has the option to export a tree from the command line, without ever opening the GUI. The command line options are shown below. +
- +
-|  -h|Show help/options | +
-|  -export <file>|Export the loaded spm file to the specified mesh file (fbx, obj, or abc) | +
-|  -export_options <file>|Set options for exporting using the indicated ini file| +
- +
-The export options .ini file you can pass on the command line is the same one you can save using the button in the bottom left of the export mesh dialog. In this manner, you can use the Modeler to set up how you wish files to be exported at a later date. +
- +
->**Note**: On Windows, if you run the .exe directly, the command line will return immediately and you will receive no output from the process until it finishes in the background. If you wish to get feedback from the Modeler, use one of the following methods: +
- +
-| cmd|start "" /B /WAIT <exe> <arguments> | +
-| PowerShell|Start-Process -Wait -NoNewWindow -FilePath <exe> -ArgumentList "<arguments>" |+
  
 +When exporting an animation, different cache formats have options that will appear in this section.
  
 +=====Extra=====
  
 +^**Control**^**Description**^
 +|**Show summary**|Shows a summary of the export settings when the export completes.|
 +|**Skip texture save**|Doesn't save the textures to disk.|