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

About generated textures #5

Closed
LIU-Yuxin opened this issue Apr 5, 2024 · 2 comments
Closed

About generated textures #5

LIU-Yuxin opened this issue Apr 5, 2024 · 2 comments

Comments

@LIU-Yuxin
Copy link

Hi, could you please explain how the rgb channels in Ks texture should be interpreted? If I understand the paper correctly, there are roughness and metallic in that texture, but I am not sure which channels stores which property. In addition, are there any processing needed, before these textures can be used as albedo, roughness and metallic input for shaders in common softwares like Blender or Unity?

@Youwang-Kim
Copy link
Contributor

Youwang-Kim commented Apr 5, 2024

Hi, thanks for the interest and question.

Regarding RGB channels in Ks texture, we use G channel as "roughness" and B channel as "metalness", and we omit R channel. We borrowed the design choice of NVDiffrec, and you can find the details below:
https://github.com/postech-ami/paint-it/blob/407c55b4255dd8e13fd950313ea860cf0ffe71e2/nvdiff_render/light.py#L88-L92

Furthermore, if you want to load the Ks texture in Blender, you can simply load Ks texture and use the "ShaderNodeSeparateRGB" node to separate the material properties. It would be much easier if you use python scripting at Blender. You can find a useful python script here:
https://github.com/NVlabs/nvdiffrecmc?tab=readme-ov-file#use-the-extracted-3d-models-in-blender

Please let me know if you have additional questions :)

Thanks.

@LIU-Yuxin
Copy link
Author

Thank you for your detailed answer!

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

No branches or pull requests

2 participants