How VR’s Next Generation Shows Key Signs of a Maturing Market

How VR’s Next Generation Shows Key Signs of a Maturing Market

66
0
SHARE

VR feels like it’s simultaneously moving fast and slow. It’s been two years and four months since the leading PC VR headsets, the Oculus Rift and HTC Vive, hit shelves. The leading high-end headset overall, PSVR, has only been around for one year and nine months. That’s a significant amount of time for individual products, but just a blip in the context of the formation of a brand new ecosystem and medium. Looking forward to the next generation of VR, advancements in specs and experience are not the only improvement; the industry as a whole is becoming more cohesive, which will ultimately benefit everyone involved. Here’s how.

OpenXR API Standard

OpenXR is an in-development standard that’s open and royalty free. It’s being developed by a consortium consisting of effectively every major player in the VR market, including chip makers, headset makers, game engines, publishers, and VR app stores. The standard is being developed under the Khronos Group, the organization behind a number of major graphics standards like OpenGL, WebGL, and Vulkan.

Public supporters of OpenXR. | Image courtesy Khronos Group

OpenXR aims to foster greater interoperability between major pieces of the VR ecosystem: apps, game engines, and headsets. The goal is to make it easier to ‘write once and run anywhere’, meaning reducing the redundancy and complexity for an app, game engine, or headset to support the multitude of options available on the market.

The OpenXR project is building an ‘Application Interface’, which sits between VR apps and content platforms, and a ‘Device Layer’, which sits between the content platforms and individual VR headsets and devices. The idea is that the Application Interface and the Device Layer should be standardized so that everyone can design against a common target rather than needing to maintain individual support for many different platforms and devices.

OpenXR is a broadly supported initiative to create an industry standard method of interfacing between VR headsets and software. | Images courtesy Khronos Group

Hypothetically this means that a game supporting OpenXR that launches tomorrow could work with an OpenXR-supported headset that launches in five years, since both were built targeting the same Application Interface and Device Layer. Similarly, a OpenXR headset from one company could work with OpenXR controllers from another company, letting users use various devices together more easily.

Similarly, if a new game engine wanted to offer support for VR, it needs only to target the OpenXR Application Interface to potentially work with every headset and VR platform that supports OpenXR.

.IRPP_kangoo , .IRPP_kangoo .postImageUrl , .IRPP_kangoo .imgUrl , .IRPP_kangoo .centered-text-area { min-height: 100px; position: relative; } .IRPP_kangoo , .IRPP_kangoo:hover , .IRPP_kangoo:visited , .IRPP_kangoo:active { border:0!important; } .IRPP_kangoo { display: block; transition: background-color 250ms; webkit-transition: background-color 250ms; width: 100%; opacity: 1; transition: opacity 250ms; webkit-transition: opacity 250ms; background-color: #eaeaea; box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -moz-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -o-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); -webkit-box-shadow: 0 1px 2px rgba(0, 0, 0, 0.17); } .IRPP_kangoo:active , .IRPP_kangoo:hover { opacity: 1; transition: opacity 250ms; webkit-transition: opacity 250ms; background-color: #e6e6e6; } .IRPP_kangoo .postImageUrl , .IRPP_kangoo .imgUrl { background-position: center; background-size: cover; float: left; margin: 0; padding: 0; } .IRPP_kangoo .postImageUrl { width: 30%; } .IRPP_kangoo .imgUrl { width: 100%; } .IRPP_kangoo .centered-text-area { float: right; width: 70%; padding:0; margin:0; } .IRPP_kangoo .centered-text { display: table; height: 100px; left: 0; top: 0; padding:0; margin:0; } .IRPP_kangoo .IRPP_kangoo-content { display: table-cell; margin: 0; padding: 0 10px 0 10px; position: relative; vertical-align: middle; width: 100%; } .IRPP_kangoo .ctaText { border-bottom: 0 solid #fff; color: #1ABC9C; font-size: 13px; font-weight: bold; letter-spacing: .125em; margin: 0; padding: 0; text-decoration: underline; } .IRPP_kangoo .postTitle { color: #34495E; font-size: 16px; font-weight: 600; margin: 0; padding: 0; } .IRPP_kangoo .ctaButton { background-color: #e6e6e6; margin-left: 10px; position: absolute; right: 0; top: 0; } .IRPP_kangoo:hover .imgUrl { -webkit-transform: scale(1.2); -moz-transform: scale(1.2); -o-transform: scale(1.2); -ms-transform: scale(1.2); transform: scale(1.2); } .IRPP_kangoo .imgUrl { -webkit-transition: -webkit-transform 0.4s ease-in-out; -moz-transition: -moz-transform 0.4s ease-in-out; -o-transition: -o-transform 0.4s ease-in-out; -ms-transition: -ms-transform 0.4s ease-in-out; transition: transform 0.4s ease-in-out; } .IRPP_kangoo:after { content: “”; display: block; clear: both; }

SEE ALSO
Oculus Wants to “Go big” On Opening Their Platform to Third-party Headsets, When the Time is Right

This doesn’t necessarily mean that every VR platform that supports OpenXR will support every headset that supports OpenXR (for instance, the HTC Vive on the Oculus Store), but it does mean that the technical capability is in place if platform stakeholders want to move to an open device approach.

In total, this makes it easier for new players to jump into the VR market, whether that be with a game, a game engine, a content platform, or even a new headset or accessory. This benefits everyone in the market by creating more options for developers and customers, and fosters competition which leads to better products.

Image courtesy Khronos Group

In March this year, the OpenXR group announced its latest progress and did a deep dive into the technical scope of the OpenXR spec. While the group hasn’t announced an official release of the standard, the latest timeline shows that they are nearing an initial release,  which we expect could come by the end of the year.

VirtualLink Connection Standard

Public supporters of the VirtualLink project

Most major tethered headsets today require two or three plugs on the end of the cable which need to be connected to the host PC, and they differ from one headset to the next. The Rift, for instance, has one HDMI plug and one USB plug. The Vive has one DisplayPort plug, one USB plug, and a separate power plug that needs to connect to a wall outlet.VirtualLink, backed by most of the major players in the VR industry, is a newly announced connection standard that aims to simplify headset plugs into a single, well specified connector.

Based on USB-C, the VirtualLink connector offers four high-speed HBR3 DisplayPort lanes (which are “scalable for future needs”), a USB3.1 data channel for on-board cameras, and up to 27 watts of power. The standard is said to be “purpose-built for VR,” being optimized for latency and the needs of next-generation headsets.

The new connector will not only simplify the connection on the end of the headset’s cable, it will also make it easier for customers to understand if a given computer will support a certain headset, which eases the process of buying a VR Ready system.

Whereas today you might think your system meets all the specifications for a VR headset, only to find that your USB ports don’t actually support the speeds required for the headset, or you don’t have the right HDMI spec, the VirtualLink standard means that both customers and headset makers can count on the connector to support a well specified set of capabilities.

VirtualLink was just announced last month and is expected to debut with the next generation of GPUs and PC VR headsets; the former we could see by the end of the year.

Continued on Page 2

The post How VR’s Next Generation Shows Key Signs of a Maturing Market appeared first on Road to VR.

Source

NO COMMENTS