Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add example-tinyrender: a minimal standalone renderer test against the installed OSL

Abierto
  • ¿Algo no está bien?
#2,175 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp
Área
computer-graphics, testing-qa

Línea de trabajo

Start by reviewing the existing testsuite/example-* tests and the OSL-enabled RTIOW version in the linked Path-Tracer project. Trace the planned flow from compiling .osl shaders with the installed oslc through registering and sampling closures; done means a minimal standalone renderer produces a small image matching a reference image without the unnecessary TBB or BVH dependencies.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

A follow-up from the discussion in https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/discussions/2163. (Creating this issue to better track the task and to ask questions as they come up.)

OSL has testrender and testshade to test its implementation, but they are built as part of OSL itself. So passing tests don't guarantee that the installed OSL works for downstream consumers. The testsuite/example-* tests fill part of that gap: they build against the installed OSL and test what they need to. What's still missing is a standalone renderer doing the same, i.e., registering closures, running shaders at ray hits, and sampling the closures they return.

The new RTIOW-based test, which I will call example-tinyrender, will follow the same idea: use the installed version of OSL and act as a minimal standalone renderer. (The alternative name was example-rtiow, but "rtiow", I find, is a bit too cryptic for most readers, whereas with "tinyrender" you don't have to second-guess what it means. And I can just mention in a comment that it's based on the path tracer from RTIOW.)

I already have an OSL-enabled RTIOW version in https://github.com/jinhgkim/Path-Tracer. However, it still needs to be stripped down, since it depends on TBB, includes a BVH, etc. My goal is to provide an end-to-end regression test, from compiling .osl shaders (using the installed oslc) to sampling closures, while keeping it minimal. It will render a small image and compare it against a reference image. That's the high-level plan, and I'll hash out the details as I go.

Lenguaje dominante
C++
Estrellas
2.3k
Forks
415
Merge medio
2 d 10 h
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AcademySoftwareFoundation/OpenShadingLanguage

Todos los issues de AcademySoftwareFoundation/OpenShadingLanguage

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.