XCAFDoc_VisMaterialPBR is missing properties in OCP 8.0.1

Open
#228 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, python
Domain
tooling

Research direction

Start at the OCP binding entry point for XCAFDoc_VisMaterialPBR and compare its exposed members with the official OCCT XCAFDoc_VisMaterialPBR reference. Verify the six listed properties are available on a Python instance and confirm the completed binding through the existing project checks, if present.

Written by the indexing model from the issue text.

Description

I have built materials support for build123d with PBR support. In order to convert it to OCCT, I need XCAFDoc_VisMaterialPBR.
Unfortunately, the OCP 8 bindings for XCAFDoc_VisMaterialPBR are not complete. Missing properties:

  • BaseColorTexture
  • MetallicRoughnessTexture
  • EmissiveTexture
  • OcclusionTexture
  • NormalTexture
  • EmissiveFactor

Official Anaconda OCP 8.0.1 package:

❯ ipython
Python 3.13.15 | packaged by conda-forge | (main, Sep  2 2026, 21:53:23) [Clang 21.1.8 ]
Type 'copyright', 'credits' or 'license' for more information
IPython 9.17.1 -- An enhanced Interactive Python. Type '?' for help.
Tip: Put a ';' at the end of a line to suppress the printing of output.

In [1]: import OCP

In [2]: OCP.__version__
Out[2]: '8.0.1.0'

In [3]: from OCP.XCAFDoc import XCAFDoc_VisMaterialPBR

In [4]: pbr = XCAFDoc_VisMaterialPBR()

In [5]: dir(pbr)
Out[5]:
['BaseColor',
 'DumpJson',
 'IsDefined',
 'IsEqual',
 'Metallic',
 'RefractionIndex',
 'Roughness',
 '__class__',
 '__delattr__',
 '__dir__',
 '__doc__',
 '__eq__',
...

see https://occt3d.com/dev/doc/refman/html/struct_x_c_a_f_doc___vis_material_p_b_r.html

Dominant language
C++
Stars
200
Forks
48
Avg merge
1d 13h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

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.

More from CadQuery/OCP

All issues in CadQuery/OCP

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.