Skip to content

Hydra Houdini: VdbVolume Shader #261

Description

@aoblet

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

  1. Is HDA generation from shader JSON automated or hand-maintained?
  2. If automated, is the generator just not open-sourced?
  3. Known gap, or oversight?
  4. Preferred way to add a missing shader's node?

Can PR a moonray_nodes.json entry / .ds for VdbVolume once process is confirmed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions