website

Showing posts with label AR. Show all posts
Showing posts with label AR. Show all posts

Tuesday, 22 November 2016

Guest blog: Is Microsoft Hololens really a ‘Mixed Reality’ Device?



Over the past 5 years, consumers have had a lot of new terms to grapple with. ‘virtual reality’, ‘spherical video’, ‘cinematic VR’, ‘volumetric video’, ‘augmented reality’, ‘mixed reality’, ‘blended reality’ and I’ve even heard the name ‘transmogrified reality’ floating around. With so much debate among industry professionals over the true meaning of these terms, how on earth can we expect the general public to understand the differences?


Whilst these terms are typically coined in academic papers, technical terms are often bastardised by companies in an effort to carve out their own identity and differentiate themselves from competition. And this is understandable.

Most of us can recall the less-than-complimentary term for people wearing Google Glass. In the adverts for Glass, Google introduced consumers to ‘augmented reality’, a technology which would revolutionise every aspect of our experience. However in reality, Google Glass never lived up to expectations and the term ‘augmented reality’ suffered from stigma as a result.

Two years later, when the Microsoft Hololens announced their head mounted display, they needed a new term to differentiate their new product from Google Glass. They did this in two ways. Firstly, Microsoft revived the popular concept of ‘holograms’ for the type of content it displays.

Note that this bears little relation to the technical definition of holograms, where a three-dimensional image formed by the interference of light beams from a laser. For anybody interested in a deeper dive, VR developer & academic Oliver Kreylos has a great post on his blog about the differences between holograms & what the Hololens creates.


The second way Microsoft distanced themselves from Google Glass was by bringing another term into the public lexicon - ‘mixed reality’. Microsoft use this term to describe an overlay of synthetic content on the real world that is anchored to and interacts with the real world. However, the term ‘Mixed Reality’ was actually coined in 1994 by researcher Paul Milgram in an academic paper, which described MR as part of the ‘virtuality continuum’.


Whilst the concept of the ‘virtuality continuum’ can be hard to grapple with, broadly speaking, the ‘virtuality continuum’ describes AR & VR as being on a sliding scale, rather than as discrete, binary terms. On one side of the continuum, you have good old-fashioned reality. On the opposite end of the spectrum, you have full, immersive virtual reality. Along the continuum from reality to VR, there is also ‘augmented reality’ and ‘augmented virtuality’. For a better idea of the differences between the components in the ‘virtuality continuum’, creative technologist Vincent McCurley created this wonderful gif that illustrates the virtuality continuum perfectly:


From looking at Vincent’s gif, anybody who has tried the Hololens would say that actually, Hololens content most closely resembles ‘augmented reality’. However, by describing the Hololens as a mixed reality device, Microsoft seeds the idea that their device is capable of displaying any content along the virtuality continuum.

Dispute only arises when people treat terms like AR, VR or MR as absolute terms. By nature of being a ‘mixed reality’ headset, the Hololens is both an ‘augmented reality’ headset as well an ‘augmented virtuality’ headset. Anybody trying to assert that the Hololens is one or the other, hasn’t understood the definition of what a mixed reality headset is.

Thankfully, whichever term the public adopt will ultimately be driven by the product which most resonates with consumers. Industry ‘gurus’ will argue ad nauseum whether the widely popular ‘Pokemon Go’ is or is not ‘true’ augmented reality. However as far as consumers are concerned, if you can see a Pikachu on your camera feed, it’s AR. This is in stark contrast to Snapchat, one of the most popular mobile augmented reality apps, which doesn’t mention the terms AR or MR anywhere.

It’s clear that over the next decade, we are going to see a dramatic increase in augmented and virtual reality innovations, in both hardware and software. At Scape, we’re working on localisation technology that allows regular mobile devices to recognise exactly where they are for city-scale augmented reality. My hope is that as the AR market matures, innovations will be judged by their merits and not obfuscated by buzz-words and hyperbole.

Edward Miller

Edward will be speaking at Develop VR on Thursday 1st December, 2016.

Thursday, 15 September 2016

Guest Blog: Developing for VR - Lessons from the Leaders

