Skip to content
AnimationStudiosBLUX Physics SuiteGet BLUX
Discord

Bake, upres and checkpoints

The Simulation Output node of a Blaze graph has a Mode that decides what Run and Bake do.

Mode What it does
Live The interactive preview. Nothing is cached unless Bake on Preview is on. Keep as Bake promotes those cached frames to a bake.
Bake Writes VDBs at the simulation’s resolution, with velocity and rest grids (the rest grids are optional).
Bake + Upres Bakes, then adds sub-grid detail at 2x, 3x or 4x.
Upres from Cache Re-runs only the upres pass over an existing bake.

Bake on Preview caches a live run’s frames at the live settings: smoke, heat, fuel and flame, with no velocity or rest grids.

Upres uses wavelet turbulence (Kim, Thürey, James and Gross, 2008). Smoke, fire and heat are re-advected at 2x, 3x or 4x the resolution through the simulation’s velocity plus divergence-free wavelet noise. The noise follows the gas and is scaled by the simulation’s own turbulent energy. Their coarse shape is kept equal to the simulation’s.

Setting What it does
Upres 2x, 3x or 4x the simulation’s resolution.
Upres Turbulence Amplitude of the sub-grid turbulence, relative to the estimate from the simulation’s own turbulent energy. 0 keeps only the smooth upsampled gas.
  • Velocity, burn and the rest fields stay at the simulation’s resolution in the same VDB.
  • Upres from Cache lets you change the upres settings without re-simulating.
  • Upres runs in bakes only, never in the live preview.
  • 4x costs several times the simulation itself, and 64 times the voxels on disk.

A bake writes a checkpoint of the whole solver state every Checkpoint Every frames. The default is 10, and 0 turns it off.

Button What it does
Resume Bake Continues an interrupted bake from its last checkpoint.
Re-bake from Here Re-simulates from the checkpoint at or before the current frame. Use it after changing something late in the shot.
  • Only checkpoints of the same scene and settings are used.
  • An upres pass restarts after a resume.
  • A checkpoint of a full 128³ dense grid is about 120 MB. They live in the cache folder and count toward the disk budget. See Cache and budgets.

Baked frames are sparse OpenVDB files, one leaf per 8³ brick of gas, with Blender’s grid names: density, temperature, flame, fuel and velocity, plus burn and the rest fields.

  • temperature is absolute kelvin, so Blender’s own Principled Volume reads it too.
  • Half-Float VDB on the Simulation Output node (on by default) stores 16-bit floats: a quarter to a third less disk space, three significant digits, and no visible change in a render. Upres from cache keeps its base grids at full precision.
  • Two rest-offset grids (rest_offset, rest2_offset) let the render noise move with the smoke. Each restarts every Rest Reset frames (24 by default). Rest Grids and Scatter Grid on the Simulation Output node (VDB Cache) leave the rest offsets or the scatter grid out of the files. They do not change the cache identity, so switching them keeps the cached frames.

Caches baked by an older build stored temperature in solver units and render too cold. Re-bake them.

A bake writes one volume_NNNN.vdb per frame. Export VDB Sequence (Simulation Output > VDB Cache) copies them. This is what is in a file, and how to shade it without the Blaze material.

Grid Holds Notes
density Smoke, 5× the solver’s (the default Look’s Density Scale, so a plain material at Density 1 shows the same smoke). Always written. File key blux_density_gain = 5.
flame Flame, 15× the solver’s (peak about 30). File key blux_flame_gain = 15.
temperature Kelvin, 0 where there is no heat. File key blux_temperature_unit = K.
fuel, burn Unburnt fuel, and the burn rate. Left out when empty.
velocity World units per frame, for motion blur. Only where gas is.
rest_offset, rest2_offset Where the Blaze material’s detail noise samples. Only where gas is. Simulation Output > Rest Grids.
scatter A coarse grid of fire-lit smoke. Simulation Output > Scatter Grid.

A voxel is stored only above 0.3% of its grid’s peak in that frame (never under 1e-4, and temperature is judged on its excess over ambient, not on kelvin). A file holds the gas that is visible rather than the whole box. A grid with nothing active, such as the burn grid of a burnt-out frame, is left out. The Ground Explosion’s frame 70 is 1.9 MB at Draft, 11 MB at Standard and 40 MB at Production quality. The rest grids are about a third of a file: switch Rest Grids off if you only use the plain material below.

A volume object that loads the file, with a Principled Volume and three settings, is enough to render fire and smoke:

  1. Density: an Attribute node named density, its Fac to the Principled Volume’s Density.
  2. Emission Strength: an Attribute node named flame, its Fac to Emission Strength.
  3. Emission Color: Blackbody at 2100 K.

No multiplier is needed. Blender’s default Render Space (Object) applies density and emission per object unit. An EmberGen file’s unit is its voxel and ours is a metre, so the flame is written 15× the solver’s. A plain material then shows about the fire EmberGen’s file shows: on the Ground Explosion at frame 70, 0.33 flame per line of sight, against 0.38 in EmberGen’s frame 71. The gain was matched at the Ground Explosion’s scale, a 10 m box.

Under Render Space Object, a plain material’s fire per line of sight grows with the effect’s size in metres, while an EmberGen file always counts voxels. A small effect (Candle, Moving Torch, Campfire) therefore looks dimmer in a plain material than an EmberGen file of a similar effect. Raise the material’s Emission Strength and Density for it, by about the Ground Explosion’s voxel size (0.05 m) over the effect’s.

A material that keys on flame values (a Color Ramp band on flame) needs its stops multiplied by 5 for new bakes. Files from older bakes carry no gain keys and keep their old values. EmberGen files use the same recipe with the attribute flames instead of flame.

Export a bake as an OpenVDB sequence, or as a game-engine flipbook. See Baking and exporting and Spritesheets.