Rendering and shaders
Section titled “Rendering and shaders”InnoEngine provides rendering mechanisms and extension boundaries. It does not assume a built-in Camera/Light model, PBR material system or one fixed 2D/3D pipeline. A rendering domain or plugin supplies those policies using the neutral contracts.
Choose a task
Section titled “Choose a task”- Author a shader by choosing a graph, source function or optional domain Target.
- Define a source function with explicit inputs, outputs and frozen dependencies.
- Reuse shader graph nodes while preserving stable ports and stage boundaries.
- Work with materials and runtime artifacts without persisting GPU handles.
- Contribute to a rendered frame through requests, models or graph contributors.
- Extend shader Targets and Templates for domain-specific authoring.
- Add a shader primitive only when existing graphs and public IR cannot express it.
Understand the layers
Section titled “Understand the layers”| Layer | Responsibility |
|---|---|
| Rendering Core | Device capabilities, resources, commands and RenderGraph relationships. |
| Runtime assets | Persistent neutral Shader, Material, Texture, Geometry and Pipeline data. |
| Rendering Runtime | Output requests, model generations, GPU caches and retirement. |
| Asset authoring | Imports, source freezing, target candidates and last-good publication. |
| Shader mechanisms | Function analysis, graph lowering and typed stage/region IR. |
Runtime consumes compiled artifacts; it does not interpret graph documents or compile authoring sources during a frame. Product composition selects a backend and platform integration explicitly. Read render-frame ownership before retaining resources or callbacks across frames and reloads.