RoboXR — How To Guide

What is AAXLP?

AAXLP (AI-Assisted XR Layout Planning) is a factory floor layout planning application for VIROO-based VR projects. It lets users design and edit a factory layout in VR using voice commands, ChatGPT AI command parsing, and direct object manipulation. The module is fully embedded inside the Unity project (not a separate installed package after initial import).

AAXLP System Architecture — showing the relationship between voice input, AI pipeline, layout editing, and data persistence

Installation

1. Install VIROO Studio 2.6.941 Follow the official VIROO documentation to install VIROO and all its dependencies. AAXLP was built and tested with VIROO Studio version 2.6.941.
2. Install OpenAI Unity Package In Unity Package Manager → Add package from git URL:
   https://github.com/srcnalt/OpenAI-Unity.git
3. Install Unity Sentis (Inference Engine) In Unity Package Manager → Add package by name:
   com.unity.sentis
   Note: Unity Sentis has been rebranded to "Inference Engine" in newer Unity versions.
4. Import the AAXLP Package In Unity: Assets → Import Package → Custom Package…
   Navigate to and select the AAXLP .unitypackage file. Import all contents.

Layer Configuration

AAXLP requires layers 16–21 to be set exactly as follows. These must be configured manually in Edit → Project Settings → Tags and Layers.

16 Floor

17 Placing

18 Ceiling

19 Wall

20 Boundary

21 WallPoint

Layers 22–29 are free for your own use.

Correct Layers tab configuration

Project Configuration

1. Enter OpenAI API credentials Open Assets/Scenes/VR scene. Select the Manager GameObject in the Hierarchy. In the Inspector, find the ChatGPTController component and enter your OpenAI API key and Organization ID.
2. Set Active Input Handling to "Both" Edit → Project Settings → Player → Other Settings → Configuration
   Set Active Input Handling to Both.
3. Add "VIROORoot" tag In Edit → Project Settings → Tags and Layers, add a new tag named exactly VIROORoot. Then in the VR scene, assign this tag to the Root GameObject.
4. Remove Space key from Submit input Edit → Project Settings → Input Manager. Find the Submit input and clear the Alt Positive Button field (remove "space").
5. (Optional) Configure desktop testing To test in the Unity Editor without a VR headset, configure the VIROO bootstrap mock. See the screenshot below for the correct settings.

VIROO Bootstrap Mock configuration for testing without a VR headset

Testing the Installation

1. Open the VR scene Open Assets/Scenes/VR.unity in Unity.
2. Enter Play mode Press the Play button or Ctrl + P.
   Expected result: the "Welcome to AAXLP" starting menu appears after a few seconds with no error messages in the Console.
3. Test Free Mode — New Layout Select four or more wall points in the environment to define a room boundary. Name the layout. The room should generate without errors.
4. Test Free Mode — Item Manipulation

   • Spawn item: press Q to open the commands menu
   • Delete item: press Left Mouse Button while looking at an item → options menu → Delete
   • Move item: hold E while looking at an item
   • Connect items: options menu → Manage Connections → Add a New Connection → click another item
   • Miniature mode: drag the World Scale slider (top right) — connections are disabled in miniature mode (expected)
5. Test Load Layout Stop and restart Play mode. From the menu choose Load Layout — your saved layout should appear and load successfully.
6. Test Scenario Mode Load each available scenario and follow the voice instructions. Complete each scenario without errors.

System Architecture — Script Responsibilities

Unity Events Reference (20+ endpoints)

All AAXLP events are accessible in the Inspector via the (+) button on each script. Use them to trigger custom functions without coding.

Unity Events as shown in the AAXLP manual

Using Your Own 3D Models

1. Open the Manager GameObject in the VR scene Find the ItemHandler component in the Inspector.
2. Add items to the Items array Each item entry has three fields:

   • Name — must be unique and contain no whitespace
   • Type — category label; can be shared across items, but also no whitespace
   • Prefab — the 3D prefab to spawn
3. Prepare the prefab correctly The prefab must have:

   • One or more child mesh objects with MeshRenderer + MeshFilter, or a SkinnedMeshRenderer
   • Layer set to Default
   • No Collider components on the prefab (AAXLP manages these itself)
4. (Optional) Customise the Boundary Canvas Edit the Boundary Canvas prefab referenced in ItemHandler to display custom info on items. Do not remove existing elements and do not rename or reorder the four ruler objects.

What is this Integration?

