Example - Your First Runnable Graph

A Minimal First Graph

This example walks through a tiny graph that runs on the editor's default scene and shows the full loop from start to finish:

1. Add an event block.
2. Add a data block.
3. Add an execution block.
4. Connect them.
5. Run the graph and inspect the result.

You can open the finished graph straight in the hosted editor, fully wired and ready to run: Open this graph in the Flow Graph Editor

If you would rather build it from scratch, start with an empty editor instead: Flow Graph Editor. The steps below walk through wiring it yourself.

Goal

The goal is simple: when the scene becomes ready, the graph logs a message.

This is intentionally small, but it uses the editor in a realistic way and gives you a reliable starting point before you move on to pick events, scene properties, or custom event flows.

Expand

Blocks Used

• SceneReadyEvent
• Constant
• ConsoleLog

You can find these blocks in the following families:

• SceneReadyEvent in Events
• Constant in Data Access
• ConsoleLog in Utility

Step By Step

1. Start With The Default Scene

Open the editor without loading any external content. The default scene gives you a safe environment for first experiments.

2. Add SceneReadyEvent

From the Events family, add SceneReadyEvent to the canvas.

This block is your execution entry point. It fires once the scene is ready to be used.

3. Add Constant

From Data Access, add a Constant block.

In the property panel:

• Set the constant type to String.
• Enter a short message such as Test.

4. Add ConsoleLog

From Utility, add ConsoleLog.

This block is useful for first experiments because it gives immediate confirmation that the graph executed as expected.

5. Connect The Graph

Make two connections:

• Connect the execution output done of SceneReadyEvent to the execution input of ConsoleLog.
• Connect the output value of Constant to the value input message of ConsoleLog.

At that point, the graph has both the control flow and the data it needs.

6. Run The Graph

Press Start.

When the graph runs, the event should fire and the message should be logged.

If you want to confirm execution visually:

• Turn on Debug Mode.
• Run the graph again.
• Watch the active blocks highlight as the graph executes.

What You Learn From This Example

Even this tiny graph teaches the core authoring pattern:

• Events start execution.
• Data blocks provide values.
• Execution blocks perform actions.
• The graph can be inspected visually and iterated quickly.

That pattern scales directly into larger scenes and more complex interactions.

Good Next Steps

After this example, natural follow-ups are:

1. Replace SceneReadyEvent with a pointer or pick event.
2. Replace ConsoleLog with a property-changing or animation-driving block.
3. Add validation, naming, and notes so the graph is easier to maintain.

For deeper reference, continue with Editor Operations and Shortcuts, Validation and Property Editing, and Block Reference.

If you want the next practical step, continue with Example - Click A Mesh And Log It.

Further reading