cgmath — a DCC-agnostic CG math library

A Python toolkit for what tech artists, and pipeline engineers actually need:

• common CG dataclasses you can define, introspect, query, and manipulate.
• solid bilinear data resampling methods for topology, skin weights, etc.
• various deformer detaclasses (RBF Wrap kernels, LBS, DQS, etc)
• skeletal hierarchy manipulation
• import support for OBJ / GLB / FBX / USD
• a software raytracer
• and more!

Everything is numpy-native, Numba-accelerated where it matters.

import numpy as np

from cgmath.geometry import MeshData
from cgmath.render import Object, Scene

cube = MeshData(
    points=np.array([
        [-0.5, -0.5,  0.5], [ 0.5, -0.5,  0.5],
        [-0.5,  0.5,  0.5], [ 0.5,  0.5,  0.5],
        [-0.5,  0.5, -0.5], [ 0.5,  0.5, -0.5],
        [-0.5, -0.5, -0.5], [ 0.5, -0.5, -0.5],
    ]),
    indices=np.array([0, 1, 3, 2,  2, 3, 5, 4,  4, 5, 7, 6,
                      6, 7, 1, 0,  1, 7, 5, 3,  6, 0, 2, 4]),
    counts=np.array([4, 4, 4, 4, 4, 4]),
)

scene = Scene("hero")
scene.append(Object(name="cube", mesh=cube))
frame = scene.render()
print(frame.array.shape)                       # (500, 500, 4) RGBA

That is a full render — the library brought its own camera, its own 3-point lighting rig sized to the bounding box, and its own resolution.

---

Where to go next

Every subpackage has a README (concepts, conventions, when to reach for it) and a CHEATSHEET (every public name, with a runnable example).

Module	What it holds
this page	conventions, the map, the quick taste	CHEATSHEET — the 24 most common things, cross-cutting
learning by doing	ten walkthroughs that each build something complete	TUTORIAL
cgmath.transforms	matrices, quaternions, euler, axis-angle, vectors — as batched functions	README · CHEATSHEET
cgmath.hierarchy	TransformData / TransformList / HierarchyData / ClipData — the scene graph	README · CHEATSHEET
cgmath.geometry	MeshData, UVs, B-splines, SDFs, skin weights, morphs, maps, resampling	README · CHEATSHEET
cgmath.geometry.deform	FFD, Delta Mush, patch relax, skinning, RBF wrap	README · CHEATSHEET
cgmath.geometry.utils	the 59 numba kernels everything above stands on	README · CHEATSHEET
cgmath.render	software raytracer, Scene / Object / Camera / Light / Frame	README · CHEATSHEET
cgmath.formats	FBX + GLB curve / take / accessor I/O, USD stage and prim helpers	README · CHEATSHEET
cgmath.rbf	21 radial basis function kernels + a JIT LU solver	README · CHEATSHEET
cgmath.constraints	ProcrustesData — rivet a transform to a deforming patch	README · CHEATSHEET

REFERENCE.md, a flat API listing, also sits in this directory. It is generated from the live code by gen_reference.py (kept in the tools/ folder beside the packages, not in this repository): every public name with its real signature and first docstring line.

---

What's inside

cgmath/__init__.py is a docstring and re-exports nothing, so import cgmath gives you nothing to call. Import from a subpackage.

cgmath/
├── utils.py               info() / docstring(), pretty_json, profile(), run_tests()
│
├── hierarchy/             TransformData, TransformList, HierarchyData, ClipData
│   ├── __init__.py        re-exports the public surface
│   └── hierarchy.py       the four types, the fbx / glb readers, the batched clip evaluator
│
├── geometry/              meshes, UVs, curves, fields, transfer
│   ├── _base.py           Data / DataList / ImmutableArray + serialization
│   ├── mesh.py            MeshData, MeshList, UVData, UVList, the loaders
│   ├── map.py morph_target.py skin_weights.py    MapData, MorphData, SkinData
│   ├── bspline.py bspline_patch.py _saddle_surface.py _cdt.py
│   ├── sdf.py             SDF primitives + dual marching cubes
│   ├── pack.py resample.py surface_plotting.py
│   ├── robust_skinweights_transfer_bilinear.py
│   ├── camera.py delta_mush.py ffd.py patch_relax.py raytracer.py texture.py
│   │                      one-release deprecation shims -- they warn and re-export
│   ├── deform/            FFDData, DeltaMushData, PatchRelaxData,
│   │                      SkinDeformData, WrapData
│   └── utils/             main.py + _numba/ -- the kernel floor
│
├── transforms/            main.py + _numba/ -- batched matrix, quaternion, euler, axis, vector math
├── render/                scene.py raytracer.py camera.py frame.py texture.py
├── formats/               fbx.py, glb.py, usd/prim.py, usd/stage.py
├── rbf/                   _kernels.py + _numba/   (__init__.py is a docstring, on purpose)
└── constraints/           procrustes.py

