Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| arvr [2025/02/13 07:02] – Ronell Sicat | arvr [2026/04/29 06:47] (current) – Ronell Sicat | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== AR/VR Tools User Guides ====== | ====== AR/VR Tools User Guides ====== | ||
| - | The KAUST Visualization Core Lab (KVL) provides augmented reality (AR) and virtual reality (VR) hardware, software, and technical support. KVL provides a wide variety of AR/VR devices as well as high-end Windows workstations for AR/VR development. KVL also provides access and support for AR/VR software such as Avizo, Unity, | + | The KAUST Visualization Core Lab (KVL) provides augmented reality (AR) and virtual reality (VR) hardware, software, and technical support. KVL provides a wide variety of AR/VR devices as well as high-end Windows workstations for AR/VR development. KVL also provides access and support for AR/VR software such as Avizo, Unity, GetReal3D, and our own KVL Viewer and KVL Digital Twin Platform. In some cases, KVL also provides development support and collaboration for special projects. [[help@vis.kaust.edu.sa|Contact us]] or [[https:// |
| ===== AR/VR Hardware ===== | ===== AR/VR Hardware ===== | ||
| - | Users who wish to quickly access an AR/VR workstation can book our [[facility_user_guides# | + | Users who wish to quickly access an AR/VR workstation |
| - | | + | * [[https:// |
| - | | + | |
| * [[https:// | * [[https:// | ||
| * [[https:// | * [[https:// | ||
| Line 15: | Line 14: | ||
| * [[https:// | * [[https:// | ||
| * [[https:// | * [[https:// | ||
| + | * [[https:// | ||
| ===== AR/VR Software ===== | ===== AR/VR Software ===== | ||
| Line 22: | Line 22: | ||
| ==== Avizo ==== | ==== Avizo ==== | ||
| - | The easiest way to bring your data to VR is by using [[vistools# | + | The easiest way to bring your data to VR is by using [[vistools# |
| ==== Unity ==== | ==== Unity ==== | ||
| - | Users can also develop their own AR/VR application using the [[https:// | + | Users can also develop their own AR/VR application using the [[https:// |
| ==== GetReal3D for Unity ==== | ==== GetReal3D for Unity ==== | ||
| Line 66: | Line 66: | ||
| ===== Example Projects ===== | ===== Example Projects ===== | ||
| - | Below are example projects that we developed in the past: | + | Below are example |
| * [[highlights: | * [[highlights: | ||
| Line 72: | Line 72: | ||
| * [[highlights: | * [[highlights: | ||
| * [[highlights: | * [[highlights: | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | <!--- | ||
| - | ==== SimLab Composer ==== | ||
| - | |||
| - | [[https:// | ||
| - | |||
| - | ---> | ||
| - | |||
| - | {{tag> | ||
| - | |||
| - | <!--- | ||
| - | |||
| - | ===== Vive VR Development Guide ===== | ||
| - | The Kaust Visualization Core Laboratory now provides its users with access to the HTC Vive HMD VR system. | ||
| - | |||
| - | The general workflow is that a new user will first apply for and obtain access to the facility. | ||
| - | |||
| - | KVL offers training in Unity development for VR. Please keep an eye out for upcoming opportunities to join a class. | ||
| - | |||
| - | === Getting Started === | ||
| - | |||
| - | Firstly, users will require **access** to the facilities where the VIVEs are available. | ||
| - | |||
| - | All users will require their KAUST **credentials** to log into the VIVE systems. | ||
| - | |||
| - | Users require a **free Unity account**. | ||
| - | |||
| - | Users also must sign up for a **free Steam account**. | ||
| - | |||
| - | Now, **log into the KVL Vive system** using your active directory credentials. | ||
| - | |||
| - | **Launch Steam** and enter your **Steam credentials**: | ||
| - | |||
| - | {{: | ||
| - | |||
| - | **Launch Steam VR** by clicking on the VR icon in the upper right-hand corner of the Steam window. | ||
| - | |||
| - | {{: | ||
| - | |||
| - | **Confirm the Vive is ready for use** by looking at the SteamVR window(s) at the bottom of the windows desktop: | ||
| - | |||
| - | {{: | ||
| - | |||
| - | A green “Ready” indicates that the Vive is connected and ready for use. A red “Not Ready” indicates a problem with the system. | ||
| - | |||
| - | In the event of a technical problem, you may follow the troubleshooting feature. | ||
| - | |||
| - | **Launch Unity** | ||
| - | |||
| - | Prepare your Unity scene to work with VR and the HTC Vive (these details are beyond the scope of this training document) | ||
| - | |||
| - | For reference, you may open the KVL Vive Demo scene, which contains all of the basic elements required for Vive display through Unity. | ||
| - | |||
| - | === Resources for HTC Vive Developers (Unity) === | ||
| - | |||
| - | Unity Main Site: http:// | ||
| - | Unity Community Answers: http:// | ||
| - | SteamVR: http:// | ||
| - | |||
| - | === Important Reminders for Users: === | ||
| - | |||
| - | Please remember to **CHARGE THE VIVE REMOTES** by plugging them in when you finish your work. | ||
| - | |||
| - | Always LOG OUT when finished. | ||
| - | |||
| - | === Development Notes === | ||
| - | |||
| - | If you use git-based version control for your project, the following is a useful git-ignore setting to use: https:// | ||
| - | |||
| - | ---> | ||