OVRTX MaterialX/OpenPBR
Prepare Blender materials for the add-on's OVRTX MaterialX/OpenPBR conversion
and diagnose failures through documented add-on and runtime interfaces.
When to Use
Use for source textures, OpenPBR graphs, black/red/flat OVRTX materials, missing bindings, UV/normal-map issues, or Blender-versus-OVRTX material comparisons.
Boundary and inputs
- Work through the installed add-on, Blender APIs, documented probes, and the
supported runtime interfaces.
- Preserve source textures and relative paths. Do not bake a comparison image
and call it a material conversion.
- Record Blender, add-on, runtime, material, texture, UV, and color-space
identities before changing the graph.
Instructions
- Inventory only materials assigned to renderable polygons and verify evaluated
geometry, slots, polygon assignment, UV layer, and texture paths.
- Build or repair a reachable graph from the active material output. Prefer
named Principled/OpenPBR-adjacent inputs and source image textures over
disconnected diagnostic nodes.
- Validate base color, roughness, metallic/specular, normal, transmission,
opacity, emission, coat, sheen, and texture color-space intent separately.
- Confirm the add-on's generated MaterialX/OpenPBR binding and geomprop/UV name
in the resolved output. Treat USD Preview fallback as a separate lane.
- Render a neutral control and one material-specific fixture through Blender and
OVRTX. Compare scene-linear/HDR data when available; use display PNGs only as
a separately labeled presentation comparison.
- Classify each used material as
faithful, approximate, unbound, or
runtime-unavailable, with the cause and next action.
Failure ladder
Diagnose in this order: runtime/readback, stage/material identity and binding,
UV/texture path and color space, global lighting/exposure/display transform,
then individual lobe conversion. Do not change albedo to hide a light or
tone-map problem. Do not reject a scene because an unreachable unsupported node
exists.
Handoff
Summarize the material changed, conversion class, native result, and any
unsupported node or texture. Add hashes, mapping tables, fixture renders, or
raw/display comparisons only when the caller needs a reproducible handoff or
review artifact. Pair with ovrtx-render-settings for probed scene
controls and a contributor parity skill for graph-family regression tests.
1---2name: ovrtx-materialx-openpbr3description: Prepare Blender materials for the add-on's OVRTX MaterialX/OpenPBR conversion and diagnose failures without renderer source access. Use for source textures, OpenPBR graphs, black/red/flat OVRTX materials, missing bindings, UV/normal-map issues, or Blender-versus-OVRTX material comparisons.4license: Apache-2.05---6# OVRTX MaterialX/OpenPBR78Prepare Blender materials for the add-on's OVRTX MaterialX/OpenPBR conversion9and diagnose failures through documented add-on and runtime interfaces.1011## When to Use1213Use for source textures, OpenPBR graphs, black/red/flat OVRTX materials, missing bindings, UV/normal-map issues, or Blender-versus-OVRTX material comparisons.1415## Boundary and inputs1617- Work through the installed add-on, Blender APIs, documented probes, and the18 supported runtime interfaces.19- Preserve source textures and relative paths. Do not bake a comparison image20 and call it a material conversion.21- Record Blender, add-on, runtime, material, texture, UV, and color-space22 identities before changing the graph.2324## Instructions25261. Inventory only materials assigned to renderable polygons and verify evaluated27 geometry, slots, polygon assignment, UV layer, and texture paths.282. Build or repair a reachable graph from the active material output. Prefer29 named Principled/OpenPBR-adjacent inputs and source image textures over30 disconnected diagnostic nodes.313. Validate base color, roughness, metallic/specular, normal, transmission,32 opacity, emission, coat, sheen, and texture color-space intent separately.334. Confirm the add-on's generated MaterialX/OpenPBR binding and geomprop/UV name34 in the resolved output. Treat USD Preview fallback as a separate lane.355. Render a neutral control and one material-specific fixture through Blender and36 OVRTX. Compare scene-linear/HDR data when available; use display PNGs only as37 a separately labeled presentation comparison.386. Classify each used material as `faithful`, `approximate`, `unbound`, or39 `runtime-unavailable`, with the cause and next action.4041## Failure ladder4243Diagnose in this order: runtime/readback, stage/material identity and binding,44UV/texture path and color space, global lighting/exposure/display transform,45then individual lobe conversion. Do not change albedo to hide a light or46tone-map problem. Do not reject a scene because an unreachable unsupported node47exists.4849## Handoff5051Summarize the material changed, conversion class, native result, and any52unsupported node or texture. Add hashes, mapping tables, fixture renders, or53raw/display comparisons only when the caller needs a reproducible handoff or54review artifact. Pair with `ovrtx-render-settings` for probed scene55controls and a contributor parity skill for graph-family regression tests.
NVIDIA-Omniverse