Here is a quick overview of the basic steps for wedging the output of a Bifrost graph using Flow Wedging. If you prefer to look at an example that has already been set up, try the aero_combustion_wedging sample graph that's available in the Bifrost Browser.

Note that Flow Wedging is a cloud service and requires Flex tokens in your Autodesk account. The amount of tokens used is based on computation times.

• Load the Flow Wedging plug-in
• Prepare the graph for wedging
• Set up preview rendering (optional)
• Include file dependencies (optional)
• Submit the wedging job
• Download the cache files
• View the downloaded cache files in the scene
• Apply your preferred settings

Load the Flow Wedging plug-in

The Flow Wedging plug-in is installed with Bifrost for Maya, but it might not be loaded.

1. Make sure that you are running Maya 2025 with Bifrost 2.12.1.0, or later versions.

2. Open Maya's Plug-in Manager: Windows > Settings/Preferences > Plug-in Manager.

3. Make sure that flowWedging.py is loaded.

   

   If you'll be wedging often, you can set it to Auto load.

back to top

Prepare the graph for wedging

Flow wedging requires special nodes in the graph: mainly wedge_cache for writing and reading the cache files, as well as others like wedge_parameter to determine the variations.

1. Before you start, it's a good idea to remove unnecessary properties from the objects that you will be wedging. For example, for a combustion effect, you may need only the voxel_fog_density, voxel_temperature, and voxel_velocity for rendering the result and you can erase any other properties that are used only for computing successive frames. This helps to keep the size of the downloaded cache files to a minimum.

   • Use a watchpoint or a data browser to see the properties that exist on the object. See Diagnose and debug graphs.
   • Use erase_property or erase_component_properties to remove data that you don't want in the final caches. Make sure to leave properties that are essential to the object's geometry type, such as *_component, *_offset, voxel_tile_tree, and others.
   • If desired, you can cache out a few frames locally using the regular file_cache node to check their file size.

2. Custom referenced compounds that are not in your default user location may cause problems. It's a good idea to import any such compounds locally into the scene by right-clicking on them and choosing Make Editable.

3. Add a wedge_cache node to the top level of the graph, and connect the objects to be wedged into the objects port.

   

   • The output of the wedge_cache node must eventually lead to an output node. Wedging does not work if it is connected only to terminal nodes.
   • It's usually best to assign a material before the wedge_cache node so that the material will be included in the caches (as well as preview renders if you generate them). The exception is when you plan to use the VDB format for caches — the VDB format does not support material assignment, so assign the material after wedge_cache to ensure that the material is properly applied after the cache files have been read.
   • Use only one wedge_cache node per graph. Flow Wedging will process only the first node it finds in the graph that's selected for a job. However, you can connect multiple objects to the objects fan-in port of the wedge_cache node to process several objects as an array.
   • By default, the wedge_cache node's mode is set to Read or Passthrough if no File. In this mode, it will automatically read the cache files once they exist later in this procedure. However since you have not downloaded any cache files yet, it instead evaluates the upstream nodes and simply passes the result along to the downstream nodes.

4. Connect a wedge_parameter node into an input that you want to vary, and set the start and end values for the range you want to test. The wedges will be evenly spaced between these values based on the number of wedges that you specify in a later step. For example, if you have only one wedge then it will be evaluated at the midpoint between start and end; two wedges will be evaluated exactly at start and end; three wedges will be evaluated at start, the midpoint, and end; and four wedges will be evaluated at start, 1/3 of the range, 2/3 of the range, and end.

   

   • By default, start and end are auto ports that are set to float type. To vary something else such as vector3, right-click on either port and select a different value type.
   • You can use multiple wedge_parameter nodes to vary multiple inputs. However, they will not be varied independently — instead the parameters will be varied in lock-step between their respective start and end values based on the wedge being evaluated.
   • If you do not use any wedge_parameter nodes, you can still submit a job. This may be useful if you simply want to offload the generation of cache files to the cloud without any wedging.
   • As an alternative to wedge_parameter, you can use wedge_index to return the index of the wedge being evaluated (0, 1, 2, etc.) and use custom logic to specify the input value for each case.

