I connected two File Pattern nodes (Low-poly and High-poly) to a Partition by Index node, but only the information from one File Pattern node is being displayed.
How can I output and view the data from both File Pattern nodes simultaneously?
How to merge two File Pattern nodes in Houdini TOPs?
1011 1 0-
- rudgus1228
- Member
- 2 posts
- Joined: 4月 2019
- Offline
-
- hellencharless54
- Member
- 3 posts
- Joined: 5月 2026
- Offline
This usually happens because Partition by Index is only effectively receiving/processing one stream of work items, even though you’ve visually connected two File Pattern nodes.
In most node-based PDG/TOP-style setups, each upstream branch is treated separately unless you explicitly merge them into a single stream.
What’s going wrong
Each File Pattern node generates its own set of work items
Partition by Index expects a single combined stream
Without combining, one input often ends up overriding or being prioritized in the display
How to fix it
1. Add a Merge node (most common fix)
Place a Merge node between your File Pattern nodes and Partition by Index:
File Pattern (Low-poly) ─┐
├── Merge ── Partition by Index
File Pattern (High-poly) ─┘
This forces both datasets into a single unified stream so Partition can actually see everything.
2. Verify display vs actual data
Sometimes only one branch shows in the viewer even though both exist:
Click the Merge node and inspect work items
Then check Partition output separately
3. Alternative (if you need strict separation)
If you actually want to keep them distinct:
Use two separate Partition nodes (one per File Pattern)
Or tag each stream first (attribute like source=low/high) and partition later
Key idea
Partition nodes don’t “visually combine inputs” — they operate on whatever single stream they receive, so you always need an explicit merge when working with multiple generators.
In most node-based PDG/TOP-style setups, each upstream branch is treated separately unless you explicitly merge them into a single stream.
What’s going wrong
Each File Pattern node generates its own set of work items
Partition by Index expects a single combined stream
Without combining, one input often ends up overriding or being prioritized in the display
How to fix it
1. Add a Merge node (most common fix)
Place a Merge node between your File Pattern nodes and Partition by Index:
File Pattern (Low-poly) ─┐
├── Merge ── Partition by Index
File Pattern (High-poly) ─┘
This forces both datasets into a single unified stream so Partition can actually see everything.
2. Verify display vs actual data
Sometimes only one branch shows in the viewer even though both exist:
Click the Merge node and inspect work items
Then check Partition output separately
3. Alternative (if you need strict separation)
If you actually want to keep them distinct:
Use two separate Partition nodes (one per File Pattern)
Or tag each stream first (attribute like source=low/high) and partition later
Key idea
Partition nodes don’t “visually combine inputs” — they operate on whatever single stream they receive, so you always need an explicit merge when working with multiple generators.
-
- Quick Links
