3D Rendering and Content Exact Reference

Use this page when the work is in the native 3D render path, imported scenes, or 3D asset flow.

Table of Contents

1. Covers
2. Narrower Split Routes
3. Fast Routing
4. Namespace Map
5. Exact Reading Order
6. Practical Rule

Covers

• aura.draw3d
• aura.camera3d
• aura.light
• aura.mesh
• aura.material
• aura.scene3d
• aura.skinnedMesh

Narrower Split Routes

• Draw3D, Camera, Lighting, and PostFX Exact Reference
• Scene3D, Mesh, Material, glTF, and Avatar Exact Reference

Fast Routing

Namespace Map

• render submission: aura.draw3d
• view state: aura.camera3d
• lighting: aura.light
• authored content primitives: aura.mesh, aura.material
• scene graph and imported content: aura.scene3d, aura.skinnedMesh

Exact Reading Order

1. Start with the relevant handbook page.
2. If you already know the subsystem, move to one of the narrower split routes above.
3. Confirm the exact method and option shape in ../api-contract-3d.md.
4. If the task also touches physics, terrain, navmesh, or multiplayer, switch to world-simulation-and-multiplayer-exact-reference.

Practical Rule

If the scene does not render yet, stay in this family until camera, light, mesh, and material are known-good. Do not mix 3D content debugging with physics or networking too early.