Debug
Inspects values passing through the graph. Passes the input through to the output unchanged while reporting the value in the performance HUD.
Category: Utility Menu path: Utility > Debug
Ports
| Port | Type | Direction | Description |
|---|---|---|---|
in | imageRgba16f | input | Any value to inspect (accepts all port types via compatibility) |
out | imageRgba16f | output | Passthrough of the input (unchanged) |
Parameters
None.
How It Works
Debug is a passthrough node -- whatever comes in goes out unchanged. Its purpose is to inspect values at any point in the graph. The node reports the value it sees to the performance HUD via DebugValue, which appears in the perf store's debugValuesMap.
Debug probe mode: Debug nodes with connected inputs are seeded as additional BFS roots during graph evaluation, so a standalone Debug probe attached anywhere in the graph will evaluate even without a path to the Output node. This makes Debug useful for inspecting side branches.
Value types reported:
- Scalar: displays the numeric value
- Vec2/Vec3: displays component values
- Color: displays RGBA components
- Texture: displays dimensions (e.g., "Texture 1920x1080")
- Other types: displays type name and summary
Usage Examples
Basic: Inspect a value
Math.out -> Debug.in. Open the perf HUD (backtick key) to see the Debug node's value for the current frame.
Inline passthrough
Insert Debug between two nodes: ImageSource -> Debug -> Transform2D. The image passes through while you can inspect its dimensions.
Side branch probe
Attach Debug to any node's output without routing through Output. The Debug node evaluates independently and reports the value.
Tips
- Toggle the perf HUD with the backtick key (`) to see debug values
- Debug nodes have zero performance cost for texture passthrough (they share the reference, not copy)
- Texture thumbnails are not currently rendered in the HUD -- textures show as "Texture WxH" text
- Multiple Debug nodes can be placed throughout the graph to monitor different points simultaneously