Open Source Mac VR Development Software - Page 2

BLUI is an ongoing research project in user interface design for virtual reality environments. BLUI was developed by the Arctic Region Supercomputing Center at the University of Alaska- Fairbanks.

Crimild Engine is an open source scene graph based engine which purpose is to fulfil the high-performance requirements of typical multi-platform two and tridimensional multimedia projects, like games, simulations and virtual reality.

A project for my thesis at Nanjing University designed for processing distributed vision computing. Also it provides the features for virtual reality, including scene construction, editing on animation objects and cameras, and sampling video on them.

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).

HyperInteractiveReality[hir] is virtual reality evolved. HiR is a system that allows anyone to do anything. HiR is the interactive representation of ideas via sound, graphics and immersive worlds. A power toolbox for artists and scientists alike. -- more to come soonly!

MOF-VR is a virtual reality program developed for Microsoft Windows and HTC Vive that allows for hypothetical metal-organic frameworks (MOFs) to be constructed and tested in molecular dynamics simulations of guest molecules.

The Mercury messaging toolkit is a new way to handle cross-component communication in the Unity game engine. It integrates seamlessly with the Unity Editor, and is both robust and expandable. It has been tested in Unity 2020 up until 2020.3.21f1, Unity 2019 up until 2019.2.17f1, Unity 2018 up until 2018.3.13f1, Unity 2017 up until 2017.4f1, and 5.6. The toolkit contains the Mercury messaging framework, which is a messaging and organizational framework built around the Mercury Protocol. Unity organizes its rendered scene objects (known in Unity as GameObjects) using a standard scene graph (known in Unity as the Scene Hierarchy). While Unity is very powerful, it is fairly difficult to achieve nonspatial communication between scriptable components of GameObjects (in Unity, known as MonoBehaviours).

NatML allows developers to integrate machine learning into their Unity applications in under five lines of code with zero infrastructure. NatML completely removes the need to have any experience with machine learning in order to take advantage of the features it can provide. NatML takes advantage of hardware machine learning accelerators, like CoreML on iOS and macOS, NNAPI on Android, and DirectML on Windows. As a result, it is multiple times faster than Unity's own Barracuda engine. NatML exposes machine learning models with simple classes that return familiar data types. These are called "Predictors", and they handle all of the heavy lifting for you. No need to write pre-processing scripts or shaders, wrangle tensors, or anything of that sort. NatML supports Android, iOS, macOS, and Windows alike. As a result, you can build your app once, test it in the Editor, and deploy it to the device all in one seamless workflow.

Collection of Open Source based tools and API that facilitate rapid application development for Games and Virtual Reality based applications.

OpenVRL - standas for Open Source Virtual Reality 'L' ('L' stands for Life or Library...). A full 3D virtual reality simulation library, with physics, collision detection, platform independand rendering, etc. Uses OpenDE and OPCODE libraries for dy

OpenReality will be a 3D Engine Library for development of Games, Virtual Reality and 3D Visualization applications. It will be very intuitive, and strongly object oriented. Of course, performance will have a great weight on the project´s decisions.

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.

A toolkit for developing virtual reality applications. Built in C++, over OpenGL, it is object oriented and offers the use of a scene graph for object hierarchy. Also, it provides interfaces for using VR equipment such as tracking devices.

UE4-Plugin-OffAxis plugin provides a fishtank-VR via a so-called OffAxisProjection by modifying the projection matrix using a custom ULocalPlayer. If your project is a C++ project, you are good to go. If you have a pure blueprint project, add a random C++ class via File -> Add C++ class (empty class is fine). Copy the Plugin in your (you might need to create a Plugin folder in the directory where your project file is). Start (or restart) Unreal Engine. You might get a warning that the plugin needs to be rebuilt. That's normal. Drag the OffAxisActor in your scene. Set position of OffAxisActor to 0,0,0. In the OffAxisActor, place the child actors P_a, P_b, and P_c so that they correspond to the corners of your "virtual window". For some inputs, you might need to change the key if they are already in use in your project.

VRMoo can be summed up as such: Virtual Reality Object Oriented MUD. I intend VRMoo to be capable of simulating complex environments, allowing real time 3D interaction with these environments, and allowing real time 3D interaction with other users.

VRTK is a collection of useful, reusable solutions to common problems found when building for virtual reality. VRTK aims to help productivity by speeding up the creation process from prototyping ideas to building complete solutions. The passion behind VRTK is to try and enable as many people as possible to build for VR, from seasoned developers to complete beginners who have a wonderful idea in their head but are unsure of how to create it. VRTK aims to be easy to understand so the absolute beginner can feel comfortable turning their creative thoughts into experiences but it also has enough power and flexibility to allow developers to really build out their perfect solution with little friction and without constantly re-inventing the wheel. Virtual reality is a relatively new medium so no one really understands what truly works or what doesn't work in terms of solutions, so VRTK aims to bring a community of diverse people from all across the world together to work on solving this.

A collection of projects based on the Virtual Object System (VOS) platform. The goal of Interreality is to develop a free and open platform for multiuser 3D virtual reality and interactive, collaborative 3D virtual spaces, as well as other applications.

VRS is an environment for presenting three dimensional (3D) world. All visualisations are made at client(s) side VRC (Virtual Reality Client - example client is under developement, SF site avaible, see also http://jvrc.info).

VRT is a Virtual Reality Toolkit. It is planned to be OS-independent, easy-to-use, full-feature VR platform. It integrates 3D engine, physical engine and AI engine.

Vive Stereo Rendering Toolkit provides drag-and-drop components for developers to create stereoscopic rendering effects in a few minutes. With this toolkit, effects such as mirrors or portal doors can be easily achieved in your VR application. Vive or other SteamVR-compatible HMDs, no need to modify. Vive Focus, add WaveVR from "WaveVR/Prefabs" to the scenes; remember to expand the camera rig. Oculus Rift, add OVRCameraRig from "OVR/Prefabs" to the scenes.

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.

Build virtual reality experiences with A-Frame and React. A-Frame is a web framework for building virtual reality experiences. Since A-Frame is built on top of the DOM, web libraries such as React, Vue.js, Angular, Ember.js, d3.js are able to sit cleanly on top of A-Frame. I recommend using vanilla A-Frame and aframe-state-component with static templating over aframe-react. React wastes a lot of cycles and incurs a lot of memory garbage. aframe-react is often abused where it is too easy to place 3D/real-time logic at the React layer, causing poor performance (e.g., doing React renders on ticks). aframe-react applications frequently ignore the prescribed ECS framework of A-Frame. Internally, React does tons of computation to compute what changed, and flushes it to the entire application. It is apparent React ecosystem does not care much about memory as most examples allocate functions and objects in the render method, and where immutables are popular.

Configurable, device-independent virtual reality engine built on top of OpenSceneGraph.

Virtual Reality Modeling Language

Platform Independent Virtual Reality Client and Server. Come to http://www.vrspace.org/ for more information and demo.