Smile Connect VR Support

Smile Connect VR

User Manual

Version 1.0  |  June 2026

ProductSmile Connect VR
EngineUnreal Engine 5.6.1
Target HardwareMeta Quest 3 / 3S / Pro — Windows 
Document Version1.0
Release DateJune 2026
ClassificationConfidential — Authorized Users Only
1Introduction

Welcome to the Smile Connect VR Platform

The SOLOXR’s Smile Connect VR Platform is a high-fidelity virtual reality PC-VR training system built on Unreal Engine 5. It delivers photorealistic, interactive simulation environments across Meta Quest  headsets, Windows desktop clients. This manual covers everything you need to get started, navigate the platform, and make the most of every simulation session.

Document Scope

This manual is intended for three audiences:

  • End Users (Learners / Trainees) — operating the VR headset or desktop client, launching and completing simulations
  • Instructors / Facilitators — configuring scenarios, monitoring live sessions, and reviewing performance reports
  • IT Administrators — installing, deploying, and maintaining the platform infrastructure
i  Note Sections 2–4 cover hardware setup and first launch. Section 5 covers the simulation experience. Instructors should focus on Section 6. Admins should refer to Section 7.

Platform Architecture Overview

The Smile Connect VR platform consists of three integrated layers:

Instructor PanelThe PC-VR Part of the simulation that controls the simulation
The VR SimulationThe OCULUS part of the simulation
Data LayerThe Data Analytics  with automated grading, competency tracking, and reporting
2System Requirements

Meta Quest

Supported DevicesMeta Quest 3, Meta Quest 3S, Meta Quest Pro
OS VersionMeta Horizon OS 62 or later
StorageMinimum 4 GB free application storage
NetworkWi-Fi 6 (802.11ax), minimum 25 Mbps dedicated bandwidth
MDMMeta for Work enrollment required for enterprise/institution deployments
BatteryFully charged before each session; USB-C charging supported during use

Windows Desktop Client

Operating SystemWindows 11 (64-bit)
ProcessorIntel Core i7 / AMD Ryzen 7 (8th Gen or later)
RAMMinimum 16 GB (32 GB recommended for multi-patient scenarios)
GPUNVIDIA RTX 2070 / AMD RX 6700 XT or better (Windows)
Storage10 GB free disk space (SSD recommended)
Display1920 x 1080 minimum; 4K recommended for desktop observation mode
Network50 Mbps broadband; <50 ms latency to nearest cloud region
CAUTION: Do not attempt to run the VR simulation on devices below the minimum specifications. Degraded hardware can cause simulation lag, which may compromise training fidelity and trigger motion discomfort.
3Installation & First Launch

Installing the Smile Connect VR Application

Step 1: Laptop / Desktop (Institution-Managed Devices)

Your IT administrator will install the application into the assigned Laptop / Desktop and make the necessary setting ( Installing the Meta Horizon Link ) and test the cable connection to the Oculus (Recommended using a USB 3 for best performance )

Step 2: Installing the Smile Connect VR Application

  1. Power on your Meta Quest headset and put it on.
  2. Activate the Meta Link Cable Connection
TIP  Quick Launch Tip Pin the SOLOXR app to your Quest home screen for faster access. Press the Meta button > App Library > Long-press SOLOXR > Add to Home.

Windows Desktop Client

  • Download the installer from your institution’s portal or from the SOLOXR Client download link provided by your program administrator.
  • Windows: Run SOLOXRSetup.exe and follow the installation wizard. macOS: Open the .dmg file and drag SOLOXR to your Applications folder.
  • On first launch, click Sign In and authenticate using your institution’s Single Sign-On (SSO) credentials.
  • The application will download the latest scenario library (~1.2 GB) on first startup.
4Hardware Controls & Navigation

Meta Quest Controller Layout

The SOLOXR platform uses standard Meta Quest Touch controllers. The following table maps each control to its in-simulation function.

InputControllerFunction
Trigger (Index Finger)LeftGrab object, interact with UI elements, confirm selections
Grip (Middle Finger)Left / RightHold / carry objects (equipment, instruments)
ThumbstickLeftLocomotion — smooth walk in the direction pressed
ThumbstickRightSnap turn (45° increments) or smooth turn (configurable)
A ButtonRightConfirm / select highlighted menu item
B ButtonRightReset your position in the scenario
X ButtonLeftOpen AI patient interaction (verbal input mode)
Y ButtonLeftToggle scenario information / hint panel
Menu Button (≡)LeftOpen main menu / settings / exit session
Meta ButtonRightReturn to Quest home screen (exits simulation)
Ctrl + QEnd and submit simulation session
5Running a Simulation

Launching a Scenario

  • Log in and navigate to your Dashboard. Assigned scenarios appear under My Simulations.
  • Select a scenario card to view its details: clinical domain, estimated duration, difficulty level, and learning objectives.
  • Press Launch Simulation. The application will load the 3D clinical environment (15–30 seconds on Quest).
  • A brief orientation screen will appear. Review the scenario context and patient information before proceeding.
  • Press Begin when you are ready. The AI simulation clock starts, and the patient scenario goes live.