5. At the top level of the graph, deselect all nodes. The job ports of the graph appear in the Parameter Editor. Set the Wedge values as desired.

   

   • Wedge Filename is the full path and file name for downloading the caches. A path without tokens is valid for a single cache, but keep in mind that the <wedge_index> token should be used to ensure that different wedges do not overwrite each other's files. Environment variables of the form $variable or ${variable} can be used, and will be expanded after takens are replaced. The extension determines the format of the cache files: .bob for Bifrost object files (any objects), .abc for Alembic files (meshes, particles, strands), or .vdb for VDB files (volume). Any other extension will be written as Bifrost object files.
   • Wedge Index specifies which set of cache files to read once they have been downloaded. It can also be used to specify which wedge to evaluate if you choose not to evaluate all wedges in a single job.
   • Wedge Index Count sets the total number of wedges that you want to evaluate. It is also used to calculate the fraction of the range between the wedge_parameter nodes' start and end values. The maximum number of wedges per job is 4.

back to top

Set up preview rendering (optional)

Flow Wedging can generate Arnold preview renderings that you can inspect in the Flow Job Monitor. Note that:

• Only Bifrost object (.bob) caches are supported.
• Materials should be assigned to the cache inputs in the graph (not to the cache outputs) using assign_material or a similar node.
• Materials must be defined in the graph (for example, using standard_surface_mat or Arnold_standard_volume_mat) rather than referenced from the host scene.
• GPU rendering is not supported. Make sure that Render Device is set to CPU on the Device tab in the scene's Render Settings (Arnold Renderer).

1. In the Maya scene, create a transform group and name it preview.

2. Under this group, parent any lights that you want to use for the previews.

   • You can additionally parent any extra geometry that you want to include in the previews.
   • If there are multiple renderable cameras in the scene, you can specify the one to use by including it under the preview group.

back to top

Include file dependencies (optional)

If the graph depends on external files, you must make sure they are included when the graph is uploaded for wedging. This includes image files used for textures and geometry files such as USD or Alembic used for emitters and colliders, as well as others.

To include such files:

1. Connect the filename port of a file node to an input node at the top level of the graph.

   • This creates a corresponding input parameter in the Graph Inputs section of the bifrostGraphShape node in the scene.
   • The current path is automatically copied over to the input parameter.
   • If necessary, you can modify the path in Maya's Attribute Editor.

2. Rename the port on the input node to flow_input_filename. This also renames the corresponding parameter of the bifrostGraphShape node in Maya.

3. Repeat for any additional files. Subsequent ports will have an integer appended automatically (flow_input_filename1, flow_input_filename2, etc.), and the files associated with those ports will be included when you submit a job.

back to top

Submit the wedging job

Once the graph has been prepared for wedging, you are ready to submit the job.

1. Choose Flow > Flow Wedging > Create New Job from Maya's main menu. After you sign in to your account if required, the Flow Job Monitor window launches and the Create Flow Wedging Job dialog box opens:

   

2. Set the options as desired:

   • If the scene has multiple graphs with wedge_cache nodes, make sure to set Graph Shape to the one that you want to evaluate for this job.
   • Set Wedge to evaluate the current wedge only (Wedge Index in the job parameters at the top of the graph), or all wedges.
   • Select a Worker based on the size and complexity of your scene.
   • Set Timeout and Per Execution Timeout to prevent excessive computation and token use in case there is a problem with your scene or its settings.
   • Job Name is used only to identify the job in the Flow Job Monitor. The default name is based on the names of the scene and graph.
   • Select the range of frames to cache: Time Slider for the entire scene length, Animation Range for the current playback range, or Custom to specify Start Frame and End Frame manually. However, note that simulations must start from the first frame.
   • If you set up preview rendering, set those options as well.

