# Part

class `cee.geo.``Part`()

  A Part is a collection of primitives (triangles, lines, points) and a specification of how to render these primitives.

  The primitives are defined as a Mesh.

  The PartSettings class defines how a part will be rendered (color, opacity, visibility) and if the part should be intersectable or not.

  The GeometryModel is designed to handle a large number of parts (at least 300k+ without issues).

Accessors

- `customData`
- `mesh`
- `partIndex`
- `settings`
- `transformationMatrix`

## Accessors

`Part.``customData`()

  Custom data for the part. This field is not used by EnvisionWeb.

  Return type: | any

`Part.``customData`(data)

  Arguments: | data (`any`) – None
  Return type: | void

`Part.``mesh`()

  The mesh defining the geometry of the part. If no mesh is defined, null is returned.

  Return type: | Mesh

`Part.``mesh`(mesh)

  Arguments: | mesh (`Mesh`) – None
  Return type: | void

`Part.``partIndex`()

  The index of the part in the parent geometry model

  Return type: | number

`Part.``settings`()

  Returns an active reference to the settings for this part.

  Return type: | PartSettings

`Part.``transformationMatrix`()

  The transformation matrix to use for this part.

  The default is null.

  Return type: | Mat4

`Part.``transformationMatrix`(transformationMatrix)

  Arguments: | transformationMatrix (`Mat4`) – None
  Return type: | void

Conversation saved
HOOPSY BETA

### Hello! I'm HOOPSY

Your Docs generative AI assistant. Ask me anything about HOOPS Envision for Web or choose a sample question below to start a conversation:

What is HOOPS Envision for Web?
What are the latest release notes for HOOPS Envision for Web?
How do I start evaluating HOOPS Envision for Web?
How do I write my first sample application?
How can I get assistance?

HOOPSY may store conversations according to OpenAI's policy. Responses may not always be accurate.

HOOPSY is thinking...