Title
VdbVolume shader has no Houdini node, how are otls/*.hda generated?
Summary
BaseVolume is exposed as a VOP.
But VdbVolume isn't, despite being a distinct, documented shader for VDB-backed geometry (VdbGeometry), not an alias for BaseVolume.
Findings
houdini/moonray_nodes.json: has BaseVolume, VdbGeometry, VdbLightFilter... no VdbVolume.
moonray/dso/volume/Vdb/attributes.cc: real, distinct attrs (opacity_gain_mult, color_mult, incandescence_gain_mult, anisotropy).
shader_json/VdbVolume.json: already has this data.
houdini/CMakeLists.txt: only installs pre-built otls/soho — no JSON→HDA generator in-repo.
Questions
- Is HDA generation from shader JSON automated or hand-maintained?
- If automated, is the generator just not open-sourced?
- Known gap, or oversight?
- Preferred way to add a missing shader's node?
Can PR a moonray_nodes.json entry / .ds for VdbVolume once process is confirmed.
Title
VdbVolume shader has no Houdini node, how are otls/*.hda generated?
Summary
BaseVolumeis exposed as a VOP.But
VdbVolumeisn't, despite being a distinct, documented shader for VDB-backed geometry (VdbGeometry), not an alias forBaseVolume.Findings
houdini/moonray_nodes.json: hasBaseVolume,VdbGeometry,VdbLightFilter... noVdbVolume.moonray/dso/volume/Vdb/attributes.cc: real, distinct attrs (opacity_gain_mult,color_mult,incandescence_gain_mult,anisotropy).shader_json/VdbVolume.json: already has this data.houdini/CMakeLists.txt: only installs pre-builtotls/soho— no JSON→HDA generator in-repo.Questions
Can PR a
moonray_nodes.jsonentry /.dsforVdbVolumeonce process is confirmed.