meta data for this page
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
expstaticmesh [2020/03/31 10:24] – external edit 127.0.0.1 | expstaticmesh [2023/11/07 09:31] (current) – steph.jorgensen | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======Exporting Meshes====== | + | ======VFX export options====== |
- | The SpeedTree Modeler can export | + | 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. |
- | {{ :: | + | To export |
+ | For command line export options, refer to [[export_from_the_command_line|Export from the command line]]. | ||
- | > | + | =====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 | + | ^**Preset**^**Description**^ |
+ | |**Maya**|Optimize | ||
+ | |**3D Studio Max**|Optimize the export | ||
+ | |**Houdini**|Optimize | ||
+ | |**Blender**|Optimize the export for Blender.| | ||
+ | |**Cinema 4D**|Optimize the export for Cinema 4D.| | ||
+ | |**FBX**|Export | ||
+ | |**Alembic**|Export | ||
+ | |**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. | ||
- | {{ :: | + | {{: |
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, | 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, | ||
- | + | ====Geometry | |
- | ==Geometry | + | |
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 | + | There are a variety of extra things you may include in the mesh during export. |
+ | |||
+ | The availability of these options | ||
+ | |||
+ | ====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/ | ||
- | ==Bones/ | ||
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. |
+ | |||
+ | 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 | + | 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, | Additionally, | ||
- | |||
=====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 " |
- | When exporting an animation, | + | > |
+ | {{: | ||
- | =====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 | + | When exporting an animation, different cache formats have options |
- | + | ||
- | | -h|Show help/ | + | |
- | | -export < | + | |
- | | -export_options < | + | |
- | + | ||
- | The export options .ini file you can pass on the command line is the same one you can save using the button | + | |
- | + | ||
- | > | + | |
+ | =====Extra===== | ||
+ | ^**Control**^**Description**^ | ||
+ | |**Show summary**|Shows a summary of the export settings when the export completes.| | ||
+ | |**Skip texture save**|Doesn' |