THREE.JS / FOUNDATIONS 124

Know your bytes.

The same two-attachment MRT scene is rendered as RGBA8, RGBA16F, or RGBA32F. Readback exposes the actual typed array, byte width, and decoded values instead of hiding precision behind a preview.

Initializing -

Creating the attachment format matrix.

backend: -
target: -
type: -
color space: -
typed array: -

Format matrixrebuild target

renderer target color type color space internal scale attachment view

animate objects

Target policywaiting

size: -
attachments: -
bytes / texel: -
MSAA: 0

The two MRT attachments intentionally share one type and color-space policy.

Backend capability snapshot pending.

Beautytexture 0 / output

readbacks: 0
values: -

Normaltexture 1

readbacks: 0
values: -

Timing and readbackwaiting

CPU frames: -
CPU avg: -
CPU p95: -
readbacks: 0
last read: -
bytes/pixel: -

Readback values are shown as raw channel values and decoded floating-point values when the target uses half or full float.

Scene -> MRT { beauty, normal } -> typed target texture -> preview / readback

MSAA is fixed at 0 here so format precision stays isolated. For packed G-buffer data, `NoColorSpace` is usually the truthful policy; sRGB encoding is a color-output contract, not a normal/data-buffer policy.

Compare layered readback next →

LAB 124 / ATTACHMENT FORMAT MATRIX