Loomguides

The debug panel

Timings, the logical viewport, the live instance tree, loaded typefaces, and a stage inspector.

Every gallery has a debug panel that describes the scene in Roblox terms: instances, sizes and fonts, not the divs a browser inspector shows.

Opening it

Use any of these:

  • the debug button in the sidebar header,
  • Ctrl+Alt+D,
  • ?debug=1 on any gallery URL.

The panel is off by default. While it’s closed it does no work at all, and it never touches the render path, so a scene behaves the same with it open or closed.

A bare ?debug turns it on. 0, false, off, no and none turn it off. Any other value turns it on.

The gallery remembers the toggle across HMR reloads for the tab. An embed (chrome=none) doesn’t, so a panel only appears on an embedded preview when its URL asks for one.

What it reports

Each section folds away and still shows its headline number while folded.

SectionShows
targetThe target’s path and title, how long its import() took, and time from mount to first frame. ↻ re-mounts the target to take those timings again.
viewportThe stage in real pixels, the logical viewport the scene laid out against, Workspace.CurrentCamera.ViewportSize, the scale factor, device pixel ratio and theme.
sceneLive instances, how many are GuiObjects and how many of those are invisible, tree depth, DOM node count, a count per class, and each layer with its DisplayOrder and size.
fontsEvery typeface the scene’s text resolved to, the weights requested, and whether the browser actually loaded each one.
frameFrame rate, DOM patches since the panel opened, and a count of loom’s log messages.
inspectThe object under the pointer. See Inspecting the stage.

Where to look first:

  • A scene looks empty: check the invisible count in scene.
  • A scene looks too small: in viewport, the four sizes agree unless the page uses ?base=. They tell a scene that laid out small from one that was drawn small. See Previews on a phone.
  • Layout differs on another machine: check fonts. A family that never loaded still paints, at the wrong metrics. See Fonts and text metrics.
  • Something is off and you don’t know what: the warnings counted under frame often explain it.

Inspecting the stage

Hover the stage. The panel names the GuiObject under the pointer, outlines it, and lists its ancestry, absolute geometry, UI* modifiers, resolved typeface and properties.

  • Alt+click pins the selection. Escape releases it.
  • Click the ancestry trail or the under rows to walk the tree. The under rows list everything else beneath the pointer.
  • Hit testing uses the scene’s own PlayerGui:GetGuiObjectsAtPosition, not the browser’s. You can inspect a click-through frame that a browser inspector can’t reach.

Taking a snapshot out

copy puts the readout on the clipboard as text. json downloads every section as data, plus the full instance tree with each object’s absolute position and size. Attach that to a bug report instead of a screenshot.

While the panel is open, the same object is available from the console:

In the devtools console, panel open
copy(loomDebug.snapshot());

See also