AcademySoftwareFoundation / AcademySoftwareFoundation/MaterialX

[Khronos] MaterialX Specification for glTF texture procedurals

Open
#1,906 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
2.3k
Forks
464
Avg merge
4d 21h
Merged PRs (30d)
11

Description

I'm relaying a request on behalf of members on Khronos glTF PBR Procedural Texture group committee.
The proposed extensions:

  1. KHR_texture_procedurals
  2. EXT_texture_procedurals_mx_1_39

will allow defining procedural patterns graphs in glTF using MaterialX 1.39 standard library nodes.

We are seeking clarification on MaterialX Specification, specifically around expected behavior of nodes when invalid values are supplied. Will the MaterialX specification define the behavior or will the behavior be defined by the underlying language implementation (glsl, msl, osl etc). This is especially relevant for math, and operator nodes in MaterialX standard library.
For example, consider sqrt node, what is the expected behaviour if input is negative?

In order for Khronos glTF PBR Procedural Texture group committee to proceed with using MaterialX 1.39 as a standard, it would be helpful if this behavior is clarified either at the node level or as a general guideline in the specification for each category of nodes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the linked KHR_texture_procedurals and EXT_texture_procedurals_mx_1_39 extension paths, then inspect the MaterialX 1.39 standard library nodes, especially sqrt and other math/operator nodes. Compare the specification with the listed GLSL, MSL, and OSL implementation contexts. Done means documenting an agreed rule for invalid values at the node or category level.

Written by the indexing model from the issue text.

Assessment

Domain
computer-graphics, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.