Mike Sawicki
digzelot
About Me
INDUSTRY
Gamedev
Connect
LOCATION
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Trying to troubleshoot pyro sim crash H22 Oct. 21, 2026, 3:39 p.m.
Umang_Raj
can you send the crash report?
I just crashed with the same viewport glitch/segmentation fault error, but here I was using VDB From Polygons not pyro - 10x10x10 box -> Bound -> VDB From Polygons @ 0.01 voxel size = crash (log attached)
Image Not Found
Trying to troubleshoot pyro sim crash H22 Oct. 19, 2026, 2:44 p.m.
It seems I constantly crash when simulating high res pyro and I'm trying to understand why.
rtx 5090, 32 thread ryzen 9 7950x and 128gb ram
In this most recent example I only had my voxel size at 0.02 and still crash after what looks like cache size exceeding 1gb - I post process the vdb's and 1) I had the cache set to 64 frames and H22 crashed at frame 50 2) when I try to load frame 50 from the cache, H22 still crashes
When the crash occurs my viewport seems to break and all I get is "segmentation fault"
Attached is what my viewport looks like and a screen grab of cached file sizes
I was wondering if anyone had any insight into either why this might be happening or knows of any information about correlation between voxel grids and memory/etc...
Also, when I crash, task manager reports that my GPU usage is minimal, ram usuage is at about 50/60%, and cpu usage is the only thing that maxed out
rtx 5090, 32 thread ryzen 9 7950x and 128gb ram
In this most recent example I only had my voxel size at 0.02 and still crash after what looks like cache size exceeding 1gb - I post process the vdb's and 1) I had the cache set to 64 frames and H22 crashed at frame 50 2) when I try to load frame 50 from the cache, H22 still crashes
When the crash occurs my viewport seems to break and all I get is "segmentation fault"
Attached is what my viewport looks like and a screen grab of cached file sizes
I was wondering if anyone had any insight into either why this might be happening or knows of any information about correlation between voxel grids and memory/etc...
Also, when I crash, task manager reports that my GPU usage is minimal, ram usuage is at about 50/60%, and cpu usage is the only thing that maxed out
How do I drive a Switch SOP input from a Wedge TOP attribute Aug. 8, 2026, 11:28 a.m.
I'm doing something similar, I have an HDA to expedite wedge params like folder paths, files names etc - on my HDA I have a "Preview Wedge" slider that will swap wedges, here you might just use the HDA param to control the wedge and the switch -
python script module in HDA:
Callback script on int parameter:
python script module in HDA:
def select_wedge(node, index): # ← CHANGE THIS path to your actual Wedge TOP top = node.node("topnet1/wedge1") if top is None: return pdg = top.getPDGNode() if pdg is None: return # Prefer matching by wedgeindex attribute for wi in pdg.workItems: if wi.intAttribValue("wedgeindex") == index: top.setSelectedWorkItem(wi.id) return # Fallback if 0 <= index < len(pdg.workItems): top.setSelectedWorkItem(pdg.workItems[index].id)
Callback script on int parameter:
kwargs["node"].hdaModule().select_wedge(kwargs["node"], kwargs["parm"].eval())