RSS< Twitter< etc

<< Back To XMesh Index

XMesh Saver MX Save Channels Rollout

 

These controls define which mesh data channels will be saved to disk, if found in the sources:

Do Not Save These Channels:

This list contains the channels that should not be saved to disk, even if they exist in the source meshes. Usually, it should be empty, allowing all supported channels to be saved  if necessary.

Note that the Vertex and Face lists will always be saved implicitly and are not listed here.

Save These Channels (If They Exist):

This list contains the channels that should be saved to disk in case they are found in at least one of the source meshes. If multiple meshes are being saved but only some have the channels in question, the other meshes will be set to default values for these channels.

Left / Right Arrow Buttons

Use these buttons to move the selected channels from the one list to another. Alternatively, you can double-click channels to move them to the opposite list.

All / Inverse Buttons

Use these buttons to highlight All or invert the selection of the respective list. Note that All+Invert=None!

Reset To Defaults Button

Use this button to reset the channel lists to the factory defaults, enabling all existing channels for saving.

Special Notes About Velocity Channel Saving 

When the Velocity channel is on the right list, the XMesh Saver will generate a Velocity in one of two ways described below. The Velocity channel will then allow the XMesh Loader to interpolate geometry on sub-frames according to the vertex velocities to produce motion blur.

By default, the XMesh Saver will try to evaluate the geometry on the full frame and at a sub-frame and if the topology is the same, it will extract the velocities based on these two snapshots. If the sub-frame sample has a different topology, the XMesh Saver will attempt to move closer to the full frame and try again. This will continue until a valid matching topology is found OR the velocity generation fails due to changing topology in the very vicinity of the full frame (zero velocities will be saved in that case). Thus, saving changing topology with the "Save Velocity" option on can become very slow - if you know that your geometry is changing topology on most frames and you don't intend to use Motion Blur, you might want to disable this option to speed up the caching process.

An exception to the rule is the saving of Thinking Particles geometry where the velocities of the particles will be used to generate the mesh velocities. This is very fast and should not affect the caching performance at all.

When saving Frost geometry with the XMesh Saver, be sure to use the "Frame Velocity Offset" option in the Frost > Meshing > Motion Blur Mode controls to ensure consistent topology on sub-frames! Otherwise, the XMesh Saver will be unable to find a closest sample with identical topology, but will attempt to rebuild the Frost mesh multiple times, thus causing a significant performance hit!