Rendering

How Mowo draws a frame. A deferred renderer on one RHI with four backends, real-time Global Illumination and five quality tiers.

Last updated Oct 26, 2026Edit this pageVersion 1.0.0

Mowo renders every scene through one deferred renderer, SceneRenderer. It records its passes through an abstract RHI, so the same frame runs on each backend: D3D11RHI, D3D12RHI, MetalRHI, VulkanRHI. A quality tier decides which features run, and every feature has a console variable that can override the tier.

This section explains how a frame is built, how to choose a backend and a tier, and how lights, shadows, Global Illumination, ray tracing, upscaling, materials and post-processing fit together.

The layers

Rendering code is split into layers. You mostly work with the top one.

LayerModuleWhat it owns
Scene componentsSceneTypes, GameLights, sky, reflection captures, mesh, splat and volume components and their actors
Scene rendererSceneRendererThe deferred pipeline, Global Illumination, shadows, post-processing, quality tiers ()
Renderer dataRendererMaterials, meshes, light structs and per-frame data (RenderFrameData, ScenePostProcess)
RHIRHI plus D3D12RHI, VulkanRHI, MetalRHI, D3D11RHIThe abstract GPU API, the render graph, upscaler and frame-generation interfaces. The RHI module holds no backend code.
Engine note

Each backend registers a factory when its module loads, and the abstract Create() calls dispatch through it. Capability gating has two axes: says what an API can ever do, and the live RendererCapabilities say what this device can do now. The editor hides a control the API can never support and greys one the device lacks.

How a frame is drawn, in short

Opaque geometry writes a G-Buffer first, and lighting runs once per pixel over it. Translucent surfaces are drawn forward afterward, and post-processing finishes the frame.

  1. Shadows
  2. G-Buffer
  3. Velocity
  4. AO
  5. Lighting
  6. GI
  7. Sky
  8. Reflections
  9. Fog
  10. Translucency
  11. Post
  12. Upscale
  13. Tonemap
  14. Overlays
A simplified view of the pass order. The full order is on the Frame pipeline page.

Read Frame pipeline for every stage in order.

What you get at each tier

There are five tiers: Low, Medium, High, Epic and Cinematic (). High is the code default; when you do not pick one, the engine picks a tier for the machine at launch.

TierWhat it adds
LowClustered lighting, 2-cascade sun shadows, 0.75 render scale. No live Global Illumination (a baked field if present), no SSR, no GTAO.
MediumGlobal Illumination with world probes, SSR, GTAO, bloom, motion blur, subsurface scattering, SDF far sun shadows.
HighThe screen-probe gather, 4 cascades, soft shadows, a depth prepass, translucent reflections, the terrain virtual texture.
EpicVirtual shadow maps for sun and local lights, MegaLights, ray-traced reflections and AO, the ray-traced GI gather, volumetric fog and clouds, the meshlet G-Buffer.
CinematicRay-traced sun shadows, larger budgets everywhere, no small-object or occlusion culling, native resolution.

The rows come from. Ray-traced features need a GPU and backend with ray query; without one they fall back to their raster or screen-space versions each frame.

Note

The editor viewport always renders at native resolution with a temporal AA resolve, whatever the tier's upscaler says, so you never judge reconstructed pixels. The shipped game keeps the tier's upscaling.

Four side-by-side captures of the same sunlit interior scene from the Sample project at identical camera positions, rendered at the Low, Medium, High and Epic tiers selected from Edit > Engine Quality, each labeled with its tier name in the top-left corner
The same view at four quality tiers.

Backends at a glance

PlatformDefaultAlso available
Windows x64Direct3D 12Vulkan (selectable), Direct3D 11 (automatic fallback only)
macOS on Apple siliconMetalNone
Linux x64Vulkan In developmentNone

See Backends for how to switch and what each API supports.

Pages in this section

API reference

Engine sources

This page describes behavior implemented in these files of the engine repository, checked against commit 5922e6e5e.

  • Engine/Source/Runtime/SceneRenderer/Public/Renderer/SceneRenderer.h
  • Engine/Source/Runtime/RHI/Public/RHI/RendererAPI.h
  • Engine/Source/Runtime/RHI/Public/RHI/RHIFactory.h
  • Engine/Source/Runtime/Renderer/Public/Renderer/RenderFrameData.h

Page feedback

Was this page helpful?