Versions Compared

Old Version 27

changes.mady.by.user Slavina Nikolova

Saved on

compared with

New Version 28

changes.mady.by.user Slavina Nikolova

Saved on

Key

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

...

Parameters

...

Section
Column
width40%

Help – Opens up the help documents for the Resimulation.

Use Simulation Start Frame | rs_start_from_sim - When enabled, the Resimulation will run from the first frame of the base simulation to the simulation End Frame or the Custom Stop Frame, depending on the options.

  • Custom Start Frame | rsStartFrame – Explicitly sets the Start frame of the Resimulation. This can also be a negative number.

Use Simulation Stop Frame | rs_stop_from_sim - When enabled, the Resimulation will run from the base simulation Start Frame or the Custom Start Frame to the last frame of the base simulation.

  • Custom Stop Frame | rsStopFrame – Explicitly sets the End frame of the Resimulation. This can also be a negative number.
Column
width60%

Image RemovedImage Added

 

Particle Resimulation

...

UI Text Box
typetip

During resimulation, Phoenix reads cache files from the Base Cache Files Path, performs resimulation operations, and then saves a new cache sequence in the Output and Render Path.

For information on changing the default paths for resimulation, see the Tips and Tricks page.

Section
Column
width40%

Wait if caches are missing | rsWaitMode – When enabled, waits if the base cache file is not yet available. This can be used if another instance of Maya is simulating the base cache at the same time (on the same or other computer).

Base Cache Files Path | rsInput – Specifies the base simulation caches which will be read as base for resimulation. $(same_as_output) by default. The field below shows the resolved full path.

Output and Render Path | rsOutput – Specifies the path for writing the output cache files from Fire/Smoke resimulation. Note that Liquid resimulation overwrites the files in the Base Cache Files Path and also uses that path for preview and rendering. See the Simulation Save Path parameter in the Output Rollout for more details on the $(...) macros you can use. The field below shows the resolved full path.

Click the "..." button to open a menu with the following options:

Browse - Opens a dialog where you can select where the resimulation caches will be written to. The filename you type in must contain # signs so each resimulation frame will be written to a differently numbered file. Also, you can choose between two file formats - AUR and VDB cache files. 

Delete Cache Files - Clears the resimulation files.

Reset to Default - Resets the resimulation path to default.

Help - Opens this Help help page.

UI Text Box
typewarning

You can use the same Output and Render Path as the Base Cache Files Path, and this way Phoenix will not create a separate cache sequence for resimulation, but will overwrite the base simulation caches instead. It's valid to do so if you need a more complicated setup or when not enough disk space is available. This way you can increase the resolution more and more each time you start a resimulation.

UI Text Box
typeinfo

 The following error message may appear when you start a re-simulation:

"Cannot start the Re-Simulation! Please make sure the simulation was run with the 'Velocity' channel checked under the 'Output' rollout, and that the cache files in the Simulation Input path exist."

The reason may be that either the files in the Input Simulation Path do not exist at all, or they do not have Grid Velocity Channel exported when you have simulated them beforehand. Of course, you may use more complicated setups where you resimulate over an already resimulated cache file, or you may Load an existing base cache file as the initial state of the re-simulation. These are all possible; you just need to have velocity in the base cache and an existing path to it.

Column
width60%