Versions Compared

Old Version 5

changes.mady.by.user Svetlin Nikolov

Saved on

compared with

New Version 6

changes.mady.by.user Slavina Nikolova

Saved on

Key

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

...

Fancy Bullets
typecircle
  • Increase resolution while keeping the shape and behavior. (It's possible to add wavelet turbulence to increase detail or simply amplify the resolution)
  • Slow down or speed up the animation, as well as apply animated time scale using Phoenix's Time Bend controls. See Slowing Down a Simulation, Animating the Time-Scale, etc.
  • Keep the grid channels such as Smoke, Temperature, etc. unchanged and only change the dynamics or number of Drag particles, or vice versa.
UI Text Box
sizemedium
typetip

You can resimulate over the resimulated caches and so on - it's not necessarily just 2 passes at most. 

UI Text Box
sizemedium
typenote

Due to the difference between the compression algorithms used by Phoenix FD's Aura format and the OpenVDB format, the resimulation process may produce a different result when using exported VDB caches as opposed to Aura caches if the Storage Quality option in the Output roll-out rollout is set to a value lower than 20 (i.e. Lossless).

Section
Div
stylemargin-top: 10px
idFireSmoke_Resimulation_Overview

Rendering and simulation cache paths can be set manually. For information on how to do this, see the Tips and Tricks page regarding simulation paths and resimulation paths.

When performing a resimulation, it is recommended that you leave the Dynamics settings unchanged between running a base simulation and resimulation unless more advanced behaviors are specifically needed.

Additionally, the scene must be intact between running the base simulation and the resimulation. Please do not remove any Sources and their emitters, obstacles or forces that interact with the simulation.

 

The resimulation workflow for Fire/Smoke is as follows:

 

UI Steps
UI Step
Section
Column
width40%

Enable Velocity in the Output rollout. If you are going to add wavelet turbulence as well, also enable Wavelet.

Column
width60%

UI Step
Section
Column
width40%

Start the original (base) simulation and let it run through.

Column
width60%

UI Step
Section
Column
width40%

Enable Grid Resimulation or Particle Resimulation. Adjust the resimulation options in this rollout if needed.

Column
width60%

UI Step
Section
Column
width40%

Start the simulation again - this time the Resimulation will take place. You can switch between preview and render of the base and resimulated caches by enabling/disabling the Resimulate checkbox.

Column
width60%

 

 

medium
UI Text Box
size
typetip

UI Path: ||Select Fire Smoke Simulator | FireSmokeSim|| > Modify panel > Resimulation rollout

 

Parameters

...

Anchor
EnableParticleResimulation
EnableParticleResimulation
Particle Resimulation

...

...

 

Div
stylemargin-top: 10px
idFireSmoke_Resimulation_EnableParticle

Enable | resim_resimulate_particles – Enable/disable the particle resimulation. Use this option to modify the look of Drag particles. The resimulation will produce the exact same result as the base simulation only with Steps per Frame = 1 in the Dynamics rollout. With a higher number of steps, the intermediate steps cannot be reconstructed, so full simulation is needed.

 

 

Anchor
EnableGridResimulation
EnableGridResimulation

Div
idFireSmoke_GridResimulation

Grid Resimulation

 

 

Div
stylemargin-top: 10px
idFireSmoke_Resimulation_EnableGrid

Enable | resim_resimulate_grid – Enables/disables the grid resimulation. Use this option when the grid detail has to be improved by increasing the resolution, by eventually adding wavelet turbulence, or if you need to re-time your simulation using Time Bend effects. The resimulation will produce the exact same result as the base simulation only with Steps per Frame = 1 in the Dynamics rollout. With a higher number of steps, the intermediate steps cannot be reconstructed, so full simulation is needed.

Div
stylemargin-top: 10px
idFireSmoke_Resimulation_AmpResolution

Amp. Resolution | resim_ampres – Magnifies the grid resolution. A value of 0.0 means no change, 1.0 means doubling the voxel amount in all axes (2*2*2=8 times the resolution), 2.0 means tripling (3*3*3=27 times the resolution), etc. Non-integer values can also be entered, however, they are slightly slower to calculate. The resolution can also be decreased by using a negative value.

Div
stylemargin-top: 10px
idFireSmoke_Resimulation_AmpMethod

Amp. Method | resim_ampmeth – When the grid resolution is increased, this parameter specifies which method to use to sample the velocity.

Interpolate – Use interpolation. The velocity channel is stretched from the lower resolution to the increased one.
Wavelet Fast – Use wavelet turbulence to synthesize fine detail. Needs a Wavelet channel exported from the base simulation. This is a slightly faster approximation method.
Wavelet Nice – Use wavelet turbulence to synthesize fine detail. Needs a Wavelet channel exported from the base simulation.

Div
stylemargin-top: 10px
idFireSmoke_Resimulation_WaveletStrength

Wavelet Strength | resim_wvstr – Specifies the strength of the wavelet turbulence.

Div
stylemargin-top: 10px
idFireSmoke_Resimulation_WaveletCutoff

Wavelet Cutoff | resim_wvcut – Turbulence with smaller amplitude will be cut off to reduce calculation time.

Div
stylemargin-top: 10px
idFireSmoke_Resimulation_NoExportChannels

No-Export Channels | resim_tmpchan – Specifies the channels that are used just for resimulation, which will not be exported to the resimulation output cache. For example, for wavelet turbulence, removing the UVW/Wavelet and Velocity channels from the final simulation will reduce the cache size.

...

Section

Example: Resimulation with Wavelet Turbulence

 

 

medium
UI Text Box
size
typetip

The example below shows the difference between a base Fire/Smoke simulation and the Resimulation result when using Wavelet Turbulence.

Section
Column
width10%

 

Column
width40%


Base Simulation 

Column
width40%


Resimulated with Amplify Resolution = 1
and Wavelet Nice Method

 

Column
width10%

 

Anchor
TimeBendResim
TimeBendResim

...

Phoenix has many tools for changing the animation timing of a cache sequence after it is simulated. Resimulation with enabled Time Bend Controls can produce smoother playback in cases where the Input Time Bend controls are insufficient. For more information on Resimulating with Time Bend, see the Tips and Tricks topic on How to slow down a simulation, animate the time scale, etc.

...

 

Div
stylemargin-top: 10px
idFireSmoke_Resimulation_UseTimeBend

Use Time Bend Controls | resim_grid_timebend – Change the time scale of the base simulation according to the Time Bend Controls in the Input rollout. You need to re-scale the animation of all other interacting objects and sources in the scene as well. For constant play speed, use 3ds Max's Rescale Time feature.

...

Section

Example: Time Bend Resimulation

 

 

UI Text Box
sizemedium
typetip

The example below shows the difference between the Input roll-out rollout → Frm.Blend Interpolation used to slow down without resimulating, the Resimulation → Slow Down Time Bend Method and the Resimulation → General-Purpose Time Bend Method.


Section
Column
width5%

 

Column
width30%

Input Play Speed = 0.2, Interpolation Blend

 

Column
width30%


Slow Down method + Wavelet 

Column
width30%


General-Purpose method + Wavelet

 

 
Column
width5%

 



Resimulation Cache

...

medium
UI Text Box
size
typetip

During resimulation, Phoenix reads cache files in the Input Simulation Path, performs resimulation operations, and then saves a new cache sequence in the Output Simulation path.

For more information on how to set up resimulation paths, see the Tips and Tricks page.

...

Help - Opens this Help page.

 

UI Text Box
sizemedium
typewarning

If the Output and Render Path coincides with the Base Cache Files Path, Phoenix FD will not prevent you from overwriting your existing cache files. It's valid to do so if you need a more complicated setup or when not enough disk space is available.

UI Text Box
sizemedium
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' roll-outrollout, 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.

Viewtracker
hidetrue
renderusernamesfalse