Log inGet started
What it does

display_curve

The chain's display transform in Luau, for a suite that reads a rendered pixel and has to say what light produced it.

__display__ runs on every frame the engine delivers, so a surface answering a known light value does not arrive at the frame as that value: it arrives as the Khronos PBR Neutral tone curve of it, encoded for a display. shownRGB is that pair composed — hand it the light a case authored and it answers the code values the capture should read.

local DisplayCurve = require("@builtin::tests.fixtures.display_curve")
local expected = DisplayCurve.shownRGB({ 0.8, 0.2, 0.2 })
-- … compare `expected` against the pixel the capture returned …

The curve mixes channels by their shared peak, so neutralCurve and shownRGB take the whole triple; a case holding a single channel still passes the three. srgbEncode is the transfer function alone, for a case that holds __display__ at curve = 0 and measures the encode by itself. srgbDecode is its inverse, for a case that reads such a frame back and needs the light a code value came from — dividing out the exposure the frame was captured under recovers the scene-referred value.

The formula is zero_display_neutral in src/engine/renderer/subsystems/post_process_renderer.rs, read on a light triple rather than on a fragment.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

This asset doesn't declare a schema or structured payload.

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

0items
This part has no composite children. See the Files segment for its leaf payloads.
This part has no leaf payloads.

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.