Component Architecture

How to structure COMPs for modularity, reusability, and clean hierarchy.

COMP Types

• baseCOMP — general container, extensions, custom pars. Most common for modules. Always set display=true after creating
• containerCOMP — has a UI panel, use for anything with a visual interface
• geometryCOMP — renders geometry, contains SOPs/POPs + MATs, has instancing support

Parent Shortcuts

Every COMP that others reference should have a parentshortcut. Set on the COMP itself.

• CamelCase, capital first: Project, Render, Camera, MyModule
• Depth-independent — parent.Project works from any nesting level
• Refactor-safe — reparenting doesn't break references
• Always prefer over ../../ or parent(2)