Log inGet started
What it does

fx_probe

The reader half of the frame probe: the grid fx_frame_probe.renderFeature writes each frame, and the measurements taken off it.

litRegion is the one that answers a size question. It measures the area of the region rising above a baseline and reports the radius of a disc with that area, so a parameter that claims to change how big something is has a reading to move. A whole-frame number cannot tell an effect that grew from one that merely brightened.

local probe = require("@builtin::tests.fixtures.fx_probe")
local feature = renderer.feature.create("@builtin::tests.fixtures.fx_frame_probe")
-- … let a few frames pass …
local baseline = probe.read()
-- … play the effect …
local lit = probe.litRegion(probe.read(), baseline, 6)
renderer.feature.destroy(feature)

tileAt, faceTiles, sphereTiles and skyTiles answer WHERE to read. The grid covers the whole frame whatever shape the frame is, so a tile box written down for one shape reads a different part of the scene at another. These work out the tiles a world point, the middle of a flat face, the inner part of a sphere, or the sky above the horizon is drawn in from the view the frame was drawn under (camera.viewData(id)), and tilesLuminance and tilesColour read a set of them.

local view = camera.viewData(cam.id)
local plate, offFrame = probe.faceTiles(view, { -4, 40.25, -4 }, { 8, 0, 0 }, { 0, 0, 8 })
local sky = probe.skyTiles(view, { 0, 40, 0 })
local grid = probe.read()
local ratio = probe.tilesLuminance(grid, plate) / probe.tilesLuminance(grid, sky)

local ball = probe.sphereTiles(view, { -3.5, 0, 0 }, 1.5)
local red = probe.tilesColour(grid, ball).r

The two halves are separate assets because renderer.feature.create compiles a feature's init.luau as its own chunk rather than requiring it, so the feature records the target here instead of on its own module table.

A probe is trusted only once it has been shown stable — an unchanged view read twice agreeing — and shown to discriminate, by moving on a control known to change the frame. Both checks belong in the suite that uses it.

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.