The VIROO Integration for VR Builder (D9 package) enables seamless use of VR Builder — a powerful node-based authoring tool for creating interactive VR training scenarios — within VIROO Studio. It replicates VR Builder's core functionality while adding multi-user synchronisation, VIROO interaction system support, and role-based permission management.

Architecture diagram: Unity scene → VR Builder process → VIROO Integration module → multi-user deployment

System Requirements

Installation

1. Set up VIROO Studio 2.6 Template Project Unzip and open the VIROO Studio 2.6 template project in Unity 2022.
2. Import VR Builder 5.3.1 or later Import from Unity Asset Store or package file.

   • If a Layer 31 overwrite dialog appears → click Skip as many times as needed
   • On the last page of the import wizard → untick "Load demo scene" to avoid unnecessary content
3. Disable VR Builder's built-in interaction system Edit → Project Settings → VR Builder
   Untick "Enable built-in interaction component" — you will use the VIROO interaction system instead.
4. Import VR Builder Permission Management package This is a dependency of the VIROO Integration. Import it before step 5.
5. Import the VIROO Integration for VR Builder package Import the VIROO Integration package. This completes the setup.

Scene Setup

Creating a New VIROO Scene

1. Open Scene Setup Wizard Tools → VR Builder → Scene Setup Wizard…
2. Select VIROO as scene type Choose VIROO from the scene configuration dropdown.
3. Create a new scene (recommended) For best results create a new scene. If using an existing scene, it must already be VIROO-compatible (the wizard does not apply VIROO-specific changes to existing non-VIROO scenes).

VIROO Scene Requirements (mandatory checklist)

• All GameObjects are parented to the Root object in the Hierarchy
• VR Builder config objects are under Root → VR Builder
• Floor objects are on Layer 8 ("Physics-Floor")
• Every interactable has a Process Scene Object component
• After configuring an object in the Step Inspector: open VIROO Network Object component → click "Generate Object ID"
• Tag VIROORoot is assigned to the Root GameObject

Process Editor

The Process Editor is the main authoring tool for VR training scenarios. Open it from: Tools → VR Builder → Process Editor or Window → VR Builder → Process Editor

VR Builder Process Editor — Chapters list (left), graph view (right)

Step Inspector — behaviors panel

Transition with conditions

Node Types

Step (default)

The main building block. Empty by default — execution proceeds immediately to the next node. Add Behaviors and Conditions in the Step Inspector to build your logic.

Step Group

A self-contained sub-chapter with its own node graph. Has one input and one output. Double-click to expand. Use to keep the main graph tidy. Create a group by selecting nodes → right-click → Make group.

Step Group node — expandable sub-chapter

Parallel Execution

Runs two or more step sequences simultaneously. Execution continues when all non-optional paths complete. Optional paths are immediately interrupted at that point.

• Non-optional path — continuous arrow icon — must complete
• Optional path — interrupted arrow icon — interrupted when non-optional paths finish (good for looping hints)
• Use the + button to add more paths

Parallel Execution node

Parallel path graph

End Chapter

Immediately ends the current chapter and starts a specific chapter selected from a dropdown. Useful for non-linear processes. Not required for linear processes — an empty transition automatically ends the chapter.

Permission Management

Project Settings → VR Builder → Roles and Permissions

Roles and Permissions panel — enabling and configuring policies

Configuration

• Open: Edit → Project Settings → VR Builder → Roles and Permissions
• Tick "Enforce user role policies" checkbox to activate the system
• Each role has a display name and a unique ID (default: GUID, can be changed to something readable)
• Tick/untick policy checkboxes per role to grant permissions

Assigning Roles

Built-in Policies

Permission Check (Code)

The user ID is IPlayer.ClientId — accessible from the IPlayer component on the user's rig or via ISessionClientsProvider.

VIROO-Specific Behaviors & Conditions

Find all VIROO-specific items in the VIROO section of the Behaviors and Conditions menus in the Step Inspector.

Execute VIROO Actions — Behavior

Grip Button Condition

Pull Lever Condition

Push Button Condition

Set Slider Condition

Turn Knob Condition

Multi-User Limitations

Best Practices, Testing & Logging

Design Best Practices

• Use VR Builder for the linear step-by-step process (actions the user must perform in order)
• Use VIROO actions and interactions for things that should be interactable at all times (not locked by VR Builder)
• Objects without a Process Scene Object component are never locked by VR Builder — users can always interact with them
• Split processes into logical chapters and step groups to keep graphs manageable

