Skip to content
Bit Quirky Behavior Trees and
State Machines

Search documentation

All topics and APIs

Close returns focus to Search.

What are you looking for?

Try a common topic or enter a complete API identifier.

Browse the reference instead

Esc closes · Tab reaches results · Enter opens the focused link

v0.6.0
Menu

Canvas capture

Save the whole graph as a PNG, at full size, without arranging the window or stitching screenshots together.

GameObject + EntityUpdated
On this page

One button writes the entire graph to a PNG and copies it to the clipboard. Dungeon Heist’s Guard2.bqbehavior is wider than any window you can open, and this is how you show it to someone.

The problem

Section titled “The problem”

Explaining a graph in a message means a screenshot, and a screenshot of a graph that does not fit means either three overlapping images or a zoom level nobody can read. Zooming out to fit costs the node names, which are the part that carries the meaning.

Canvas capture renders the whole graph at full size regardless of the window, and puts your pan and zoom back where they were.

Do it

Section titled “Do it”

  1. Open the graph. The capture button sits in the toolbar between Layout and the pan and zoom lock, with the tooltip Capture canvas image: save the whole canvas as a PNG and copy it to the clipboard.

  2. Click it. Below a narrow window width the button lives under the ... overflow as Capture canvas image.

  3. Read the status bar. It names the project-relative file, then adds either · copied to clipboard or · clipboard copy unavailable.

The capture button in the toolbar, above the status bar line confirming the written file and the clipboard copy
Figure 1. Two crops of one window, because the button and its confirmation sit at opposite ends. The button is disabled until a document is open.

What lands in the file

Section titled “What lands in the file”

The capture renders the graph at 100 percent, so node names, status words, and decorator pills are legible at their authored size. It covers the whole graph rather than the visible region, which is why a wide guard tree comes out as one readable image.

Recordings/ sits beside Assets/ in the project root, outside the imported asset tree, so a capture is a throwaway file and never becomes project content.

The clipboard copy is best effort per platform, and it is the part most likely to be unavailable. When it fails, the file is still written and the status bar says so.

Use it for

Section titled “Use it for”
  • A message or a bug report where the shape of the graph is the point.
  • A before and after pair around a refactor of a big branch.
  • A record of a Live graph mid-run, since the capture includes the status colors the canvas is showing.

When it goes wrong

SymptomCheckFix
The button is missing.Read the window width.Widen the window, or open the ... overflow menu.
The button is disabled.Confirm a document is open.Open a graph. An empty canvas still enables the button; a click then says "Nothing to capture: open a graph with nodes first."
Nothing arrived on the clipboard.Read the status message for "clipboard copy unavailable".Use the written file. Clipboard support depends on the platform tool being present.
You cannot find the file.Look in Recordings/BehaviorTreeEditor/ in the project root, beside Assets/.The status bar prints the project-relative path of the file it just wrote.
The image is enormous.The capture is the whole graph at full size.Capture a referenced subgraph on its own, or split the graph, which the editor hub covers.

Next

Section titled “Next”
  • Editor: the toolbar this button belongs to.
  • Live colors: what a capture of a running graph is showing you.
  • Help: where a captured graph is worth attaching.
Full-size image