Skip to main content

Blueprint Analysis

Why Analyze Blueprints?​

Blueprints can grow complex quickly. You might have:

  • Logic errors that are hard to spot visually
  • Performance issues (too many nodes in Tick)
  • Unused variables cluttering your graph
  • Complex execution flows that are difficult to trace

Orion's Blueprint analysis sends your Blueprint's structure to the AI—not a screenshot, but the actual node graph data (node types, connections, variables, execution flow). The AI can:

  • Spot logic errors ("This event isn't connected")
  • Suggest optimizations ("Move this out of Tick, use a Timer")
  • Explain complex flows ("Here's what this branch does...")
  • Find unused nodes and variables

Method 1: Blueprint Graph Toolbar​

The fastest way to analyze a Blueprint is from inside the Blueprint editor.

Step-by-step:

  1. Open any Blueprint in the editor (double-click from Content Browser)
  2. Look for the Orion toolbar in the top-right area of the Blueprint editor, near the Compile and Search buttons
  3. The toolbar has three buttons: Screenshot | Send ▼ | •••
  4. Click the Send dropdown (middle button with down arrow)
  5. You'll see options:
    • Full Graph — Sends the entire Blueprint structure (all nodes)
    • Selection — Sends only the nodes you've selected in the graph
    • Destination: Orion — Sends to Orion chat (default)
    • Destination: EDA — Exports to Epic Developer Assistant
  6. Click "Send Full Graph to Orion"
  7. The Orion window opens (or focuses if already open)
  8. If "Compile On Send" is enabled (default), the Blueprint is compiled first
  9. Context is sent to AI
  10. AI acknowledges: "I've received the Blueprint for MyActor. What would you like to know?"
  11. Ask follow-up questions:
    • "Are there any logic errors?"
    • "Suggest optimizations"
    • "Explain what this graph does"

Screenshot Placeholders:

  • [Blueprint editor window with Orion toolbar visible in top-right area, highlighted with red box near Compile button]
  • [Orion toolbar's Send dropdown menu expanded, showing options: "Full Graph", "Selection", and destination toggle "Orion" vs "EDA"]
  • [Orion chat window showing user message "Blueprint MyActor is being analyzed..." and AI response "I've received the Blueprint for MyActor with 5 graphs and 47 nodes. What would you like to know?"]

Method 2: Content Browser Right-Click​

You can also analyze Blueprints directly from the Content Browser without opening them.

Step-by-step:

  1. In Content Browser, right-click a Blueprint asset
  2. Scroll to the bottom of the context menu
  3. Hover over "Azimuth Orion" (submenu expands)
  4. Choose analysis type:
    • Blueprint: Graph Flow — Analyzes only execution-flow nodes (events and nodes reachable via exec pins). Faster, focused on logic.
    • Blueprint: Full Graph — Analyzes all connected nodes (execution + data-linked variables). Slower, comprehensive.
  5. Orion window opens
  6. Blueprint context is sent to AI
  7. AI acknowledges receipt

Screenshot Placeholders:

  • [Content Browser with Blueprint asset selected, right-click context menu open, "Azimuth Orion" menu item highlighted at the bottom]
  • ["Azimuth Orion" submenu expanded, showing three options: "Describe to Orion", separator line, "Blueprint: Graph Flow", "Blueprint: Full Graph"]

Compile On Send​

By default, Orion compiles your Blueprint before analysis. This helps the AI diagnose issues.

What it includes:

  • Compiler errors and warnings — "Variable 'Health' not found", "Blueprint has compile errors", etc.
  • Defined variables — List of all variables in the Blueprint

Why it's useful:

  • AI can diagnose: "You're referencing a variable 'Health' but it's not defined. Add a Float variable named 'Health' to the Blueprint."
  • AI sees compiler warnings: "This cast always fails because the types are incompatible."

Compilation log: When Compile On Send is enabled, Orion includes the full compilation log (errors and warnings from the Output Log) in the context sent to Orion and EDA. This helps AI diagnose issues when you paste into EDA or send to Orion.

To toggle Compile On Send:

  1. Settings > Blueprint Context
  2. Check/uncheck Compile On Send (enabled by default)

Screenshot Placeholder: [Settings window showing Blueprint Context category with "Compile On Send" checkbox checked]

Sample Workflow: Debug a Blueprint​

Scenario: You have a character Blueprint with a health system. Damage events aren't reducing health.

Steps:

  1. Open BP_PlayerCharacter in the editor
  2. Click Orion toolbar: Send > Full Graph to Orion
  3. Orion compiles the Blueprint, sends context to AI
  4. AI responds: "I've received BP_PlayerCharacter with 8 graphs and 92 nodes. The Blueprint compiled successfully with no errors. I can see TakeDamage custom event, UpdateHealth function, and Health variable (Float). What would you like to know?"
  5. You type: "Why doesn't the health decrease when I take damage?"
  6. AI analyzes execution flow, identifies the issue: "The TakeDamage event's execution pin is not connected to the UpdateHealth function. The event fires but nothing happens. Connect the exec output pin from TakeDamage to the exec input pin of UpdateHealth."
  7. You fix the connection in the graph
  8. Test in PIE (Play In Editor)
  9. Health now decreases correctly!

Screenshot Placeholder: [Blueprint graph showing TakeDamage event node with exec pin NOT connected to UpdateHealth function node, with a red arrow indicating the missing connection]