Testing Shortcuts

• To skip to a specific chapter quickly: add an End Chapter node as the very first step, pointing to the target chapter
• Temporarily disconnect steps in the graph to skip sections you don't need to test
• VR Builder Pro users: use menu prefabs to skip steps/chapters at runtime

Verify Setup in Play Mode

Expected console output when pressing Play with a correctly configured VIROO + VR Builder scene

Logging Configuration

Adjust logging granularity in Edit → Project Settings → VR Builder → Logging

VR Builder logging settings window

Update Strategy

Extending VR Builder

Custom behaviors and conditions can be created by extending VR Builder's API.

• Custom behaviors: mindport.co/vr-builder-tutorials/creating-custom-behaviors
• Custom conditions: mindport.co/vr-builder-tutorials/creating-custom-conditions
• Custom permission policies: extend Policy or ConfigurablePolicy abstract classes
• Full documentation: documentation.mindport.co

Production Hall Overview

The learner enters a modern industrial production hall where three robotic tending cells operate in parallel. The environment reflects a realistic manufacturing setup with walkways, safety fencing, and structured material flow.

XR production hall viewed from operator level — fenced robotic cells with 6-axis robot arms, AGV units, and palletised material

Three-cell layout overview

Cell configuration — robots, conveyors, safety fencing

Each Robotic Cell Contains

Three Cell Entry/Exit Configurations (intentional variation for teaching)

Learners observe how these layout decisions directly affect accessibility, safety, and workflow efficiency.

Learner Roles

All three roles operate within the same unified production hall:

Multi-cell production hall — shared logistics infrastructure

Cell detail — material handling and robot workspace

Scenario 1 — XR Layout Planning (AAXLP)

Activities

1. Compare the three cell entry/exit configurationsObserve how opposite-side, opposite-corner, and U-flow layouts affect operator access and AGV routing.
2. Adjust robot, machine, and conveyor placementUse the AAXLP drag-and-drop system to reposition factory items. Voice commands supported.
3. Visualise robot reach and safety zonesView the robot arm reach envelope overlaid on the layout to ensure safe clearances.
4. Evaluate AGV path routing and workspace clearanceCheck that AGV paths are unobstructed and that operators have clear walkways.

Scenario 2 — Robotic Machine Tending (REACH)

Activities

1. Verify machine readinessCheck that the process machine is in a ready state before starting the tending cycle.
2. Perform the robot load/unload cycleFollow the structured VR Builder process to load raw material and unload finished parts.
3. Monitor machine stateTrack the machine's operational state during processing (running, error, complete).
4. Transfer finished part to conveyor or AGVComplete the cycle by delivering the finished part to the next stage in the flow.
5. Respond to incorrect sequencingHandle error states when steps are performed out of order or incorrectly.

Scenario 3 — Safety & Human–Robot Interaction (HRI)

Activities

1. Detect restricted and warning zonesIdentify the different safety zone types (restricted, warning, collaborative) around each robotic cell.
2. Observe speed reduction and stop behavioursWatch how the robot responds when a human enters a defined safety zone (speed reduction, full stop).
3. Activate emergency stopLocate and trigger the emergency stop device. Verify that the robot halts correctly.
4. Respond to human entry and AGV conflictsHandle scenarios where a person enters a robot workspace or an AGV path is blocked.

Safety fencing, restricted zones, and operator areas

Human–robot interaction zones with safety indicators

VORAUS Industrial Connection

The XR environment is not limited to visual simulation. It can connect to the VORAUS industrial automation system via WebSocket for real robot control.

VORAUS system connection architecture — VIROO ↔ WebSocket ↔ Industrial control layer

Two Operating Modes

What the WebSocket Interface Enables

• Real robot control from within the XR environment
• Industrial process monitoring inside XR
• Integration with higher-level automation systems
• Transforms the XR scene from a training tool into a software-driven automation interface

Figure 1: Robot controlled via industrial-level VORAUS system

Figure 2: WebSocket configuration for VORAUS connection

Scenario 1 — AI-Assisted Industrial Layout Optimisation (AAXLP)

Storyboard — 5 Panels

Actions

Scenario 2 — Robotic Machine Tending (REACH)

Storyboard — 5 Panels

Actions

Scenario 3 — Safety & Human–Robot Interaction (HRI)

Safety Zone Model

Storyboard — 5 Panels

Actions