Hydra Houdini: VdbVolume Shader
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 43/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cmake
- Domain
- tooling
Research direction
Start with houdini/moonray_nodes.json, shader_json/VdbVolume.json, moonray/dso/volume/Vdb/attributes.cc, and houdini/CMakeLists.txt to trace how existing shader nodes are represented and installed. The issue leaves the HDA generation process and preferred contribution path unresolved, so confirm those before choosing an implementation. Done means the project’s process is established and, if appropriate, VdbVolume is exposed as a Houdini node.
Written by the indexing model from the issue text.
Description
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: 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
- 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.
- Dominant language
- CMake
- Stars
- 4.7k
- Forks
- 321
- Avg merge
- 13m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenMoonRay/openmoonray
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OpenMoonRay/openmoonray#332 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OpenMoonRay/openmoonray#320 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OpenMoonRay/openmoonray#233 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
OpenMoonRay/openmoonray#331 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
OpenMoonRay/openmoonray#330 ·
All issues in OpenMoonRay/openmoonray
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
MarketSquare/robotframework-browser#5479 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
rookslog/zlibrary-mcp#408 ·
Maintainers usually reply within 1 day
-
good first issue priority:low type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
crazy-goat/fdb-php#182 ·
Maintainers usually reply within 1 day
-
area: documentation good first issue package: rule-data status: accepting prs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100