feat: CUDA/OptiX implementation of TextureSystem
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- cpp
调研方向
这个 issue 更像是规划和设计讨论，而不是范围明确的代码任务，并且没有列出任何文件或测试。首先审查现有的 CPU-based OIIO TextureSystem 以及已提出的 CUDA/OptiX 设计目标。只有在就涵盖交付、API 兼容性、共享计算和按需加载纹理的 MVP 范围与实现计划达成一致后，才算完成。
由索引模型根据 Issue 内容生成。
描述
Most production renderers that use OSL for shading also use OIIO's TextureSystem as their texture engine, and also quite a few non-OSL renderers still use OIIO TextureSystem. But as those renderers add GPU abilities with CUDA and OptiX, they are pretty much on their own when it comes to texture (OSL gives them a customization point where the renderer itself provides texture facilities).
We've talked for some time about OIIO providing a CUDA/OptiX implementation of TS, and it's time to finally get it underway. I think we can get to an MVP in main relatively rapidly, and then continue work to make this a major supported feature.
I would consider the basic design goals to be the following:
- Delivered as part of OIIO somehow, and in a form easily consumable by OSL and other renderers.
- With full feature/quality parity with the existing and future development of the CPU-based OIIO TS (this can happen in stages, with an MVP delivering basic functionality and additions over time getting us to full parity and higher quality).
- With as close as possible an API to existing TS.
- Sharing as much computational code as possible between CPU and GPU implementations.
- Using the OptiX toolkit's on-demand texture loading to provide similar functionality to ImageCache (or maybe as part of, or in conjunction with IC?).
Using this issue to plan, discuss design, track progress, and rally participation from interested parties.
- 主要语言
- C++
- 星标
- 2.4k
- 派生
- 718
- 平均合并
- 2 天 18 小时
- 30 天内合并 PR
- 85
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
AcademySoftwareFoundation/OpenImageIO 的其他 Issue
-
bug: get_image_info returns true after copying an uninitialised buffer into the caller's output when every UDIM tile is unreadable可能已有人在做 @lgritz 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
AcademySoftwareFoundation/OpenImageIO#5662 · 1 条评论 · 已指派 1 人 ·
维护者通常 2 天内回复
-
bug: copy() writes destination channels the source does not have, taking the values from past the source's pixel可能已有人在做 @lgritz 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 35/100
AcademySoftwareFoundation/OpenImageIO#5661 · 1 条评论 · 已指派 1 人 ·
维护者通常 2 天内回复
-
bug: a malformed filename throws std::regex_error out of ImageCache, and catching it deadlocks the file cache可能已有人在做 @lgritz 于 2 天前认领。 未关闭
AcademySoftwareFoundation/OpenImageIO#5660 · 已指派 1 人 ·
维护者通常 2 天内回复
-
bug: deep paste wraps into the next scanline instead of clipping, and ignores chbegin可能已有人在做 @lgritz 于 1 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 45/100
AcademySoftwareFoundation/OpenImageIO#5649 · 1 条评论 · 已指派 1 人 ·
维护者通常 2 天内回复
-
bug: make_kernel("binomial", ...) indexes its tap arrays past their allocation for even or fractional extents可能已有人在做 @lgritz 于 4 天前认领。 未关闭
难度 3/5 半天 新手友好度 62/100
AcademySoftwareFoundation/OpenImageIO#5648 ·
维护者通常 2 天内回复
查看 AcademySoftwareFoundation/OpenImageIO 的全部 Issue
相似的 Issue
-
kind/bug priority/medium qa_automation
难度 2/5 1-3 小时 新手友好度 78/100
yugabyte/yugabyte-db#37324 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
CharlotteCross1998/awesome-game-decompilations#61 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
godotengine/godot#125240 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
new issue
难度 2/5 1-3 小时 新手友好度 72/100
llvm/llvm-project#240065 ·
维护者通常 1 天内回复