Export

Owned by thomas (Unlicensed)
Last updated: 24 Oct, 2016
2 min read

 

 

Jump to

File (A)

File Name Prefix

Here it is possible to add a custom prefix, character combination or name that will be added in front of any cache file.

Frame/Extension order

You can choose from a selection of four options, but we recommend keeping the default (name#.ext), because it is used by our RealFlow RenderKit and the connectivity plugins.

Padding size

The number defines the number of leading nulls to establish a five-digit number, for example Circle04_00026.bin. We recommend keeping the default (5), because it is used by our RealFlow RenderKit and the connectivity plugins.

Auto default folder creation (B)

Automatically create the default scene tree

When active RealFlow will create a series of standard folder inside the project's directory where the different file types for particles, meshes, fields, etc. will be stored.

Scene embedded data (C)

Include legacy particles in scene file

By default, the particles from standard particle fluids will not be included with the scene file to make it smaller in size.

Include RealWave geometry in scene file

By default, the particles from RealWave simulations will not be included with the scene file to make it smaller in size.

OpenVDB file output (D)

Cache file on memory

When active the OpenVDB files will be pre-cached in your computer's RAM to accelerate the writing of OpenVDBs, especially in networks.

Direct file output

If your OpenVDB files are very large (500+ MB) and save them locally we recommend this option.

Alembic back-end (E)

Ogawa

This is the default selection. Ogawa creates a more efficient data structure and is also much faster than the legacy MD5 format.

MD5

If you need backward compatibility, e.g. for older versions of Alembic, check this option.

Dependencies to copy (F)

With → "Pack and Go" you are able to save a zipped version of a project, e.g. if you want to create a backup or share files with other artists. You decide which dependencies and simulation files will be included with the archive. The function is located in RealFlow's main menu under File > Pack and Go... Here, the standard resources can be changed.

Resources

Dependencies are files the project needs to a correct simulation. Typical dependencies are external objects from SD or ABC files, HDR maps for → imaged-based lighting, or  → parameter maps for controlling attributes like friction or bounciness.

Preserve relative path for files inside project folder

If you want to preserve the project's relative paths leave the appropriate checkbox enabled.

File sequences

Decide whether you want to

  • Copy the current frame
  • Copy the entire simulation range
  • Copy all available frames – this also includes previously simulated, but not yet overwritten files.

Outputs to copy (G)

File formats

Here you can choose which simulation file types you want to add to the archive on a global level. "Global" means that these settings will affect all simulation nodes.

"Output to copy" does not only include particle, mesh, or dynamics files, but also previews, and Maxwell or Arnold render scenes. A prerequisite is, however, that the appropriate resources have been saved at simulation time: "Pack and Go" can only copy what is really there.

Preserve relative paths for files inside project folder

If you want to preserve the project's relative paths leave the appropriate checkbox enabled.

File sequences

Decide whether you want to

  • Copy the current frame
  • Copy the entire simulation range
  • Copy all available frames – this also includes previously simulated, but not yet overwritten files.