Jon Parker
jparker
About Me
EXPERTISE
Technical Director
Houdini Skills
ADVANCED
Procedural Modeling | Digital Assets | Mantra | Lighting | PDG | VEX | Python
Availability
Not Specified
Recent Forum Posts
Path mapping in Solaris, not working as expected June 16, 2025, 8:15 p.m.
Yeah, USD paths live outside of the standard Houdini file path management.
Also to put this out there, although I'm sure we're a tiny minority by now...
In addition to path mapping working differently, if you have any old school custom `$HH/GEOio.json` file types that you're used to loading any place .bgeos work, they won't load in the USD input nodes (reference / sublayer). You can get it to work by adding your file extensions to `$HH/dso/usd_plugins/usdHGeo/resources/plugInfo.json`, but it's not pipeline-friendly.
Also to put this out there, although I'm sure we're a tiny minority by now...
In addition to path mapping working differently, if you have any old school custom `$HH/GEOio.json` file types that you're used to loading any place .bgeos work, they won't load in the USD input nodes (reference / sublayer). You can get it to work by adding your file extensions to `$HH/dso/usd_plugins/usdHGeo/resources/plugInfo.json`, but it's not pipeline-friendly.
USD Modify Textures Path May 9, 2025, 10:39 p.m.
In a LOP network you can use an Attribute Wrangle node to replace strings in your texture paths.
Assuming you are using MaterialX image prims as your texture inputs, on the wrangle you can set your "Primitives" parm to:
and the VEX code like this:
Assuming you are using MaterialX image prims as your texture inputs, on the wrangle you can set your "Primitives" parm to:
%descendants(%type(Material), strict=false)
and the VEX code like this:
if (usd_isattrib(0, s@primpath, "inputs:file")) { string path = usd_attrib(0, s@primpath, "inputs:file"); path = replace(path, "D:/work/projectFile/HoudiniProject/Tex", "G:/work/HoudiniProject/Tex"); s@inputs:file = path; }
point cloud .pc vs .bgeo Feb. 15, 2025, 1:13 p.m.
In performance terms, for lookup with VEX (pcopen, etc.), is there any practical difference these days between storing points as .pc files or .bgeo?
For .bgeo, does ordered vs. unordered matter?
For .bgeo, does ordered vs. unordered matter?