Umang Raj

Umang_Raj

About Me

EXPERTISE
Hobbyist

Connect

LOCATION
Khagaria, India

Houdini Skills

Availability

Not Specified

My Tutorials

obj-image Beginner
3D Spatial Audio in CHOPs
obj-image Beginner
How DOPs Work, the Basics
obj-image Beginner
Realistic Fabric Texture with Houdini Copernicus
obj-image Beginner
Implicit Surfaces, Create Fast Parametric Collision/Proxy Geometries!
obj-image Intermediate
Solving Pyro and RBD/Vellum Together, Sequentially and Simultaneously
obj-image Intermediate
How to create Custom Solvers for APEX

Recent Forum Posts

How to get subcategories for profiling using the HDK Nov. 17, 2026, 9:33 p.m.

  667     /// Start a event.  
  668     /// Subclasses must call this method when starting their own events.
  669     int                      startEvent_(
  670                                 const UT_StringHolder &event,
  671                                 const UT_StringHolder &object,
  672                                 bool auto_nest_events,
  673                                 UT_PerfMonCategory category,
  674                                 UT_PerfMonEventType type,
  675                                 UT_PerfMonObjectType object_type,
  676                                 const UT_StringHolder &object_icon,
  677                                 int *frame_num=NULL,
  678                                 const UT_StringHolder &extra_info = UT_StringHolder::theEmptyString);
Try this, from the UT_Performance class itself, i haven't tried it yet, i have recently switched to linux and have to setup the build environment, but i guess you have to set true to auto_nest_events, and it will start nesting the events based on time of call and scope, you will also find solve category in the perf mon category enum.

HDK : Multi output Oct. 25, 2026, 10:41 p.m.

It is good to have the if block, but if you only have single extra output, then if block isn't necessary, that's why the sop_dualstar dosen't have it, but it will prevent confusions.
I think it isn't bad to use a member variable in this case, since you aren't using verbs.

Trying to troubleshoot pyro sim crash H22 Oct. 21, 2026, 11:27 p.m.

the reason for this crash is the viewport, as you can see in the log, you can try cooking the nodes without viewport and it should work as a workaround, you should submit it as a bug report.
Also you can go to display options, under geometry tab, there are volume options, you should try setting the volume quality to very low and volume filtering (if your volume is fog) to off