Versions Compared

Old Version 1

changes.mady.by.user Gosho Genchev

Saved on

compared with

New Version Current

changes.mady.by.user Kristin Ivanova

Saved on

Key

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

This page introduces the FireSmokeSim object and its rollouts.

 

Section
Column
width50%

 Section Contents

Page Tree
expandCollapsefalse
root@self
themenone

Column
width50%

 Page Contents

Table of Contents
stylecircle

Overview

...

Div
stylemargin-top: 10px
idFireSmoke_Overview
Section
Column
width50%

The Fire/Smoke

Simulator

simulator is intended to produce

realistic

gaseous effects like fire, smoke and

explosion effects. The dynamics governing the simulation are based on real-world physics.

The Fire/Smoke Simulator uses a grid-based core (a 3-dimensional array of voxels). The simulated channels are transferred through the grid based on the specified parameter values. The result of the simulation is a sequence of cache files containing the simulated channels (Temperature, Smoke, etc). These cache files are used later in the rendering process to convert the raw simulation data into realistic images.

explosions, as well as sparks or embers.

You can think of the simulator as a 3D box, inside which simulations of fluids and Rigid Body Dynamics are performed. Fire/Smoke simulations are grid-based, meaning they consist of an array of voxels that contain the fluid's properties at a position and given time, such as the fluid’s temperature, its velocity, its color, and so forth.

These fluid properties are written inside what are called Grid Channels. Each channel stores a type of value, such as Temperature or Velocity, with its own Grid Channel Range, which is the range of possible values that is most efficient for that specific channel type. Phoenix determines the fluid’s behavior at a given time, based on the content of these Grid Channels.

When running a simulation, the Fire/Smoke sim will typically output an entire animation sequence. That sequence is saved as individual files, called caches, which contain raw simulation data for each timeline frame. In essence, the cache data contains grids and particles, which describe the fluid’s behavior.

Fire/Smoke sim cache files can then be previewed in the viewport, as well as rendered, in order to create captivating and realistic images. The simulator offers multiple render modes, where the volumetric render modes are typically used for rendering Fire/Smoke sims, and the mesh render mode is typically used for Liquid sims. Phoenix offers a lot of flexibility though, so there is the option to render Fire/Smoke sims as meshes and Liquids as volumes, in order to achieve even more diverse effects.

Column
width50%

Image Added

UI Text Box
typenote
Note that the
The
simulator is represented as a single object for convenience. Internally, it contains two completely separate parts: a simulator component and a rendering component. Parameters that control the simulation are separated from those associated with the shading and rendering processes. As a result, no roll-out will contain mixed parameters, and no parameter will affect both the simulation and rendering.
 
Section
UI Expand
titleUI Path: ||Create panel|| > Geometry > PhoenixFD category > FireSmokeSim button
Image Removed

...

Image Added

 


Rollouts

...

After creating a FireSmokeSim object, the following rollouts can be accessed in the Modify panel:

Fancy Bullets
typecircle

  • Simulation - Controls the simulation and displays

    statistical information.

    statistics such as simulation times, as well as information about the data contained in the sim for the current frame.

  • Simulation Speed - Helps identifying the heaviest computation phases of the simulation and provides tips on how to get results faster and more efficiently.

  • Resimulation - Uses a base simulated cache sequence with exported velocity to drive a new simulation. Capable of adding time effects, increasing the resolution, etc, in order to enhance details, increase its resolution, or slow down or speed up the simulation.
  • Grid - Controls the boundaries, size and resolution of the simulation grid.
  • Dynamics - Controls dynamics Offers parameters to affect the fluid’s behavior when simulating, such as cooling, smoke dissipation, vorticity, advection, etc.
  • Fuel - Controls the simulation of burning when Fuel is present in the simulation, which is useful for creating gasoline explosions or propagating fire effects.
  • Scene Interaction - Specifies how the FireSmokeSim interacts with other objects in the scene.
  • Output - Specifies how and where the simulation cache files are saved.
  • Input - Determines the path of the input files for rendering and previewing, and offers settings and controls for playback.
  • Preview - Controls how the simulation is displayed in the viewport.
  • Rendering - Controls how the simulation is rendered, and includes additional volumetric options for shading Fire/Smoke simulations.
  • Export - Controls exporting meshes and particles from Phoenix.
  • Authorization - Displays information when license information cannot be obtained.

...

Upgrading from Previous Versions of Phoenix

...

...

Due to many improvements to the Phoenix solver, recreating simulations the same way you did in older versions of Phoenix may not be possible because of changes to the solvers and the UI. Here are some things to be aware of when upgrading from older versions of Phoenix FD.


Fancy Bullets
typecircle
 If

  • If you have a scene created with Phoenix

v.2

  • version 3 and you open it with version

3

  • 4, it will keep all the old settings for you, including some

of

  • which are not visible to newer versions

and the result should

  • , in order for the results to be roughly the same.

  • If you try to manually replicate

the same

  • an older simulation setup with

Phoenix v.3

  • a new Phoenix simulator using Phoenix version 4, and set all the parameters with the same values as the older version, you

would

  • may not obtain the same result

. The new simulation will be different because Phoenix v.3 uses

  • as in Phoenix version 3 or older. 

  • Since the release of Phoenix version 3, Phoenix started using a new solver for liquids and fire/smoke

.

 

...

  • simulations, so simulation results will be different between Phoenix version 3 and version 2.


Viewtracker
hidetrue
renderusernamesfalse