The Simulation Interface

Status Bar (top)Elapsed time, patient vitals strip, and current scenario objective
Patient AvatarAI-driven standardized patient — speak naturally to interact (Quest/desktop mic)
Equipment TrayAvailable clinical tools appear to the left — grab with controller trigger or click
Hint Panel (Y / Tab)Contextual guidance without revealing optimal decision paths
Decision NodesHighlighted interaction points appear as glowing outlines — approach to activate
Vital Signs MonitorWall-mounted monitor updates in real time based on your clinical decisions

Interacting with the AI Patient

The AI standardized patient responds to natural spoken language. You do not need to follow a script.

  • Hold the X button (Quest) or press F (desktop) to activate the microphone.
  • Speak your clinical question, instruction, or assessment naturally — for example: “Can you describe the pain for me?” or “I am going to take your blood pressure.”
  • The AI will respond in real time with contextually appropriate dialogue, facial expressions, and physiological changes.
  • Patient responses and your spoken input are logged with timestamps for debriefing review.
TIP  Communication Best Practices Speak at a natural, conversational pace. Shouting or whispering may affect recognition accuracy. Use clinical terminology you would use in a real patient encounter — the AI is trained on nursing scope-of-practice language. If the patient does not respond, press X / F again to re-activate the microphone.

Completing a Simulation

  1. Work through all required decision nodes until the scenario objective is fulfilled or the session timer ends.
  2. A scenario end screen will appear displaying your overall performance grade and a summary of key actions.
  3. Press Submit Session to finalize your results and send data to the LMS.
  4. Your AI-generated Debrief Report will be available in My Results within 60 seconds of submission.
Do not close the application or power off the headset before submitting your session. Unsubmitted sessions cannot be recovered and will not count toward your grade.
6Instructor Panel

Accessing the Admin Panel

The Admin Panel can be accessed by pressing on the Admin panel link on the bottom right of the Instructor Panel :

Enter the Admin Key :  “ Teeth

Student Login

Search the student by entering the first letter of the student name

Scenario Management

Assigning Scenarios to Students

  1. Navigate to Courses > [Your Course] > Assignments.
  2. Click Add Assignment and select one or more scenarios from the clinical library.
  3. Configure the due date, allowed attempts, and time limit.
  4. Under Student Access, select the student roster or cohort. Click Publish.
  5. Students will see the assigned scenario on their dashboard at next login.

Scenario Builder

Use the drag-and-drop Scenario Builder to create or customize clinical scenarios without programming knowledge:

  • Add patient conditions, vital sign curves, and physiological parameters.
  • Configure branching decision trees — define correct, acceptable, and incorrect action paths.
  • Set AI patient dialogue scripts or use open-ended AI response mode.
  • Map rubric items to specific observable student actions within the simulation.

Live Session Monitoring

During a live simulation, the Moderation Dashboard provides real-time visibility into active student sessions:

Student View3D bird’s-eye view of the student’s position and movements in the clinical environment
Decision HistoryTimestamped log of every action, interaction, and spoken input
Vital Sign TrendsLive patient vital sign graph updated in real time
Scenario InjectionRemotely trigger new clinical events (e.g., sudden deterioration, new orders)
End SessionRemotely end a student session and trigger automatic grading

Grading & Reporting

Grading is fully automated based on the rubric configured in each scenario. After a session ends:

  • Results appear in the Grade Book within 60 seconds.
  • Each rubric item shows a Pass / Partial / Fail status with an evidence citation (timestamped action that triggered the score).
  • Click any student’s name to view their full AI-generated Debrief Report.
  • Export individual or cohort results as CSV or PDF from Reports > Export.
NOTE  AACN Competency Reporting All rubric items are pre-mapped to the eight AACN Essentials domains. Navigate to Reports > Accreditation to generate CCNE-ready competency reports across any date range or cohort. Longitudinal reports spanning multiple academic years are available for senior students approaching graduation.
7IT Administration

SSO & LMS Integration

Identity ProviderSAML 2.0 and OAuth 2.0 — compatible with Microsoft Azure AD, Shibboleth, Okta
LMS IntegrationLTI 1.3 with automatic grade passback — Blackboard, Canvas, Brightspace, Moodle
Roster SyncAutomatic via LTI 1.3 course enrollment; manual CSV import also supported
SSO Config GuideProvided by SOLOXR Implementation Lead during onboarding

Network Requirements

  • Wi-Fi Standard: 802.11ax (Wi-Fi 6) recommended; 802.11ac (Wi-Fi 5) minimum.
  • Bandwidth: 25 Mbps dedicated per concurrent VR headset in standalone mode; 50 Mbps per desktop client.
  • Ports: Outbound TCP 443 (HTTPS/TLS 1.3), UDP 3478 and 3480 (WebRTC voice), UDP 9000–9100 (XR streaming).
  • Firewall Allowlist: *.soloxr.com, *.azure.com (Microsoft Azure CDN), *.oculus.com, *.meta.com.
  • QoS: Tag SOLOXR traffic with DSCP EF (46) for voice/video prioritization.

Data Security & Compliance

