Setup Presets¶

Open Presets in the Pro Particles, Pro Pyro or Pro Terrain panel, or in the Pro Physics or Pro Terrain node editor header. The Preset Manager stores a global library that is available across Blender projects and sessions.

For reusable parameter curves, use Curve Presets directly from a curve editor.

Preset types¶

A Collection contains the complete configurations of both systems. It can be exported and imported as one JSON file without depending on separately saved presets. Both systems must be created before saving a Collection.

For Particles and Pyro, only the active Lists or Nodes document is saved. Loading switches that simulation to the saved mode. The independent inactive document remains available. In the shared Pro Physics graph, a single-system preset preserves the other simulation's branch. Use a Collection when transferring a coupled Particles/Pyro graph to another project. A Physics Group containing both simulations requires a Collection. When a single preset replaces a connected branch, its matching source nodes must be present so the existing cross-simulation links can be retained.

Pyro Particle Stream connections require Particles Nodes mode. Disconnect those links before applying a Particles Lists preset, or apply a Collection with compatible modes. An incompatible mode change is rejected before replacing the scene setup.

Save and apply¶

1. Select Particles, Pyro, Collections or Terrain in the manager.
2. Choose Save Active Setup, enter a name and save. Names must be unique within that preset type.
3. Choose Apply next to a saved preset.
4. Check Scene References. Assign missing objects or assets, including any unassigned source slots, then choose Replace Setup.

Applying replaces the selected setup after confirmation and clears its results. Blender Undo restores the previous configuration. For Particles and Pyro, stop running bakes, exports and catch-up jobs before applying. Terrain preview builds are cancelled when replacing their graph; terrain exports in the scene must finish or be cancelled first. Undo does not add or remove entries in the global preset library.

A preset can also create its simulation in a scene without an existing setup. Assign its Scene References when applying. A Collection creates both simulations with their saved authoring modes.

Groups with matching names reuse their scene IDs. Conflicting IDs are assigned separately, and the incoming references are updated. Groups used by the inactive Lists or Nodes setup remain available.

Terrain presets¶

Select the target terrain in the Pro Terrain panel before choosing Apply. The confirmation dialog names the terrain that will be replaced. In a scene without an active terrain, applying creates a new one. Other terrain graphs, Particles and Pyro setups remain available. Collections contain Particles and Pyro only; save terrains individually.

If a pinned Pro Terrain node editor displays a different graph, select the terrain using that graph in the sidebar before saving or applying. If the active terrain changes while the confirmation dialog is open, reopen Apply for the new target.

Use Saved Dimensions is off by default. Enable it to apply the saved Terrain Size and Height Scale, including any animation on those two settings. Both controls affect every terrain in the scene. Preview Resolution, Display Mode, Auto Update, Preview Lighting, Node Cache and drawing-tool settings retain their scene values.

The replaced terrain's preview is cleared. With Auto Update enabled, the new graph is calculated automatically. Otherwise, choose Refresh Terrain Preview. Applying a preset does not execute its export nodes.

Terrain Palette ramps and Mask Curve curves are included and remain independently editable after loading. Drawing Field objects are scene references: assign existing curve objects under Scene References, including any unassigned Drawing slots. Their geometry is not embedded. Heightfield source files must be provided separately, and saved input and export paths retain their values.

Objects and animation¶

Presets store settings and named references to existing Blender assets. They do not contain mesh geometry, object transforms, object animation, materials, images or external Geometry Nodes definitions. Matching names and library sources are assigned automatically. The application dialog allows you to select replacements of the appropriate type.

Vertex-group and attribute names used by emission masks and collider Data Mapping with Source: Weight Map are included as references. This also includes Maps selected through Physics Group inputs. Collider mappings with an empty Map are saved without a map requirement and leave the parameter unchanged. Their weights are part of the mesh and are not embedded in the JSON. Scene References lists the required map names. Each assigned mesh must provide them before the preset can replace the setup. Use a .blend file to transfer meshes with their painted maps.

Editable color ramps, mapping curves and Physics Group definitions belong to the setup and are included. Parameter keyframes, NLA clips and simple numeric Blender drivers are included for the saved setup. Drivers that depend on custom Python expressions cannot be saved as JSON presets. Use a .blend file to transfer a complete scene with its assets and custom scripting.

Animated parameters retain their Action blending, influence, extrapolation and NLA enable state. Blender shares these settings with other animation on the same scene or node tree. If different playback settings would change unrelated animation, applying is rejected before replacing the setup. Match those settings first, or include both affected simulations in a Collection. Exit NLA Tweak Mode before saving or applying animated presets.

Cache locations and output paths retain their saved values. Cache files, Initial State files and completed simulation results are not embedded; provide those files separately where required. The Particle Initial State collection contains scene-owned captures and is excluded from presets. Capture new entries after applying a preset.

Import, export and deletion¶

• Export writes the selected preset or Collection to a JSON file. Choose any filename and destination in Blender's file browser.
• Import JSON adds a preset to the global library. It does not apply it to the scene. An optional name can be entered during import. Duplicate imported names receive a numbered suffix.
• Rename changes the library name.
• Delete asks for confirmation before removing the library entry. Exported JSON files and existing scene setups remain available.

Use Search to filter presets by name within the selected type. Page browses the filtered results. The Pyro Preset Setup examples remain separate from the global setup library.

The library is shared between Blender instances. Changes from another instance appear when the manager redraws or is reopened. If another instance is writing the library, an operation may report that it is busy. Retry the operation after that write finishes.