DocumentationAzkar Screen StatsDocumentation

Azkar Screen Stats

Documentation

Azkar Screen Stats 1.0.0 is a free, compact, camera-scoped Unity runtime diagnostics overlay with development-oriented defaults and bounded mesh rendering.

  • Runtime overlay
  • 1.0.0 features
  • Requirements
  • Retained pre-release evidence

Azkar Screen Stats is a free, compact, camera-scoped runtime diagnostics overlay for Unity. Add one component to see consistent FPS and frame duration, available CPU/GPU timing, memory and render counters, and observed frame-time history directly on a selected Game camera.

The overlay uses a generated bitmap font, bounded internal buffers, manual numeric formatting, and package-owned mesh rendering. It does not require TMP, UGUI, Unity's Input System package, a render-pipeline package, analytics, network access, a runtime account, a subscription, or automatic project-setting changes.

Key Features

  • FPS and smoothed frame duration derived from one consistent value.
  • CPU and GPU timing only when Unity's FrameTimingManager supplies each value.
  • Managed and system memory plus draw calls, batches, triangles, and vertices where Unity exposes them.
  • Observed frame-time history with a target FPS marker instead of synthetic startup samples.
  • Optional recent maximum and frame-budget misses, plus P99 frame time and 1% low FPS after 100 real observations.
  • Four fixed project-owned custom numeric rows and optional budget-colored graph bars.
  • Optional device, operating-system, processor, GPU, graphics-memory, and graphics-API details.
  • Four-corner placement, bounded integer scale, small-view auto-fit, optional safe-area margins, configurable colors, graph sizing, and a translucent text backdrop.
  • Explicit authoritative Target Camera or automatic enabled-Game-camera selection.
  • Show, Hide, Toggle, validated runtime configuration, and a retained read-only snapshot for project-owned integrations.
  • Editor + Development, All Builds, and Editor Only activation policies.
  • Compact, Standard, and Full metric presets that leave camera, layout, cadence, colors, custom rows, and build scope unchanged.
  • Development-gated by default, input-system-neutral bootstrap sample.
  • No required runtime package dependencies, telemetry, network service, or automatic scene injection.

Timing, profiler, budget, and custom fields with explicit availability show -- until valid. General frame duration is never presented as CPU time, and the overlay does not subtract its own rendering work from Unity's counters.

Requirements

  • Declared minimum editor version: Unity 2021.3.45f2.
  • One active, enabled Game camera, either assigned explicitly or selected automatically.
  • A selected camera with a non-empty culling mask and a valid pixel viewport.

The package has no required runtime package dependencies. The shader is designed for the camera-scoped diagnostic mesh, but final composition still depends on the consuming project's pipeline, camera stack, post-processing, renderer features, XR setup, render targets, and projection choices.

Package Information

FieldValue
Display nameAzkar Screen Stats
Package namecom.azkarindustries.azkarscreenstats
Current version1.0.0 — 2026-08-17
Minimum Unity version2021.3.45f2
CategoryTools
Runtime dependenciesNone
AuthorAzkar Industries LLC

Retained Pre-Release Evidence

Earlier package trees produced retained implementation evidence for exact Built-in/Metal consumer rows at the declared Unity 2021 floor and Unity 6000.0, a Unity 6000.4 URP 17.4 row, and Unity 6000.5 Built-in/Metal player checks. These results are not verification of the final 1.0.0 artifact or current Asset Store release approval, and they are not blanket claims about every target, graphics API, or render pipeline.

See Performance And Platform Notes for the complete retained matrix, counts, measured scope, and unvalidated combinations. The exact 1.0.0 artifact still needs to pass the current publishing and release gates before publication.

Data Behavior

The runtime does not use network access, analytics, telemetry, accounts, subscriptions, or external services. It does not install input bindings, add package dependencies, change project settings, or inject itself into scenes.

Device Details read Unity SystemInfo values only after that section is enabled. Those strings are cached in memory for the component's lifetime and displayed locally; the package does not transmit them or write them to disk.