Multiple RenderMaterial instances per object in renderMaterialProxies

Hi folks,

I’ve observed a Revit model having objects defined in the renderMaterialProxies structure that point to multiple RenderMaterial definitions. That is:

renderMaterialProxy

  • [0]
    • value → RenderMaterial “CLAD_Terracotta Tile_300w*F2F_batten_COLOUR 1”
    • objects → “7e43e0bd-afce-42e3-a12f-973a23ef9f2b”
  • [1]
    • value → RenderMaterial “CLAD_Terracotta Tile_300w*F2F_batten_COLOUR 2”
    • objects → “7e43e0bd-afce-42e3-a12f-973a23ef9f2b”
  • [2]
    • value → RenderMaterial “CLAD_Terracotta Tile_300w*F2F_batten_COLOUR 3”
    • objects → “7e43e0bd-afce-42e3-a12f-973a23ef9f2b”
  • [3]
    • value → RenderMaterial “CLAD_Terracotta Tile_300w*F2F_batten_COLOUR 4”
    • objects → “7e43e0bd-afce-42e3-a12f-973a23ef9f2b”

Do you know why this occurs and whether it is by design? If it is, then what is the correct way to assign material to the mesh object defined in ‘7e43e0bd-afce-42e3-a12f-973a23ef9f2b’ here?

Tim.

Hi @tlewis,

At first glance, it does not look right. For better understanding, is this generated with the latest connector? Is it possible to share the model URL so we can have a look?

1 Like