This website relies solely on user submissions.
Reviews, speculations, how-tos; anything to share?
Follow us:
#vronlinux @Freenode
Steam Group

To comment or submit articles, register and login.

Report: OpenXR Spec In-Progress; New Nvidia Vulkan Driver

Posted by Norbert, 4 weeks and 2 hours agoMon, 27 Feb 2017, 16:55 (2 comments)
The Khronos Group has announced OpenXR, an open standard for VR and AR applications and devices. Their OpenXR Working Group is creating this open and royalty-free standard to combat (API) fragmentation.

The Khronos GroupIn short, fragmentation slows the adoption of VR/AR devices, generates unnecessary work for developers and limits the ability of new and innovative devices to gain popularity.

The OpenXR standard comes in two parts: an Application Interface ("write code once that will run everywhere") and a Device Layer ("allows VR/AR runtimes to interface with various devices").

(continues after the image)


In related news, there's Vulkan 1.0.42. Mentioned in their Vulkan at GDC 2017 PDF document, and it introduces new extensions. As GamingOnLinux writes: "We know Khronos will be at GDC, so it's likely some of the Vulkan talks will mention these new extensions for VR use."

These new extensions have already made it into Nvidia's beta Vulkan driver 375.27.12. It's unclear to me if this means we can/should now move from 375.27.10 to 375.27.12. The SteamVR-for-Linux GitHub page still says 375.27.10.

Also, Valve's Joe Ludwig talks about OpenXR in a Voices of VR podcast interview. I haven't listened to it yet, but that should be interesting. Voices of VR writes: "Given that it was first announced in December 2016, then I'd expect that we might be seeing a 1.0 specification for OpenXR sometime in the first half of 2018."
Debian Website Steam Twitter Youtube
anchor Comment by Seegras, 3 weeks and 6 hours agoMon, 6 Mar 2017, 13:20
Apparently we can use 375.27.13
Mint Steam
anchor Comment by Norbert, 2 weeks and 3 days agoFri, 10 Mar 2017, 16:33
SeegrasApparently we can use 375.27.13

Careful though, that didn't work for me.
To comment, register and login.