A-Frame 1.1.0 - AR, Quest 2 Support, hand tracking, compositor layers, immersive navigation
A-Frame 1.1.0 is out! Core functionality is more polished and robust than ever. Full support for WebXR AR module (https://github.com/immersive-web/webxr-ar-module) and initial and experimental integration for upcoming and exciting WebXR APIs like immersive navigation (https://github.com/immersive-web/navigation), hand tracking (https://www.w3.org/TR/webxr-hand-input-1/), compositor layers (https://www.w3.org/TR/2020/WD-webxrlayers-1-20201203/) or hit tests (https://immersive-web.github.io/hit-test/)
This week also marks A-Frame’s fifth birthday. Five years ago, on December, 2015, we released the first version of A-Frame to make it easier for anyone to build VR experiences. What started as a little personal project is today a community of hundreds of thousands of developers worldwide.
More than 40 A-Framers helped to get 1.1.0 across the finish line. 20 of those made their first contribution. We appreciate help from everybody and newcomers are always especially celebrated. A-Frame is only as strong as its community.
We also thank Google and Oculus WebXR teams. They made an outstanding effort in a tough year. They kept the Immersive Web standard moving forward with new APIs while delivering new implementations in Chrome and the Oculus browsers.
Read the release notes and changelog (https://github.com/aframevr/aframe/releases/tag/v1.1.0) to check all the new features and celebrate everyone that made it happen.
Consider supporting A-Frame development by buying a gorgeous t-shirt (https://cottonbureau.com/p/SX82KC/shirt/a-frame-og#/9479538/tee-men-standard-tee-vintage-black-tri-blend-s)
Happy immersive Christmas! 🎄
- Reference: https://aframe.io/blog/aframe-v1.1.0/
Write a comment