In brief
- Wedge TOP creates a separate work item for each defined variation.
- Values can be generated as a range, selected from a list or sampled at random.
- Variations can be accessed with @attribute expressions or applied to a target parameter.
- Multiple Wedge nodes can be chained to create combinations of variations.
As described in the Houdini 22.0 documentation, Wedge TOP lets you compare options by turning different geometry or render setting values into separate work items. Each work item carries one or more variation attributes, which can then be used in a render node or in a network or digital asset called by the TOP network. The first documented version of the Wedge node is Houdini 17.5. The methods in this guide are based on SideFX’s TOPs and Wedge TOP documentation.
1. Plan your variations
First, choose the parameters you want to compare. In SideFX’s example, changing wall height, brick count and color hue produces different walls from the same base asset. In architectural visualization, this approach can be used to test different geometry or material properties of a base asset. Wedge TOP isn’t limited to image previews; it can also be used to generate different prop variations ahead of time or during rendering.
A single Wedge node can change multiple attributes at once. These vary independently according to the number of variations selected. If you need to create every possible combination of different attributes, you can chain multiple Wedge nodes. A Wedge with an input connection generates its own variations for each incoming work item, so it’s important to plan the total number of jobs in a layered setup.
2. Create work items with Wedge TOP
Add a Wedge node to the TOP network. Since work items generated by render nodes are created per frame for each incoming work item, place Wedge before the render node to render the variations.
Add a variable in the Wedge Attributes section and name it in the Attribute Name field. If you’re changing multiple settings, define a separate attribute for each one.
Choose a suitable data type from Attribute Type. The documentation lists Float, Float Vector, Integer, Integer Vector, String and Color. Vector types can be used for values with two to four components.
Set how values are generated with Wedge Type. Range distributes values evenly between Start and End; if Random samples is enabled, values are selected randomly from the range. Value uses a fixed value or an expression evaluated for each work item.
Set Wedge Count to the number of work items the node should create. A Range definition is divided into that many steps. If you use a list of values and the number of items exceeds the number of values in the list, the list is used cyclically.
| Setting | Options or value described in the documentation | Effect |
|---|---|---|
| Wedge Type | Range or Value | Determines whether values are generated across a range or from a fixed value or expression. |
| Random samples | On or off | With Range selected, generates random values from the range instead of distributing them evenly. |
| Wedge Count | Numeric value | Sets the number of work items to create; range definitions are divided into that many steps. |
| Attribute Type | Float, Float Vector, Integer, Integer Vector, String or Color | Sets the data type of the variation attribute. |
3. Connect variations to parameters
There are two ways to use a generated attribute. The first is to read the work item’s value using an @attribute expression in the relevant render parameter or another node run by the render. This “pull” method is flexible, but it requires TOPs-specific expressions, so it may not be suitable if the relevant node will also be used manually outside TOPs.
The second method is to target a parameter in the scene using the Target Parameter option in Wedge Attributes. This “push” approach applies the variation value to the target parameter at runtime, allowing you to change parameter values without using a TOPs-specific expression. Use the selector in the Target Parameter field to specify the node and parameter. The Set Value As setting lets you set the target parameter to a reference to the work item attribute, an explicit value or an expression.
Use caution with the Overwrite Target Parameter on Work Item Selection option, which also changes the target parameter when a work item is selected. The documentation notes that this preview can actually change the parameter, trigger a recook and leave the HIP file unsaved. Since preview changes may be saved when you save the file, check the target value and restore behavior.
4. Render and compare results
Connect render nodes after Wedge to create render work items for each variation. If you’re calling a network or Houdini digital asset, you can connect the attributes generated by Wedge to its parameters. In SideFX’s example workflow, geometry is generated from the variations, rendered and combined into a mosaic image. This makes it easier to review the results side by side rather than enabling and disabling options one at a time.
The same approach can be used for simulations: after creating base scene variations, you can add a new Wedge for RBD settings, followed by another Wedge for smoke settings. The documentation illustrates these examples with walls, a wrecking ball and smoke simulations. For architectural visualization teams, the main benefit is turning repetitive variation generation into work items and reviewing the results together. However, the number of jobs can grow along with the number of Wedge nodes and the connected render or simulation tasks. The documentation states that TOP jobs can run on a local computer or a server farm, so available hardware and job planning should be considered in the production workflow. No specific hardware requirements or time savings are stated here.
Common mistakes
Placing Wedge after the render nodes; the documentation recommends putting the node before rendering so variations are properly propagated to render jobs.
Forgetting to connect an attribute that changes a parameter to the target parameter or an
@attributeexpression. Creating an attribute alone does not change a parameter in the scene.Overlooking the effect that multiple Wedge layers have on the number of jobs. Nodes with inputs can generate new variations for each incoming work item.
Failing to account for how the preview that changes target parameters when a work item is selected may affect scene values and whether the HIP file is saved.
These features are described in the SideFX documentation in the context of Houdini 22.0 TOPs; the Wedge TOP node page lists “Since 17.5” for the feature. Since the documentation doesn’t specify a menu path, no particular interface path is assumed here.
Sources
3 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
For architecture and visualization offices in Turkey, Wedge TOP’s practical value is that it makes it possible to generate and compare alternatives to the same scene as organized work items, rather than duplicating them manually. Reviewing results together can make the workflow easier to follow, especially for repeated geometry, material or simulation tests.
However, the number of variations and render jobs can grow quickly, so it’s worth testing the scope of the work with a small test set before moving into production. The documentation doesn’t specify hardware requirements, time savings or licensing terms; it mentions the option to run jobs on a local machine or a server farm. It’s also important to remember that scene parameters may change in the push preview.
Frequently asked questions
What is Houdini Wedge TOP used for?
It creates separate work items for different values of one or more attributes. This lets you generate geometry, render or simulation variations.
How does Wedge TOP generate values?
Range distributes values between a start and end point, Random samples selects random values from that range, and Value uses a fixed value or expression.
Which Houdini version supports Wedge TOP?
SideFX’s TOPs documentation is included in the Houdini 22.0 documentation. The Wedge TOP node page lists “Since 17.5” for the feature.



