API

It’s no secret that at this early point in the lifecycle of VR that there are many different platforms, solutions and paths to choose from when it comes to content and standards for motion and control. Due to the range of APIs created for game engines and different VR solutions, such as Steam VR, Oculus, OSVR, Daydream etc., it can be difficult for developers to create one-application-fits-all software. As a result, their software typically ends up specializing for a particular VR solution over others. This can arguably limit industry growth at the expense of differentiation. The goal of the new Khronos VR Standards initiative, announced this week, is to create a set of standard APIs that portable VR applications and engines can use to interface...