Page History
This page provides information on the Output rollout for a LiquidSim object.
Overview
...
The Output rollout holds the controls for the cache file export.
When you start a simulation, the simulator will typically output an entire animation sequence, which is saved onto your hard drive by default. That sequence is saved as individual files, called caches, which contain raw simulation data for each timeline frame.
The Output rollout lets you set the save path for the cache files, manage what data is written to those cache files, and determine their compression.
Specifically, the cache data consists of grids and particles, which describe the fluid’s behavior. For Liquid simulations, Particle Channels and Grid Channels are written to each cache file, which represent the properties of the simulated fluid at that frame.
In the Output rollout, you can choose which Particle Channels and Grid Channels to export to the cache files, based on your needs.
UI Text Box | ||
---|---|---|
| ||
Phoenix Liquid simulators can simulate several particle system types: Liquid, Foam, Splash, Mist and Wetmap particles. Each of these particle systems contains Particle Channels for each particle, such as Position, Size, Age, ID, Velocity and so forth. The Output rollout lets you manage which of these are exported. Likewise, there are several Grid Channel types, such as Liquid, Velocity, RGB and so on. For Liquid simulations, the Grid Channel data is built from the simulated particles, and then exported to the cache files in the form of a voxel grid, where the Grid channels are contained in each of the voxels. |
UI Text Box | ||
---|---|---|
| ||
Exporting the Grid Liquid Channel willautomatically convert Liquid particles to a grid during export, which is why they can be rendered as a mesh and shaded using standard materials. In addition, the Liquid mesh can also be previewed in the viewport. Note that only Liquid particles can be automatically converted to a grid. The other particle systems (e.g. Foam, Splash, Mist etc.) are exported only as particles, and must be shaded using the Particle Shader. |
UI Text Box | size | medium|
---|---|---|
| ||
UI Path: ||Select Liquid Simulator | LiquidSim object|| > Modify panel > Output rollout |
...
Parameters
...
General
...
...
Section | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
...
|
...
|
UI Expand | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||
$(scene_path) – $(data_dir)\$(scene)_Phoenix_frames\$(nodename)_####.aur #### is the frame number formatted with at least as many digits as the hash signs. If the frame digits are less than the hashes, the number is padded with zeroes to the left. For example:
|
UI Text Box | size | medium|
---|---|---|
| ||
Since version 3.00.02, Phoenix FD can export VDB grid data. Check the How to export Phoenix FD simulation to OpenVDB format video. Particle data can also be exported using the .aur or the .vdb format. Phoenix can convert particles from already simulated Phoenix FD .aur caches into the .prt format as a post-process using the PhoenixFD Phoenix Export PRT Particles dialog or to .vdb format using the Cache Converter tool. |
UI Text Box | ||||
---|---|---|---|---|
| ||||
Clicking the "..." button will open a menu with the following options:
Browse - Opens a dialog where you can select where the simulation caches will be written to. The filename you type in must contain # signs so each simulation frame will be written to a differently numbered file. Also, you can choose between two file formats - AUR and VDB cache files. In order to write the simulation caches to VDB in the default simulation path, you can just edit the Simulation Cache Save Path to $(scene_path).vdb. Delete Cache Files - Clears the cache files matching the provided Simulation Cache Save Path pattern. Reset to Default - Resets the Simulation Cache Save Path to default. Help - Opens this Help page. |
Cacheless Simulation | cacheless – Only the last simulated frame will remain in RAM and no caches will be written to the storage. This will speed up simulations which are bound by slow reading or writing to the hard disk or by compression and decompression of the grid or particle data. You can use this option when iterating on the simulation settings in order to speed up your iterations. It can also be combined with the Render On Each Sim Frame option under the Simulation rollout, so you will get a ready image sequence if you leave the simulation unattended and then return to check it.
Storage Quality | storage_quality – The output grid and particle channels in AUR files are compressed by default in order to increase the performance (faster cache loading) and to avoid excessive memory consumption. This parameter can range from 8 to 20 - 8 is the smallest size, while 20 is the best quality and is uncompressed. If this value is set too low, different artifacts may start appearing depending on the type of scene. For grid channels, artifacts shaped like horizontal slices may appear in preview and rendering. For particle systems such as Liquid or Foam, the artifacts would look like ordered lines of particles , as in the following comparison (click to zoom in):(see the Particle compression artifacts example below).
Anchor | ||||
---|---|---|---|---|
|
Anchor outputParticles outputParticles
Output Particles
...
UI Text Box | ||
---|---|---|
| ||
Phoenix particle systems contain Particle Channels for each particle, which represent the properties of the fluid simulation. Each Particle Channel has its own range of possible values that is most efficient for that specific channel type (see the Particle Channel Ranges). Here in the Output rollout, you can choose which Particle Channels will be exported to the cache files. |
UI Text Box | ||||||
---|---|---|---|---|---|---|
| ||||||
The particle export parameters share a user interface to keep the user interface compact. Each particle system can be selected individually from the drop-down list, and the output settings can be selected for that particle system. When a particle system is selected again, the same settings are retained. |
Section |
---|
...
|
...
|
...
|
...
|
...
|
...
| ||||||||||
|
Example: Particle compression artifacts
...
UI Text Box | |||
---|---|---|---|
medium |
| ||
For particle systems such as Liquid or Foam, the artifacts would look like ordered lines of particles, as in the following comparison (click to zoom in): |
Section | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Note that writing more channels to the cache files takes more time and will add up to the simulation time, so if you know in advance that you will not be needing a certain channel for rendering, then it would help the simulation times if you turn it off.
...
Particle ID – The ID channel will be exported. This channel is used during rendering to identify each particle. Use it when render time size variation is needed, if you would use the Particle Shader's Count Multiplier, or when frame blending will be involved (animated frame index or non-integer play speed).
Particle Age – The particle age channel will be exported. This channel can be used for animation effect based on the particle age, which can be needed by the Phoenix Particle Texture, Phoenix Source, Particle Shader, or Particle Tuner.
UI Text Box | size | medium|
---|---|---|
| ||
The Age channel is affected by the Time Scale option under the Dynamics rollout which acts a multiplier for the Age. |
Particle RGB – The particle RGB channel will be exported. You can use this for simulations where you are mixing different particle colors or you shade the particles by the particle RGB channel through a Particle Texture. Also, enable this if you want to be able to preview the RGB channel as a particle color in the viewport.
...
Particle Viscosity - The particle Viscosity channel will be exported. Enable this if your Resimulation requires the calculation of viscosity.Particle Texture UVW – The particle Texture UVW channel is exported. Enable this to generate texture mapping coordinates that follow the movement of the fluid.
UI Text Box | ||||
---|---|---|---|---|
| ||||
All the info from this section is kept in text form in a single text parameter, which is accessible through MAXScript under the name prt_expmask. |
Grid channels
...
UI Text Box | ||||
---|---|---|---|---|
| ||||
This section determines which channels are exported to cache files The fluid properties of a Phoenix simulation are written inside Grid Channels. Here you can choose which Grid Channels will be exported to the cache files, in the form of a voxel grid. Each channel stores a type of value, such as Liquid, RGB, Velocity and so forth, with its own range of possible values that is most efficient for that specific channel type (see the Grid Channel Ranges). Phoenix determines the fluid’s behavior at a given time, based on the content of these Grid Channels. |
UI Text Box | ||
---|---|---|
| ||
Note that the more channels are used, the slower the simulation runs and the larger the output files are. While scrolling the timeline, you can check which channels are present in the loaded cache file for the current frame, from the Cache File Content list in the Simulation rollout. Also note that in the case of FLIP / Liquid simulations, currently only Liquid . Currently, only the liquid particles can be automatically converted to a grid during export, while all the other systems (e.g. Foam, Splash, etc.) are exported only as particles. |
...
Section | |
---|---|
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
...
|
...
|
...
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
Anchor | ||||
---|---|---|---|---|
|
Using Environment Variables with Phoenix Paths
...
There are path environment variables in every OS, and they can be used with Phoenix FD cache Phoenix cache file paths.
For example, to access environment variables in Windows 10 and Windows 8, follow these steps:
...
Using this, you can create a path (variable), give it a name, and use it for cache files in Phoenix FD.
For example, the path D:\PhoenixFD\Cache can be given the environment variable name "Cache". In the Phoenix Simulator Output rollout, you can specify the Output Path as the following:
...
Note that in order to reference environment variables, the following pattern must be used:
$env(<variable_name>) Viewtracker