I’m not huge fan of sporting events. And I’m even less of a fan of the Olympics. But this year, the Olympics represents an important step forward in the mainstreaming of virtual reality.
As a Canadian, my national broadcaster is the CBC (Canadian Broadcasting Corporation). Right now, the CBC is proudly broadcasting select Olympic events in VR. And not just any VR – mobile VR. The flagship platform is Gear VR – but the broadcasts also work with Google Cardboard. And on mobile devices, and desktops.
Back in the days of Flash, I’d get to “model” snow a couple of times around Christmas every year. For some animated corporate Christmas cards, usually. So, when the time came to try out the WebVR Boilerplate – that’s what I chose for my first experiment. Gently falling snow.
(The above example is an iFrame – to pop it out for your VR goggles, click here)
The WebVR Boilerplate is a collection of files that does everything you need to do to get something in WebVR up and running, really easy. So that seems perfect for me! The base-state of the boilerplate shows just a rotating cube, in a room defined by a bright green grid. So all I did, to make this demo, was to remove the cube and start coding up the snow!
One of my hobbies is photography. So as I begin dabbling in VR, I find myself quite curious about 360 photos. A 360 photo is the “bare minimum” of a VR experience.
What is a 360 photo?
A 360 photo goes by many names, but each describes a photograph that completely surrounds the camera. It shows what is in front – in back – off to the sides – and above and below. ALL of it. You can look all around, and everywhere you look has been captured in the photo.
A lot has been made of the role of VR in the art of storytelling. Even more has been made of the role of storytelling in the fledgling art of VR. At first, I was fascinated by the idea. But the more I thought about it – the more I read about it – the more I started to wonder how many “interactive” concepts could be added to an idea that is 7/12 “telling”, without the very idea of “storytelling” bursting at the seams. The dead-end implications of “telling” anything to users with the capacity for full interaction weighed on me. So I came up with the term storysharing.
Lie down under a maple tree, and watch the keys lazily drift down towards you. In your VR goggles, with WebVR!
(This is in an iFrame – to pop it out for your VR goggles, click here)
I’d written a demo using THREE.js some time back, that simulated maple keys falling in the spring. Having secured some VR goggles (Samsung Gear VR with a Galaxy S7), and tried no end of VR experiences, it seemed like I should “port” that demo into an immersive version.
About a week ago, I got my first set of VR goggles. Nothing fancy – it’s the Samsung Gear VR. I explored some of the demos. (great fun!) Some of what I explored was WebVR, which just became available on Gear VR (without the use of “experimental browsers”) a couple of weeks ago – albeit with a “deprecated API”. (which means, an old obsolete version.) Then I took a crack at a tool called A-Frame.
A-Frame makes WebVR easy. Easy peasy. It reminds me of X3DOM – it’s a “declarative language”, so it drives a lot like HTML5. All of the things you declare when you’re using A-Frame get added to the “DOM” (Document Object Model), so everything in your “world” can be accessed and manipulated just like you would the elements on a plain, old-fashioned web page. Which, really, makes a lot of things easy. Easy peasy.
I don’t always try to get to the bottom of a new technology before there’s commercial demand for it. But when I do, it’s because the potential of a technology really stands out. And that’s the case with the dawn of WebVR.
I’d tried a bunch of the WebVR demos on my flat monitor. Yup, that provides a 3D experience like anything from VRML on. But the kick with WebVR is that your 3D stuff can get rendered either on a monitor, or in a VR headset.