Encryption in TransitTLS 1.3 — all API calls, asset delivery, and LMS sync
Encryption at RestAES-256 — all student records in Microsoft Azure (US data centers)
AuthenticationMFA + RBAC — role-based access control enforced at platform level
FERPA ComplianceStudent data treated as protected education records; SOLOXR operates as school official
HIPAABAA available upon request; HIPAA-aligned administrative and technical safeguards in place
Data RetentionStudent simulation records retained for minimum 7 years
SOC 2 Type IIAnnual audit report available to institutions under NDA
Breach Notification24-hour SLA for notification following confirmed breach event

MDM Headset Fleet Management

For institutions deploying 10 or more Quest headsets, Meta for Work MDM is strongly recommended:

  • Enroll devices at manage.oculus.com/v2/work using your organization credentials.
  • Push the SOLOXR app silently to all enrolled headsets from the App Management panel.
  • Configure Wi-Fi profiles, kiosk mode, and auto-update policies to eliminate per-device setup.
  • Set up device naming conventions (e.g., KSU-SON-001) for easy identification in the SOLOXR admin panel.
8Troubleshooting

Common Issues & Resolutions

IssueLikely CauseResolution
Cannot log in / SSO redirect failsInstitution SSO misconfiguration or account not provisionedContact your IT help desk to verify your account is active in the identity provider.
Simulation loads to black screenInsufficient GPU / VRAM or corrupted installRestart the application. If persists, uninstall and reinstall. Verify GPU meets minimum specs.
AI patient not responding to voiceMicrophone not activated or background noiseHold X (Quest) or press F (desktop). Check microphone permissions in system settings.
Choppy movement / low frame rateInsufficient bandwidth or device overheatingMove closer to the Wi-Fi access point. Remove headset for 5 minutes to allow cooling.
Grades not appearing in LMSLTI passback delay or misconfigurationWait 5 minutes and refresh your LMS course. If missing, contact your instructor or IT admin.
Headset boundary / Guardian lostRoom lighting too low or guardian reset neededIn headset: Meta button > Guardian > Redraw boundary in a well-lit area.
SSO session expired mid-simulationSession token timeout (default 8 hours)Press B (Quest) or Escape (desktop) to open the menu. Re-authenticate; session data is preserved.
Application not updatingMDM policy blocking auto-update or storage fullConfirm device has >2 GB free storage. Contact IT admin to push update via MDM.

Contacting Support

Priority 1 — Critical (Platform down / active session blocked)Phone: Dedicated 24/7 priority line Response SLA: 15 minutes
Priority 2 — High (Feature impaired, no workaround)Email / Live Chat Response SLA: 2 hours
Priority 3 — Normal (Non-critical issue or question)Email / Help Center Response SLA: 8 business hours
Self-Service ResourcesHelp Center: help.soloxr.com Video Tutorials: Available in the Faculty & Student portals
Account Manager (Faculty / Admin)Named account manager assigned from contract execution Available Mon–Fri, 8:00 AM–6:00 PM Eastern
iPriority 1 (Critical) incidents are defined as platform outages affecting active student simulations or a faculty-scheduled academic session. SOLOXR commits to restoring service or providing a documented workaround within four (4) hours.
9Glossary
TermDefinition
AI Standardized PatientAn AI-driven virtual patient avatar that responds to natural language input and adapts its dialogue and physiology based on student decisions.
AACN EssentialsThe American Association of Colleges of Nursing core competency framework used for nursing education accreditation.
Branching ScenarioA simulation structure where student decisions dynamically alter the course of the scenario (patient condition, available options).
CCNECommission on Collegiate Nursing Education — the nursing program accreditation body.
Debrief ReportAn AI-generated post-simulation report containing timestamped action logs, rubric scores, and individualized learning recommendations.
FERPAFamily Educational Rights and Privacy Act — U.S. federal law protecting student education records.
LMSLearning Management System — the cloud platform managing course delivery, roster sync, grading, and reporting.
LTI 1.3Learning Tools Interoperability 1.3 — the standard protocol for integrating SOLOXR with institutional LMS platforms.
MDMMobile Device Management — enterprise software used to enroll, configure, and manage Meta Quest headsets at scale.
NCLEX NGNNCLEX Next Generation — updated nursing licensure exam format emphasizing clinical judgment, reflected in SOLOXR simulation-based prep content.
SAML 2.0Security Assertion Markup Language 2.0 — the SSO protocol used to authenticate users via their institutional identity provider.
SSOSingle Sign-On — authentication method allowing users to log in with their institution credentials without a separate platform password.
Unreal Engine 5Epic Games’ real-time 3D rendering engine powering the SOLOXR simulation graphics, physics, and environment fidelity.
WebXRA browser-based API allowing VR/AR experiences to run natively in a web browser without additional plugins.
xAPI (Tin Can API)A learning data specification used to record granular learner activity and export simulation data to external LRS systems.

SOLOXR CORP  |  1040 Wild Cherry Lane, Wellington, FL 33414  |  info@soloxr.com  |  www.soloxr.com

Copyright © 2026 SOLOXR CORP. All rights reserved. This document is confidential and intended solely for authorized institutional users.