Physics3D, Terrain, Navmesh, Character3D, and Compute Exact Reference

Use this page when the task is in simulation-heavy world systems before networking or full session orchestration is mixed in.

Table of Contents

1. Covers
2. Open These Handbook Pages First
3. Canonical Contracts
4. Namespace Coverage Summary
5. Namespaces
6. Non-Namespace Contract Topics

Covers

• aura.physics3d
• aura.navmesh
• aura.compute
• Terrain and character3d behavior is still routed through the 3D contract family even where the generated schema does not expose a standalone namespace list for every helper section.

Open These Handbook Pages First

• external/game-dev-api/10-physics-terrain-navmesh-character3d-and-compute.md

Canonical Contracts

• api-contract.md
• api-contract-3d.md

Namespace Coverage Summary

Namespaces

`aura.physics3d`

Optional 3D rigid-body APIs including bodies, fixed-step controls, queries, snapshots, and public joints when modules.physics=true.

• Native support: supported
• Web support: unsupported
• Exact signatures in generated schema: 1
• Additional known method names: 10
• Contract source: api-contract.md

Exact Signatures

aura.physics3d.queryRaycast(...)

Additional Known Method Names

aura.physics3d.body(...)
aura.physics3d.captureSnapshot(...)
aura.physics3d.configureStep(...)
aura.physics3d.queryAABB(...)
aura.physics3d.queryPoint(...)
aura.physics3d.replay(...)
aura.physics3d.restoreSnapshot(...)
aura.physics3d.rollback(...)
aura.physics3d.setGravity(...)
aura.physics3d.step(...)

Exact signature extraction is still incomplete for the methods above. Use the canonical contract source if argument or return-value detail matters.

`aura.navmesh`

No generated description is available yet for this namespace.

• Native support: supported
• Web support: see_web_build_contract_v1
• Exact signatures in generated schema: 5
• Additional known method names: 0
• Contract source: api-contract.md

Exact Signatures

aura.navmesh.create(definition)
aura.navmesh.findPath(meshId, start, end)
aura.navmesh.getInfo(meshId)
aura.navmesh.queryPath(...)
aura.navmesh.unload(meshId)

`aura.compute`

Native compute pipeline, buffers, bind groups, dispatch, and readback.

• Native support: supported
• Web support: unsupported
• Exact signatures in generated schema: 10
• Additional known method names: 0
• Contract source: api-contract-3d.md

Exact Signatures

aura.compute.createBindGroup( pipelineHandle: ComputePipelineHandle, entries: ComputeBindGroupEntry[] ): ComputeBindGroupHandle
aura.compute.createBuffer( size: number, usage?: ComputeBufferUsage ): ComputeBufferHandle
aura.compute.createPipeline( wgslCode: string, entryPoint?: string ): ComputePipelineHandle
aura.compute.destroyBindGroup(handle: ComputeBindGroupHandle): void
aura.compute.destroyBuffer(handle: ComputeBufferHandle): void
aura.compute.destroyPipeline(handle: ComputePipelineHandle): void
aura.compute.dispatch( pipelineHandle: ComputePipelineHandle, bindGroupHandle: ComputeBindGroupHandle, workgroupsX: number, workgroupsY?: number, workgroupsZ?: number ): void
aura.compute.getError( handle: ComputePipelineHandle | ComputeBufferHandle | ComputeBindGroupHandle ): string | null
aura.compute.readBuffer( bufferHandle: ComputeBufferHandle, offset?: number, size?: number ): Float32Array | Uint8Array | null
aura.compute.writeBuffer( bufferHandle: ComputeBufferHandle, data: TypedArray | ArrayBuffer, offset?: number ): void

Non-Namespace Contract Topics

• Terrain and character3d behavior is still routed through the 3D contract family even where the generated schema does not expose a standalone namespace list for every helper section.