In this article I’ve interviewed seven leading VR/AR developers to better understand their motivations, challenges, and hopes for the future of the platform. I’ve summarised their answers below.

The people interviewed were:
Patrick O’Luanaigh of nDreams (VR only)
James Marsden of Futurlab (traditional and VR games)
Martin de Ronde of Force Field (VR/AR)
Dave Ranyard - independent VR developer (VR only)
Jason Kingsley of Rebellion (traditional and VR games)
Sam Watts of Tammeka Games (VR only)
Mark Knowles-Lee of Fracture Games (AR only)

Q1. What motivates you to develop for VR?
New challenges - the unknown.
New experiences – possible through new interactions.
Innovation – new possibilities for creativity.
New opportunities - cutting through the noise of other games.

Q2. How do you decide which platforms to target?
Target them all. Many of the studios stated that they’re device agnostic.
Target platforms with unique differentiators. i.e. if a specific device has a differentiating feature, how can you make best use of that.
Go where the audience is. E.g nDreams only develop for devices which they think will sell over one million units.)
The game concept dictates the platform.
Make use of existing partnerships. E.g Futurelab have a fruitful relationship with Sony so it was natural for them to begin working on PlayStation VR.


Q3. What are the specific development issues you face?
People’s variation in sensitivity makes it difficult to design for. Several studios comment about always needing ‘fresh’ players who have not yet built up a tolerance to VR.
Risk. Studios commented that they weren’t sure how big the market will be for some platforms. E.g. Sony have a huge advantage in this area due to its large install base and lower cost of the VR headset.
The lack of a VR IDE. In particular judgements made on scale, lighting and legibility makes development a clunky iterative process (guess, build, test).
Difficulty in accessing hardware.
Need to prototype even the smallest feature. Some things you think will work just don’t. Don’t assume anything or rely on your past experience.

Q4. How do you design for VR?
Test everything – assume nothing.
Comfort is king so be prepared to throw things away - if a feature reduces player comfort for any reason, it has to go.
Change your thinking. Whereas in traditional game dev you want to turn everything up to 11, be more reserved for VR.
Is your experience unique to VR? Could your game only exist in VR? If not, then perhaps it’s not really a VR game, but rather a VR ‘version’ of a traditional game.


Q5. How do you evaluate the VR experience?
User test with as many people as possible due to player variation.
Aim for player comfort first, then emotion.
Is it compelling? The experience should be unlike anything else players have experience before.
Get platform owner feedback.

Q6. What are the key lessons you’ve learned so far?
Player comfort is king. A variety of issues emerged from the studios, however above all is player comfort and making sure your tech and design choices are in line with delivering it.
Experiment. Some things you think will work don’t, and some things which shouldn’t work do.
Technical aspects underlying VR are hugely important. It doesn’t matter how great your game idea is, no one will enjoy it if the tech can’t support it.
Poor design leads to motion sickness, not just frustration.

Q7. What kinds of new games / genres / interactions does VR allow?
It may be go beyond games, into experiences
A greater range of input, such as whole body interaction.
Increased presence - the potential for a greater social experience than ever before.
Design specifically for VR. Don’t ‘port’ your game from the traditional screen into VR.

Q8. Do you have any concerns?
Health and safety.
Market adoption.
Business models.
‘Bad’ VR games may put many people off. There are already some awful VR experiences out there getting high profile exposure, and these may put people off for a long time.


Q9. Will VR be a Success?
VR will be a success.  Our experts are  certain that VR will be a success, however that may take longer to happen than expected.
VR will not replace ‘traditional’ games, it’s just another way to experience them.
AR is likely to eclipse VR for non-entertainment applications.

Summary - Developing for VR Top Lessons Learned
Bear in mind that I only spoke to studios who had already invested in VR development, so this is not a representative sample of developers. So, taking the most popular responses from these developers, here’s the top lessons learned:
Player comfort is key.
Test your assumptions.
There is an opportunity here, but it is a risk.
Is your game unique and compelling for VR?
VR will not replace traditional games, it’s an alternative.
VR will be a success, but it might take some time.

Graham McAllister, Director, Player Research
Graham is the Director of Player Research, an award-winning games user research and playtesting studio based in Brighton, UK.