The batched matrix / quaternion / euler / axis / vector functions that all of this stands on live in cgmath.transforms; its own README and CHEATSHEET cover them. The same code is published on its own as transforms for anyone who wants the math without the rest of cgmath.

The public surface of each subpackage is what its __init__.py re-exports:

from cgmath.hierarchy import TransformData, TransformList, HierarchyData, ClipData
from cgmath.geometry   import MeshData, MeshList, UVData, UVList
from cgmath.geometry   import BSplineData, BSplinePatchData, PatchSampleData
from cgmath.geometry   import MorphData, MorphList, MapData, GeomSubsetData
from cgmath.geometry   import SkinData, SkinList, CompactSkinData
from cgmath.geometry   import DeltaMushData, PatchRelaxData
from cgmath.geometry.deform import FFDData, SkinDeformData, WrapData, DeformMethod
from cgmath.render     import render, Scene, Object, Camera, Light, Frame, look_at
from cgmath.constraints import ProcrustesData

Note the asymmetry: cgmath.geometry re-exports only two of the five deformers. FFDData, SkinDeformData and WrapData come from cgmath.geometry.deform.

---

Conventions, all in one place

cgmath depends on no DCC, but its conventions are modelled on Maya's: row-major matrices, Maya's rotate orders and its SRT parenting rules. If you know Maya, nothing below will surprise you.

