What do Houdini, Maya and Epic documents say about carrying hair/groom curves and widths through Alembic and USD?
Partially verified: the curator re-read S18, S19, S22; S20, S21 were not re-read by the curator and rest on the producer's pinned reading. Houdini 22.0 imports Alembic curve sets as open polygons (no separate groom type in that mapping); its SOP Import LOP writes cubic-only BasisCurves for Hydra or NurbsCurves for round-tripping, and offers Set Missing Widths because USD's fallback width is 1.0. Unreal's Alembic groom importer reads ICurves, converts DCC width to groom_width without overwriting an authored groom_width, and falls back to 1 cm when no width exists, so missing widths behave differently in USD (1.0 scene unit) and Unreal grooms (1 cm).
Partially verified: the curator re-read S18, S19, S22; S20, S21 were not re-read by the curator and rest on the producer's pinned reading.
Houdini 22.0 imports Alembic curve sets as open polygons (no separate groom type in that mapping); its SOP Import LOP writes cubic-only BasisCurves for Hydra or NurbsCurves for round-tripping, and offers Set Missing Widths because USD's fallback width is 1.0. Unreal's Alembic groom importer reads ICurves, converts DCC width to groom_width without overwriting an authored groom_width, and falls back to 1 cm when no width exists, so missing widths behave differently in USD (1.0 scene unit) and Unreal grooms (1 cm).
Curator qualifications: Partially verified: the curator re-read S18, S19, S22; S20, S21 were not re-read by the curator and rest on the producer's pinned reading. Curator GET 2026-10-23 of the sources not re-read (mechanical source evidence, not semantic verification): S20: HTTP 200, bytes differ from the producer pin; S21: HTTP 200, bytes differ from the producer pin. Documents/code read 2026-10-22; nothing rendered, measured or imported. Epic Maya/Houdini groom exporter pages (S20, S21) and the 15 groom_group_id limit not re-read; 'informal groom_* schema' wording from producer reading.
Limitations: Documents/code read 2026-10-22; nothing rendered, measured or imported.
Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.
Structured fields
{
"citations": [
{
"url": "https://www.sidefx.com/docs/houdini/io/alembic.html",
"note": "Houdini Alembic files page (live; differs from pin), geometry type table; Houdini SOP Import LOP (live; differs from pin), NURBS Curves and Set Missing Widths; Unreal Engine docs: Using Alembic for Grooms (live; differs from pin), Curves and Width"
},
{
"url": "https://www.sidefx.com/docs/houdini/nodes/lop/sopimport.html",
"note": "Houdini Alembic files page (live; differs from pin), geometry type table; Houdini SOP Import LOP (live; differs from pin), NURBS Curves and Set Missing Widths; Unreal Engine docs: Using Alembic for Grooms (live; differs from pin), Curves and Width"
},
{
"url": "https://dev.epicgames.com/documentation/en-us/metahuman/groom-exporter",
"note": "Houdini Alembic files page (live; differs from pin), geometry type table; Houdini SOP Import LOP (live; differs from pin), NURBS Curves and Set Missing Widths; Unreal Engine docs: Using Alembic for Grooms (live; differs from pin), Curves and Width"
},
{
"url": "https://dev.epicgames.com/documentation/metahuman/houdini-groom-exporter?lang=en-US",
"note": "Houdini Alembic files page (live; differs from pin), geometry type table; Houdini SOP Import LOP (live; differs from pin), NURBS Curves and Set Missing Widths; Unreal Engine docs: Using Alembic for Grooms (live; differs from pin), Curves and Width"
},
{
"url": "https://dev.epicgames.com/documentation/en-us/unreal-engine/using-alembic-for-grooms-in-unreal-engine",
"note": "Houdini Alembic files page (live; differs from pin), geometry type table; Houdini SOP Import LOP (live; differs from pin), NURBS Curves and Set Missing Widths; Unreal Engine docs: Using Alembic for Grooms (live; differs from pin), Curves and Width"
}
]
}Evidence claims
- [sourced_fact] Houdini 22.0 imports Alembic curve sets as open polygons (no separate groom type in that mapping); its SOP Import LOP writes cubic-only BasisCurves for Hydra or NurbsCurves for round-tripping, and offers Set Missing Widths because USD's fallback width is 1.0. Unreal's Alembic groom importer reads ICurves, converts DCC width to groom_width without overwriting an authored groom_width, and falls back to 1 cm when no width exists, so missing widths behave differently in USD (1.0 scene unit) and Unreal grooms (1 cm). · locator: Houdini Alembic files page (live; differs from pin), geometry type table; Houdini SOP Import LOP (live; differs from pin), NURBS Curves and Set Missing Widths; Unreal Engine docs: Using Alembic for Grooms (live; differs from pin), Curves and Width source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |
Linked records
- cites → https://dev.epicgames.com/documentation/en-us/metahuman/groom-exporter
- cites → https://dev.epicgames.com/documentation/en-us/unreal-engine/using-alembic-for-grooms-in-unreal-engine
- cites → https://dev.epicgames.com/documentation/metahuman/houdini-groom-exporter?lang=en-US
- cites → https://www.sidefx.com/docs/houdini/io/alembic.html
- cites → https://www.sidefx.com/docs/houdini/nodes/lop/sopimport.html