Skip to main content

User

Response_User_MouseCursor_Show.png Show Mouse Cursor

 

image.png

The Show Mouse Cursor node explicitly controls the visibility and functionality of the user's mouse pointer within the VR Viewer. When activated, the node checks the boolean Enable input for the specified User. Setting it to True displays the cursor on-screen, allowing the user to freely move it and click to interact with objects utilizing Node Triggered events. It is important to note that while this cursor mode is active, standard navigation is suspended—the user cannot walk or rotate their camera view until the node is activated again with the Enable input set to False, which hides the cursor and restores normal movement.

The Show Mouse Cursor mode is used for desktop/PC version of VR Viewer

Enable Gamepad Navigation

Turns gamepad navigation on or off for a user, so they can move through the scene with a game controller.

What it does

When you switch this on, the chosen user can use a connected gamepad to navigate the scene. Switch it off and gamepad navigation is turned off again for that user. You decide whether this applies just to the host or to everyone in the session.

The node only changes the gamepad setting for the user you pick — it doesn’t affect anything else about the scene. It also passes the same user and the on/off value straight through, so you can carry on with more steps right after it.

Inputs

Port Type What to connect Execute Trigger Wire this from the previous node’s Execute output. User User Choose which participant this applies to: Host Only or All Users. You can also wire in a specific user from an earlier node. Enable True / false Set this to true to turn gamepad navigation on, or false to turn it off.

Outputs

Port Type What you get Execute Trigger Fires once the node has finished. User User The same user, passed along so you can chain more user steps after this one. Enable True / false The same on/off value you set, passed along for any later steps that need it.

Example

User input All Users Enable input true User output The same user, ready for the next step Enable output true

Tips

    Use the same node with Enable set to false later in your scene to turn gamepad navigation back off when it’s no longer needed.

    Start QR Detection

    Turns on QR code scanning for a participant so the scene can react when they point their view or device at a QR code.

    What it does

    When this node fires, the chosen participant starts looking for QR codes. From that moment on, whenever they aim at a QR code it can be picked up and used elsewhere in your scene. You can also choose whether an on-screen scanning panel appears to guide them, or whether detection happens quietly in the background.

    This only switches scanning on — it doesn’t change the participant or the scene in any other way. The same participant is passed straight back out so you can connect more participant-related nodes after it.

    Inputs

    Port Type What to connect Execute Trigger Wire this from the previous node’s Execute output. User User Choose who starts scanning: Host Only (just the main user) or All Users (everyone in the session). You can also wire in a participant from an earlier node. Show UI? True / false Set to true to show the on-screen scanning panel that guides the participant, or false to scan quietly in the background. Defaults to true.

    Outputs

    Port Type What you get Execute Trigger Fires once the node has finished. User User The same participant you chose, passed along so you can connect more participant nodes after this one.

    Example

    User input Host Only Show UI? input true User output The same participant, ready to pass on to the next node

    Tips

      Set Show UI? to false when you want scanning to feel seamless — for example, automatically recognizing a code the participant walks up to without a panel popping up. This node only starts scanning. Use a matching stop node when you want the participant to stop looking for QR codes.

      Stop QR Detection

      Turns off QR code scanning for a participant, so the app stops looking for QR codes through their headset or device camera.

      What it does

      When you start QR detection, the chosen participant’s view keeps watching for QR codes in the real world around them. This node switches that watching back off. Once it runs, the app no longer scans for QR codes for that person, which is handy after they’ve scanned the code you needed, or when a part of your scene that relied on scanning is finished.

      You pick who it applies to with the User input — just the host, or everyone. It only stops the scanning; it doesn’t undo anything that was already detected, and it has no effect if scanning wasn’t running for that participant. The same participant is passed straight through the User output, so you can carry on with more steps for that person.

      Inputs

      Port Type What to connect Execute Trigger Wire this from the previous node’s Execute output. User User Choose who this applies to: Host Only (the default) or All Users. You can also wire in a participant passed along from an earlier user node.

      Outputs

      Port Type What you get Execute Trigger Fires once the node has finished, so you can continue to the next step. User User The same participant you chose, passed along so you can chain more user nodes after this one.

      Example

      User input Host Only User output The same participant, ready for the next user node

      Tips

        Pair this with Start QR Detection: switch scanning on when you need a code read, then switch it off here once you’re done. Make sure the User choice matches the one you used to start scanning — if you started it for All Users, stop it for All Users too.