Open Source VR Development Software

The main feature of ApertusVR is the so called "Distributed Plugin-in Mechanism" which means that not only humans could be involved in a multi-user virtual reality scene but any element of the Internet of Things like hardware, software, robot or any kind of smart device. ApertusCore is a programming library written in C++11, that fulfills modern software requirements as it is modular, embeddable, platform-independent, and easily configurable. It contains basic software interfaces and modules for logging, event-handling, and for loading plugins and configurations. It is also responsible for distributed data synchronization. ApertusVR is a set of plugins that extend ApertusCore with XR (AR/VR/MR) capabilities, which help to integrate XR technologies into new/existing developments, products rapidly. It creates a new abstraction layer over the hardware vendors in order to use different display and control devices in any product or service.

This project enables developers to build XR experiences using the same code that runs on the web. Exokit engine is written on top of Node and emulates a web browser, providing native hooks for WebGL, WebXR, WebAudio, and other APIs used in immersive experiences. The future is immersive. The web is the best application platform. Javascript is the best ecosystem. It's not possible to do both 2D and 3D well. We don't do 2D. We can use an external 2D browser. Exokit empowers and connect apps, even (especially) if they aren't designed to cooperate. Apps should run in "reality tabs", layers of reality that blend together. Exokit is a Javascript Node.js module. C++ bindings hook into WebGL, WebXR, Magic Leap, Leap Motion, and various other device APIs. Exokit runs on Windows, macOS, Linux (x64), Linux (ARM64), and Magic Leap (ARM64).

Hover UI Kit is a tool for creating beautiful, customizable, dynamic user interfaces. All interface interactions utilize a simple and consistent mechanism, the "hover", which users can perform with any 3D input device. These interfaces are designed specifically for VR/AR applications, addressing the complex UX challenges of these immersive environments. Virtual reality (VR) or augmented reality (AR) applications must provide ways for users to interact -- to select items, to move them, to modify them, to trigger actions, to control their virtual world. The user experience (UX) can become increasingly complex as new features are introduced, leading to a long list of application-specific interactions that can conflict with each other and can be difficult for users to learn. Hover UI Kit is built to solve this problem. It is a tool for creating beautiful, customizable, dynamic user interfaces.

RealityUI is a collection of user interface classes for RealityKit. The classes included in RealityUI aim to offer familiar User Interface guidelines, but in a 3D setting for Augmented and Virtual Reality through RealityKit. The User Interface controls in this repository so far are made to be familiar to what people are used to with 2D interfaces, however the plan is to expand the tools on offer to new and unique controls, which are more appropriate for an Augmented Reality and Virtual Reality context. RUISwitch is a 3D toggle switch with an on and off state. Default bounding box is 2x1x1m. RUIStepper is used to increment or decrement a value. Default bounding box is 2x1x0.25m. An interactive track to represent an interpolated value. Default bounding box is 10x1x1m including thumb. RUIButton is used to initiate a specified action. The action here will only trigger if the gesture begins on a button, and also ends on the same button.

This project aims to develop an interaction framework based on body detection by webcams, identifying the skeleton shape (hands, arms, head, legs etc), for games, virtual reality, augmented reality and other applications.

Use the WebXR Device API today, providing fallbacks to native WebVR 1.1 and Cardboard. A JavaScript implementation of the WebXR Device API, as well as the WebXR Gamepad Module. This polyfill allows developers to write against the latest specification, providing support when run on browsers that implement the WebVR 1.1 spec, or on mobile devices with no WebVR/WebXR support at all. The polyfill reflects the stable version of the API which has shipped in multiple browsers. If you are writing code against the WebVR 1.1 spec, use webvr-polyfill, which supports browsers with the 1.0 spec, or no implementation at all. It is recommended to write your code targeting the WebXR Device API spec however and use this polyfill as browsers begin to implement the latest changes. The minimal input controls currently supported by WebXR is polyfilled here as well, using the Gamepad API.