Open Source JavaScript VR Development Software for Linux

A-Frame is an open source web framework for building virtual reality experiences. With A-Frame you can create WebVR with HTML and entity-component works on Vive, Rift, Daydream and more. A-Frame simplifies virtual reality by handling the required 3D and WebVR boilerplate to get you running on platforms like mobile, desktop, Vive, and Rift. Because it can be used from HTML, just about everyone can use it. A-Frame is a thin yet powerful framework on top of three.js. While A-Frame is completely accessible from HTML, developers can also make full use of JavaScript, DOM APIs, three.js, WebVR, and WebGL.

A visual inspector tool for A-Frame scenes. Just hit <ctrl> + <alt> + i on any A-Frame scene to open up the Inspector. Get a different view of the scene and see the visual effect of tweaking entities. The VR analog to the browser’s DOM inspector. Can be opened on any A-Frame scene with <ctrl> + <alt> + i. Record and replay headset and controller pose and events. Hit record, move around inside the VR headset, interact with objects with the controller. Then replay that recording back on any computer for rapid development and testing. Reduce the amount of time going in and out of the headset. The A-Frame Inspector is a visual tool for inspecting and tweaking scenes. The Inspector is similar to the browser’s DOM inspector but tailored for 3D and A-Frame. Not only can we open our local scenes inside the Inspector, we can open any A-Frame scene in the wild using the Inspector (as long as the author has not explicitly disabled it).

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

JanusXR re-imagines webpages as collaborative 3D web spaces interconnected by portals. JanusXR turns any webpage into its own three-dimensional space where users can meet and explore with others. Host content on the open web and customize Janus' open-source multiplayer server to fit your needs. VESTA is JanusXR's user-driven community. Post your own spaces and get feedback from other community members! The built-in editor allows users to join together to create content in real-time. JanusWeb's widget generator allows you to embed a 3D WebVR portal to your webspace into any 2D webpage. With the JanusXR Youtube translator, watching videos with friends is a walk in the park. Oculus Rift, Vive, GearVR, Daydream, and Cardboard support via WebVR API. Realtime collaboration across all devices via built-in networking. There are several different ways to use JanusWeb, depending on how much control you want to have over the whole system.

WebVR math platform made with A-Frame, Three.js, React, Redux. MathworldVR uses Redux for all the stuff around the app's state. It helps you write applications that behave consistently. On top of that, it provides a great developer experience, such as live code editing combined with a time-traveling debugger. For example, CalcButton component used as a backspace on the calculator is dispatching Redux action when user "clicks it" with VR hand-controller!

Multi-user VR on the Web. A framework for writing multi-user VR apps in HTML and JS. Built on top of A-Frame. Follow the NAF Getting Started tutorial to build your own example from scratch, including setting up a local server. Networked-Aframe works by syncing entities and their components to connected users. To connect to a room you need to add the networked-scene component to the a-scene element. For an entity to be synced, add the networked component to it. By default the position and rotation components are synced, but if you want to sync other components or child components you need to define a schema. For more advanced control over the network messages see the sections on Broadcasting Custom Messages and Options. Create an instance of a template to be synced across clients. The position and rotation will be synced by default. The buffered-interpolation is added to allow for less network updates while keeping smooth motion.

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

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.

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