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.
Note: Not all versions of the SpeedTree Modeler allow mesh exporting.
Currently, the SpeedTree Modeler can export meshes in Autodesk FBX, Wavefront OBJ, Alembic IO, and a raw XML format.
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.
Raw XML files are used only in custom pipelines that require extra vertex data from SpeedTree that is not available in other formats.
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.
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.
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.
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 geometry type will make mesh groups based on the type of tree geometry it is - branch, leaf, mesh, etc.
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.
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 blending pieces used to hide branch intersections
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.
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.
Includes a spline down the center of the branch, useful in some kinds of skinning.
These options modify the output geometry, such as flipping and rotating it for a particular coordinate system.
These options control the format and size of the exported textures.
No matter the format chosen for export, many of the same steps occur when dealing with textures. All needed textures are exported, per-material, and all the texture adjustments made in the Modeler are baked into the final texture. Material variations are handled by baking new versions of the maps into a new material used on the tree, so nothing additional needs to be done elsewhere to support them.
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.
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.
When exporting an animation, different cache formats have options that will appear in this section.
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.
|-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, you will want to run “SpeedTree Modeler Cinema.com” instead of the .exe from a cmd or PowerShell window. The .exe will still work, but it will not block the command line and will return immediately while it runs in the background. The .com will also allow you to get error messages back on the command line.