KhronosGroup / KhronosGroup/ANARI-Docs
Lights should have an ID
Open
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Similar to surfaces and volumes, (at least area) lights should have an ID to populate the `objectId` frame channel from. That would allow apps to select area lights, just as some apps support that for surfaces and volume object types.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing documentation for surfaces, volumes, area lights, and the objectId frame channel. Compare how IDs are documented for surfaces and volumes; the work is done when area lights, at minimum, have an ID that can populate objectId and support application-side selection.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics, documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100