• Transforms are Maya row-major. Translation lives at M[3, :3], points are row vectors (p' = p @ M), and matrix_multiply(A, B) applies A first. Maya rotate orders: XYZ=0 YZX=1 ZXY=2 XZY=3 YXZ=4 ZYX=5. Axis constants X=0 Y=1 Z=2.
• Quaternions are (i, j, k, w) — scalar last. They compose in the opposite order from matrices: quaternion_multiply(a, b) matches matrix_multiply(B, A).
• Radians in functions, degrees on nodes. Everything in transforms.* takes radians; TransformData.rotate and the angle thresholds on MeshData are degrees.
• Everything is batched, with NumPy's rules. A bare (3,) or (4, 4) is promoted to a stack of one, and every input must be as long as the longest one or exactly one, in which case it is reused for the whole batch. Mismatched lengths raise ValueError.
• -1 is the pad. Every adjacency matrix is dense (rows, max_width) with short rows padded; -1 also marks a missing face and a raycast miss.
• A mesh is a face-vertex stream, indices + counts + points. Mixed triangles, quads and n-gons in one mesh are normal.
• Camera is OpenGL: -Z forward, +Y up, +X right. look_at() and Frame.camera_matrix are column-major (eye at M[:3, 3]) while node matrices are row-major (eye at M[3, :3]).
• Images are RGBA uint8 with pixel (0, 0) top-left. Colour tuples in the scene graph are [0, 1] floats; wireframe colours are 0..255 ints.
• UV v increases up — v = 0 is the bottom of the texture (Maya / OpenGL).
• Verbs mutate, get_* and from_* return. triangulate, subdivide, merge, smooth, pack edit in place and drop the caches; copy, from_faces, sample, every resample_* hand back something new.

The first three are cgmath.transforms conventions that the rest of cgmath follows — full detail in its README.

Optional dependencies

Imported lazily behind try / except ImportError, so the package loads without them and only the paths that need them complain.

Dependency	Used for	Missing behaviour
pygltflib	GLB / glTF read	RuntimeError("pygltflib is not installed") at call time
Autodesk FBX SDK — not on PyPI, a manual install	FBX read / write	imports fine, with one UserWarning naming the SDK and where to get it; every FBX call raises RuntimeError with that same message
pxr, from usd-core — installed with the wheel	cgmath.formats.usd stage / prim helpers; from_prim / to_prim / load_usd in geometry	always present after pip install. Run off sys.path without it, import cgmath.formats.usd.prim itself raises ImportError and the geometry paths raise ImportError at call time (geometry.utils.pxr() is the accessor)
trimesh	GlbData.mesh_list	that attribute is None
PIL (Pillow)	Frame.image / .save / .wireframe / .encode_gif, to_image, texture I/O	RuntimeError("... install Pillow.") at call time
cv2	imshow() windows; UV rasterization in geometry.mesh	imshow raises RuntimeError; rasterization falls back to skimage
skimage	the cv2 fallback for UV rasterization and image loading	RuntimeError only when neither it nor cv2 is present
ffmpeg / gifski on PATH	encode_mp4 / encode_gif	encode_gif falls back to ffmpeg when gifski is absent; no ffmpeg is an error

numba compiles on first call and caches to disk next to the sources (__pycache__/*.nbi, *.nbc); set NUMBA_CACHE_DIR to move the cache. Importing any subpackage is cheap; the first sample(), subdivide() or render() in a fresh interpreter pays the JIT.

---

Quick taste

Each block below builds on the cube from the top of this page.

Read mesh topology

print(cube.point_count, cube.face_count, cube.edge_count)  # 8 6 12
print(cube.closed, cube.quads, round(cube.area, 4))        # True 6 6.0
print(cube.get_border_vertices(flatten=True))              # [] -- closed
print(cube.e2v.shape, cube.ue2v.shape)                     # (12, 2) deduped vs (24, 2) raw

Every adjacency matrix (f2v, v2f, e2v, e2f, ...) is built lazily, cached, and -1 padded.

Texture a mesh through its UVs and render it

A UVData is a mesh in UV space: the same face stream, with (V, 2) points. Here every face maps to the whole texture square.

from cgmath.geometry import UVData
from cgmath.render import Object, Scene

cube_uv = UVData(
    points  = np.array([[0.0, 0.0], [1.0, 0.0], [1.0, 1.0], [0.0, 1.0]]),
    indices = np.tile([0, 1, 2, 3], 6),
    counts  = cube.counts,
)

i, j    = np.indices((64, 64)) // 8                        # an 8 x 8 checkerboard
checker = np.where(((i + j) % 2)[..., None] == 1, 230, 40).astype(np.uint8).repeat(3, axis=2)

scene   = Scene("hero")
scene.append(Object(name="cube", mesh=cube, uv=cube_uv, texture=checker))
scene.configure(resolution=(320, 240), samples_per_pixel=4)
scene.render().save("hero.png")

texture takes a file path or an (H, W, 3) array. Without a uv, an Object renders in its flat base_color.

Carry a sculpt from a dense mesh back to a coarse one

MeshDataResampler(src, dst) projects every destination vertex onto the source surface once, then pushes any source-shaped data through that correspondence: points, skin weights, morph targets, painted maps.

from cgmath.geometry import SkinData
from cgmath.geometry.resample import MeshDataResampler

def sphere(level):
    """Subdivide the cube, then push every point onto the unit sphere."""
    mesh = cube.copy()
    mesh.subdivide(level)
    mesh.points = mesh.points / np.linalg.norm(mesh.points, axis=1, keepdims=True)
    return mesh

coarse, dense = sphere(1), sphere(3)                       # 26 and 386 points, same shape

sculpt        = dense.copy()                               # a bump at the north pole
bump          = np.exp(-8.0 * np.sum((dense.points - [0.0, 1.0, 0.0]) ** 2, axis=1))
sculpt.points = dense.points * (1.0 + 0.3 * bump)[:, None]

resampler = MeshDataResampler(dense, coarse)
back      = resampler.resample_mesh(sculpt)                # coarse topology, sculpted shape
print(back.point_count, np.abs(back.points - coarse.points).max().round(3))   # 26 0.3

y    = (dense.points[:, 1] + 1.0) / 2.0                    # weights authored on the dense mesh
skin = SkinData(weights=np.column_stack([1.0 - y, y]), influences=["root", "tip"])
print(resampler.resample_skin_weights(skin).weights.shape)                    # (26, 2)

The default mode is SPATIAL (closest point on the source surface). UV matches through a shared UV layout, and ROBUST_BILINEAR rejects bad matches and inpaints them — see geometry/README.md.

Sweep an FFD lattice

from cgmath.geometry.deform import FFDData

lattice = FFDData.create_lattice(
    (3, 3, 3),
    bbox_min = cube.points.min(axis=0) - 0.05,
    bbox_max = cube.points.max(axis=0) + 0.05,
)
ffd = FFDData.from_mesh(lattice, divisions=(3, 3, 3))   # the LATTICE, not the mesh
ffd.bind(cube)

posed = ffd.lattice.copy()
posed[:, -1, :, 0] += 0.5                                  # push the top control plane in +X
print(np.abs(ffd.update(posed).points - cube.points).max().round(4))

FFD is one of five deformers; Delta Mush, patch relax, skinning and RBF wrap sit next to it in geometry/deform.

---

Audience

Tech artists, riggers and tools engineers who want the geometry, rigging and rendering maths of a DCC as plain Python — in CI, a notebook or a headless job — with results that line up when the data goes back into the DCC.

Start with CHEATSHEET.md.

Requirements

Numpy, Scipy and Numba python modules.

Optional, per feature (see the table above for how each degrades):

Pillow                  texture I/O and rendered frames
pygltflib, trimesh      glTF / GLB read and write
Autodesk FBX SDK        FBX read and write
pxr (USD)               USD stage read and write
scikit-image or OpenCV  UV rasterization

Author

• Eric Vignola (eric.vignola@gmail.com)

If this was useful to you, buy me a coffee ☕

License

BSD 3-Clause License: Copyright (c) 2026, Eric Vignola All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. Neither the name of copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.