News for hackers. Stuff that matters.
Re:OpenXR – Cross-Platform, Portable, Virtual Reality by josh64 on Monday February 27, 2017 @04:27PM (#13748296)
Sony as well was refreshing to see.
Re:OpenXR – Cross-Platform, Portable, Virtual Reality by jsheard on Monday February 27, 2017 @05:04PM (#13748749)
It will be refreshing if they actually ship it. Vulkan slides circa 2015 showed Sony participating in that too, and they never ended up implementing it.

Page 13: https://www.khronos.org/assets/uploads/developers/library/ov...

Re:OpenXR – Cross-Platform, Portable, Virtual Reality by ktta on Monday February 27, 2017 @04:33PM (#13748357)
Yeah I think that'll make developers lives easier since games developed for the PS can be easily ported to other platforms.

I don't see microsoft anywhere, although I think they'll have to come around since everyone else is participating.

Re:OpenXR – Cross-Platform, Portable, Virtual Reality by mathw on Tuesday February 28, 2017 @05:51AM (#13752799)
Wouldn't be surprised if Microsoft are working on a VR layer for DirectX 13 to use on Windows and Xbox. Just like Vulkan/DirectX 12.
Re:OpenXR – Cross-Platform, Portable, Virtual Reality by shmerl on Monday February 27, 2017 @04:56PM (#13748652)
I wonder why they couldn't do the same thing for Vulkan.
Re:OpenXR – Cross-Platform, Portable, Virtual Reality by pjmlp on Tuesday February 28, 2017 @04:50AM (#13752564)
Something that might make you happy is that Khronos already understood that Vulkan alone won't cut it, so they are launching the "3D Portability Initiative".

https://www.khronos.org/3dportability

Lets see if anything will come out of this.

Re:OpenXR – Cross-Platform, Portable, Virtual Reality by shmerl on Tuesday February 28, 2017 @12:14PM (#13755348)
It sounds like a solution to a wrong problem. Why can't Vulkan / SPIR-V themselves be used for that purpose? Building another level of abstraction on top would just complicate things, and for the sole reason of appeasing lock-in jerks. I.e. while it might work, it's a pretty bad solution, engineering wise.

If anything, Vulkan needs simpler APIs abstraction, something higher level that uses common logic for stuff like memory management and etc. That's actually useful. And not spending time on this. But well, Khronos can do whatever they want of course.

And we'll need to wait and see if the above lock-in jerks will decide to participate this time.