Configuration

The ScreenStatsOverlay inspector groups settings into Metric Presets, Placement & Visibility, Visible Metrics, Frame-Time Graph, Appearance, and Update Cadence & Input. Public setters normalize values to the same limits as serialized inspector data.

Placement And Visibility

Setting	Default	Purpose
Visible On Start	Enabled	Initial requested visibility when Build Scope allows the component.
Build Scope	Editor + Development	Choose Editor + Development, All Builds, or Editor Only activation.
Target Camera	None	Optional authoritative Game camera. Leave empty for automatic enabled-Game-camera selection.
Attached Camera	Runtime status	Read-only camera currently selected by the overlay.
Corner	Top Left	Top-left, top-right, bottom-left, or bottom-right camera-viewport anchor.
Margin	(12, 12)	Camera-pixel inset, clamped to 0–8192 on each axis.
Text Scale	2	Integer bitmap scale from 1–6. Fractional runtime input is rounded.
Auto-Fit Small Views	Enabled	Reduces effective text scale, down to 1, when configured content does not fit.
Respect Screen Safe Area	Disabled	Adds Screen.safeArea insets for display-camera output. Ignored for cameras targeting a RenderTexture.

An assigned Target Camera is authoritative. If it becomes unusable, the overlay waits instead of silently moving to another camera. Auto-fit changes text scale only; it does not resize the configured graph. ContentFits reports whether the complete layout fits after auto-fit.

Metric Presets

Presets change only built-in metric sections and the graph:

Preset	Enabled content
Compact	FPS + Frame Time and CPU + GPU Timing text.
Standard	FPS, CPU/GPU timing, memory, render counters, and graph without verbose device text or Budget.
Full	All built-in measurements, Budget, and graph.

Custom rows, camera, layout, colors, cadence, and build scope remain unchanged when a preset is selected.

Visible Metrics

Section	New-component default	Content
Device Details	Off	Device, OS, processor, GPU, graphics memory, and graphics API/version.
FPS + Frame Time	On	FPS and corresponding smoothed frame duration.
CPU + GPU Timing	On	Independent values supplied by Unity's FrameTimingManager.
Memory	On	Managed GC and system-memory profiler counters.
Render Counters	On	Draw calls, batches, triangles, and vertices.
Frame Budget Summary	Off	Recent maximum, P99, 1% low, and misses against Target FPS.
Custom Numeric Stats	Off	Up to four fixed rows supplied through the runtime API.

Unavailable profiler and timing measurements display --. Enabling a section cannot make an unsupported source available.

Frame-Time Graph

Setting	Default	Accepted range or behavior
Show Graph	Enabled	Displays observed frame samples and a target-budget marker.
Width	240	60–600 camera pixels.
Height	64	24–200 camera pixels.
Bar Width	2	1–8 camera pixels per observation.
Graph Ceiling (ms)	33.33	1–1000 ms; taller observations are clipped visually.
Target FPS	60	1–1000 FPS for marker, bar thresholds, and budget misses. Does not set application frame rate.
Color Bars By Budget	Disabled	Uses warning above one target budget and critical above two target budgets.

Appearance

The configurable colors are Text Color, Graph Bars, Budget Warning, Budget Critical, Graph Background, Target Marker, and Backdrop Color.

Timing Smoothing defaults to 0.9 retention and accepts 0–0.99. Higher values react more slowly. It affects only FPS and frame-duration text, not graph observations.

Text Backdrop is disabled by default. When enabled, it draws a translucent background behind the measured text without adding a second material or UI framework. Backdrop Padding defaults to 4 and accepts 0–16 camera pixels. Presets do not change appearance.

Update Cadence And Input

Setting	Default	Behavior
Text Updates / Second	4	1–30. Controls text mesh refresh plus timing capture, recorder consumption, and Budget analysis when those sections are enabled.
Graph Updates / Second	12	2–60. Controls graph geometry refresh, not frame-history sampling.
Legacy Toggle Key	None	Optional legacy-input shortcut. Leave None for project-owned Input System actions or debug menus.

Increasing a visual refresh rate cannot make unavailable timing or profiler data appear. Configure the lowest cadence that answers the current diagnostic question on the actual target.