Versions Compared

Old Version 23

changes.mady.by.user Svetlin Nikolov

Saved on

compared with

New Version 24

changes.mady.by.user Slavina Nikolova

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

General

...

Section
Column
width55%

Expand – Opens a floating dialog that contains the selected rollout and automatically folds the command panel rollout.

? – Opens up the help documents for the Liquid Output.

Anchor
CachePath
CachePath

Simulation Cache Save Path | simoutput – This is the directory and the name template for the output cache files. It uses the $(scene_path) macro by default, and there are also other available macros as listed below. To set up rendering and simulation cache paths manually, see How to change the default Phoenix paths on the Tips and Tricks page.

Column
width5%

 

Column
width40%

Image RemovedImage Added

 

 

UI Expand
titleClick Here to expand additional $(VARIABLE) information

$(scene_path) – $(data_dir)\$(scene)_Phoenix_frames\$(nodename)_####.aur
$(scene_dir) – $(data_dir)\$(scene)_Phoenix2_frames\ND$(handle)_$(nodename)_####.aur
$(implicit) – Same as $(scene_dir)
$(dir) – The scene directory.
$(data_dir) – The default directory where cache files are written. By default this is $(dir), meaning that the cache files are written next to the scene file, but it can be overridden with a custom directory from the Phoenix Global Preferences.
$(scene) – The scene file name.
$(handle) – A unique number of the node.
$(nodename) – The name of the node.
$env(<variable_name>) – An environment variable. See Using Environment Variables below.

#### 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:

 

Align
aligncenter
 Result
Frame Number#######
11010001
1010100010
1000100010001000
UI Text Box
typenote

Since version 3.00.02, Phoenix can export VDB grid data. Check the How to export Phoenix FD simulation to OpenVDB format video.
Appending a .vdb extension after the Output Path tells Phoenix to write its data in the OpenVDB format.

Particle data can also be exported using the .aur or the .vdb format. Phoenix can convert particles from already simulated Phoenix .aur caches into the .prt format as a post-process using the Phoenix Export PRT Particles dialog or to .vdb format using the Cache Converter tool.

Image RemovedImage Added

UI Text Box
typeinfo

 Clicking the "..." button will open a menu with the following options:

Image RemovedImage Added

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.

...

Section

Example: Particle compression artifacts

 

 

UI Text Box
typeinfo

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
Column
width33%

Storage quality = 19

Column
width33%

Storage quality = 14
(artifacts in the lower left corner)

Column
width33%

Storage quality = 8

...