Tutorial 0 — Hello LUIDA

What you'll do

1. Open ProteusSample.unity in Unity                          (3 min)
2. Register a test experiment + a VEQ questionnaire           (3 min)
3. Paste the Experiment ID into Unity                         (1 min)
4. Press Play; walk through two trials                        (3 min)
5. Check the Unity Console for the request log                (1 min)
6. Confirm the uploaded data in the Web Console               (3 min)

Step 1 — Open the ProteusSample sample

Step 2 — Register a test experiment on the Web Console

If you already registered an experiment in Setup → Connect to Console, reuse it and skim this step.

Create the experiment

Sign in at luida.cluster.mu/experiments and click + New Experiment.

• Title: Hello LUIDA
• Room capacity: 1
• Status: Testing

Save. The experiment detail page opens.

Add the VEQ questionnaire

On the experiment detail page, find the Questionnaires section and click + Add Questionnaire. In the Template Selection dropdown, pick VEQ and click Add. The sample shows this VEQ after each trial.

Note the eID

The eID is shown at the top of the experiment detail page. You'll paste it into Unity in Step 3.

Step 3 — Link the experiment to Unity

Unity menu: LUIDA → Configure experiment identifiers. Paste the eID from Step 2 into the Experiment ID field and leave Number of Participants at 1. Close the window when you're done.

(If the window still shows the Cluster login screen, finish Setup → Log in to Cluster from Unity first.)

Step 4 — Press Play and walk through the sample

Press Play

Click the ▶️ button on Unity's top toolbar. The Game window starts in the player's perspective with a welcome message.

Walk through two trials

What you'll see:

1. The welcome message disappears automatically after ~5 s.
2. Trial 1 — A mirror appears with one of two avatars (elder or young) embodied as you. It stays for ~10 s.
3. The mirror hides; two bridges appear. Walk across either one (WASD).
4. A questionnaire prompt appears at the far end. Click it, answer each VEQ item on the 1–7 scale, and submit.
5. Trial 2 — You're returned to spawn and embodied as the other avatar. Same flow: mirror → bridges → questionnaire.
6. After both trials a portal appears. Session done.

If something doesn't behave as described, see the troubleshooting section.

Exit Play mode

Click the ▶️ button on Unity's top toolbar again.

Step 5 — Check the Unity Console

Open the Console (Window → General → Console if it isn't open). During Play you should see request JSON lines for each questionnaire submit (×2) and one final uploadCustomData carrying both trial rows:

{
  "type": "uploadCustomData",
  "token": "<token>",
  "data": {
    "data": [
      { "stateLog": "...", "avatar": "elder", "bridge": "safe" },
      { "stateLog": "...", "avatar": "young", "bridge": "danger" }
    ]
  },
  "eID": "<eID>",
  "sID": "<sID>"
}

If you see the uploadCustomData line, sending is fine. Red logs with Unauthorized or NotFound mean the request failed — see the troubleshooting section.

Step 6 — Confirm the uploaded data on the Web Console

Open the Web Console

Sign in at luida.cluster.mu/experiments and open the detail page for the experiment you registered.

Scroll down to the Answers section

Scroll to the Answers section at the bottom of the page.

Check the saved answer / data

Two kinds of records should be there:

• The regular questionnaire — two new rows, one VEQ submission per trial.
• Custom Log — two new rows, one per trial, each with avatar and bridge fields.

Participant Info won't gain a new row in Editor Play. That section only populates when a real participant joins on the published Cluster world.

If both records are there, Hello LUIDA is a success. Well done.

Common issues

"The questionnaire never appears."

• Confirm the VEQ template was added for this experiment (Step 2).
• Verify the scene's Hierarchy has a LUIDA-QuestionnaireByState > Trial - Rest GameObject.
• Scan the Unity Console for errors during Play.

"The Console shows an Unauthorized (401) error."

• Open LUIDA → Configure experiment identifiers and click Refresh Token & Endpoint ID to re-sync.

"The Console shows a NotFound (404) error."

• The Experiment ID is wrong. Compare what's in Configure experiment identifiers to the eID on the Web Console.

"The Configure experiment identifiers window still shows the login screen after I clicked Login."

• Re-issue the access token at cluster.mu/account/tokens and paste it again. The Unity Console will log the underlying error.

"I see the data in the Unity Console but not on the Web Console."

• The Web Console may be filtering by date or test-mode. If uploadCustomData lines are present with no error logs but rows still don't appear, contact the LUIDA team.

What's next

You've watched the data flow end-to-end. Time to actually build.

• Tutorial 2 — Proteus Effect (with LUIDA automation) (~75 min): your first hands-on build. Constructs a bridge-choice study on LUIDA's variables, state machine, and state-listening items.

By the end of the tutorial, your scene will behave the way the ProteusSample.unity sample did.

If something didn't work and you're stuck: revisit Setup, then email luida@cluster.mu with what you tried.