OptiX (CPU) tracking issue
Open
Nobody has claimed this yet.
C-OptiX (Host)
T-tracking-issue
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
Issue to track what needs to be done to complete the CPU (host) side of OptiX:
(me) Denoising:
- optixDenoiserComputeIntensity
- optixDenoiserComputeAverageColor
-
setup_state_with_buffers - Some way of running the denoiser with the same input and output image.
- AOV models
- Tiled denoising
(@anderslanglands) Actual Raytracing:
- port remaining iw examples
- port SDK examples necessary to test remaining features (e.g. motion blur, curves)
- implement instance transforms, motion blur
Contributor 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.
Research direction
This tracking issue names no files, tests, or entry points. Start by locating the OptiX CPU/host implementation and separating the denoising tasks from the raytracing and SDK-example tasks; completion requires addressing the relevant checklist items, including instance transforms, motion blur, and remaining denoiser features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100