3. If you set up preview rendering, set those options as well.

   

   • Turn off Create Output Previews with Arnold Rendering if you want to skip generating previews for this job.
   • Select Use Render Settings Resolution and Use Render Settings File Format to use the image resolution and format set in the scene's render settings instead of the default (250 × 250 pixel PNG files).
   • Select Worker and Timeout as above.
   Note: Render Node is not implemented.

4. Click OK. The graph and any connected scene objects are uploaded to the Flow Wedging service and the Flow Job Monitor shows progress.

   

   If you receive the errors shown below, it means that you are running unsupported versions of Bifrost or Maya. Ideally, you should use the latest versions, or at least Maya 2025 with Bifrost 2.12.1.0.

   

5. You can close the Flow Job Monitor while the job gets computed in the background, and then choose Flow > Flow Wedging > Open Job Monitor to re-open it at any time to monitor progress. Click on a specific job to view details, log files, play through preview renders, and more.

   

Progress logs are saved to a local file by default to declutter the script editor as the plug-in uploads and downloads files. These are not the same as the job logs that you can download later, which contain information about the job execution in the cloud. The location of these progress logs depends on the version of Maya — for example in Maya 2026, they are in the following folders:

• Windows: %LOCALAPPDATA%\Autodesk\FlowGraphEngine\maya2026\FlowWedging.log
• Linux: ~/.local/share/Autodesk/FlowGraphEngine/maya2026/FlowWedging.log
• MacOS: ~/Library/Logs/Autodesk/FlowGraphEngine/maya2026/FlowWedging.log

Download the cache files

back to top

The cache files get downloaded automatically if you left Download Job Results checked when you submitted the job. You can also download them manually from the Flow Job Monitor in case you unchecked that option, or quit your Maya session before the download was complete, or simply need to download them again.

1. Open the Flow Job Monitor.

2. Locate the job to download, and click Download.

   

3. Select a wedge, if there are multiple wedges in the job.

4. Select the items to download (for example, All or Only logs).

5. Browse and select a folder on your disk for the downloaded files. You do not need to select the Wedge Filename location that was set on the wedge_cache node, but note that the graph will not read the downloaded cache files until you update that parameter with the new location.

back to top

View the downloaded cache files in the scene

You can begin scrubbing through the results in your scene as soon as first few frames of a wedge are available.

1. At the top level of the graph, deselect all nodes.

2. Set Wedge Index to the index of the wedge you want to view: 0 for the first wedge, 1 for the second, and so on. You may need to change the frame to see the viewport update.

3. Play through or scrub the timeline.

back to top

Apply your preferred settings

When you have found a wedge that you are happy with, you can apply it so that those input settings won't get changed when wedging further parameters. This process replaces wedge_parameter nodes with applied_wedge_parameter nodes, and wedge_index nodes with applied_wedge_index nodes.

1. At the top level of the graph, deselect all nodes.

2. Set Wedge Index to the index of the wedge that you want to use.

3. If you want to apply the current wedge only to nodes in a particular compound of your graph, navigate into that compound.

4. Choose Edit > Apply Wedge. A list of nodes that will be affected is displayed.

   

5. Set the options as desired:

   • The upper box shows the node types that will be affected, as well as a tag that will be be used to rename the affected nodes. If you want to lock the settings of only wedge_parameter nodes then you can deselect wedge_index, and vice versa.
   • Apply to current compound restricts the scope to the compound you navigated into in step 3, if applicable. If you are at the top level of the graph, it has no effect.
   • Select Skip referenced compounds to preserve nodes that are inside referenced compounds like wedge_cache. If you don't do this, then you'll need to use a new wedge_cache node if you want to continue using the same graph for further wedging.
   • Deselect any individual nodes that you want to preserve in the lower box, or choose Select All.

6. Click Apply.

7. If desired, you can now wedge other parameters by connecting new wedge_parameter or wedge_index nodes. The input values for wedges that you have applied will be maintained.

back to top