People have come to associate plugins with 3D interactive content on the web. But with the arrival of HTML5 and the death of Flash, the standard is set – content must be delivered without plugins, so that it will be available to any and all web-enabled devices.
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.
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.
So you’re a web developer, and you’ve been hearing things about VR. I’m also a web developer, and I’ve also been hearing things about VR! And I’ve been blogging about it. Not just VR – but how VR is very likely to soon become both a crisis and an opportunity for web developers. So what are the prospects for VR for web developers?
Today is April 8, 2016. The Oculus Rift and the HTC Vive both tried to start shipping in the last couple of weeks – and it’s been a bit of a mess. But even so, eager early adopters have raved up and down that this revolutionary technology finally actually works.
As a sequel to my Feb 23 post X3DOM vs. Three.js, I’d like to quickly compare Blend4web vs. Three.js, using that same old arbitrary VRML file as a neutral sample. Blend4web is an add-on for Blender, the open-source 3D authoring tool I use.
Here’s how the Blender workspace containing my old VRML file looks when I export it using Blend4web:
And here’s the same Blender workspace exported as a COLLADA file and then imported into Three.js:
You can drag your mouse on either of those to move them around. Each button gives you a different motion when you drag. Each example uses each button in a different way.
idoru.js is an experiment I’m working on with artificial characters in virtual worlds. The idea is that to provide good “user experience” (UX) in a virtual world, a character must have good “stage presence” to stimulate engagement.
The idea is to create a framework for an artificial character that is charming and attentive to the user. This character can then be “dressed up” with any imaginable avatar. It can be given any “job” that anyone cares to script.
A good suit and deep knowledge are not enough to make a person engaging in the real world. A person needs body language. A person needs to be attentive to the person they are engaging. They need to make eye contact. They need to interact with a person’s personal space in a thoughtful, polite way.