Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Radiance to Ignis converter #25

Open
24 tasks
PearCoding opened this issue May 27, 2022 · 1 comment
Open
24 tasks

Improve Radiance to Ignis converter #25

PearCoding opened this issue May 27, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@PearCoding
Copy link
Owner

The current converter is able to map geometry from Radiance to standard formats used by Ignis (and other renderer).
It would be great if we could support the following as well:

  • Maybe directly integrate the mapper into the backend (like glTF)?
  • Basic materials without modifiers (e.g., plastic, dielectric, glass, ...)
    • Plastic
    • Mirror
    • Glass. Keep in mind that 'glass' is not the same material as in Ignis! Especially the (thin) fresnel term is missing.
    • Dielectric
    • Trans
    • Interface
    • BSDF (Klems, TensorTree)
    • ABSDF (TensorTree only, as Klems is already too imprecise to work well with Peak Extraction, imho)
  • Basic lights without modifiers
    • Light (aka area lights)
    • Spotlight
    • Illum. This is a camera hidden light source. Requires the light interface to support ray depth.
    • Glow. We will handle this the same as Light. So no maximum radius, etc...
  • Large subset of modifiers. Most of the modifiers in Radiance can be mapped to Ignis via procedural patterns and PExpr.
    • Function files (.cal) can be mapped to PExpr or directly to Artic.
    • Brightfunc. Same as a number parameter with an expression.
    • Colorfunc. Same as a color parameter with an expression.
    • Brightdata. Scalar image data. (Most likely a custom format we have to add)
    • Colordata. Color image data. (Most likely a custom format we have to add)
    • Colorpict. A standard texture
    • Texfunc. Procedural texture
    • Texdata. A standard texture?
    • No support for text patterns and antimatters

Keep in mind that the above mentioned features have low priority in the project and working on them will not start anytime soon.
This issue is primarily a roadmap for future developer improving the converter.

@PearCoding PearCoding added the enhancement New feature or request label May 27, 2022
@PearCoding
Copy link
Owner Author

See issue #46 as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant