Raevenlord
News Editor
- Joined
- Aug 12, 2016
- Messages
- 3,755 (1.25/day)
- Location
- Portugal
| System Name | The Ryzening |
|---|---|
| Processor | AMD Ryzen 9 5900X |
| Motherboard | MSI X570 MAG TOMAHAWK |
| Cooling | Lian Li Galahad 360mm AIO |
| Memory | 32 GB G.Skill Trident Z F4-3733 (4x 8 GB) |
| Video Card(s) | Gigabyte RTX 3070 Ti |
| Storage | Boot: Transcend MTE220S 2TB, Kintson A2000 1TB, Seagate Firewolf Pro 14 TB |
| Display(s) | Acer Nitro VG270UP (1440p 144 Hz IPS) |
| Case | Lian Li O11DX Dynamic White |
| Audio Device(s) | iFi Audio Zen DAC |
| Power Supply | Seasonic Focus+ 750 W |
| Mouse | Cooler Master Masterkeys Lite L |
| Keyboard | Cooler Master Masterkeys Lite L |
| Software | Windows 10 x64 |
After putting in work in the OpenGL, WebGL, and most recently, Vulkan APIs, the technology industry consortium Khronos Group is setting its sights on the VR industry and ecosystems. Their aim: to create a "cross-vendor, royalty-free, open standard" for the VR development community. This move is an effort to prevent the VR system from fragmenting itself towards an eventual collapse, considering the multiple engines to create content, platforms to sell that content through, and a few different hardware options with casuistically different requirements and tool-sets. As a result, for a developer to support SteamVR (OpenVR), Oculus (OVR), and OSVR, it has a lot of work to do, since each platform (with its unique runtime) interfaces with the game engine in a different way. Developers must account for the intricacies of each platform during the development process.
Khronos Group's solution: to create a standard API that interfaces with all hardware APIs and takes the extra work out of the equation for developers. It looks like the implementation of a high-level API, in essence - a common programming interface that allows developers to basically "ignore" vendor and device-specifics, potentially trading higher performance for simplicity of programming. Instead of fully programming for three different platforms - such as SteamVR (OpenVR), Oculus (OVR), and OSVR - with an assortment of different game-engines and hardware specifications, developers will instead be able to use a single API that scales through all of those, with the bulk of the work being done by the API itself. This is an apparent step-back from where the industry is going, lower level and closer-to-the-metal, at least on usual graphics workloads - as Mantle, DX 12 and Vulkan attest. In reality, it might give the VR platform the glue that keeps it all a coherent whole.
Khronos said that the new standard would include "APIs for tracking of headsets, controllers, and other objects, and for easily integrating devices into a VR runtime." The Khronos Group already has a variety of key players in the VR industry onboard with the initiative - almost all the big household names are working on VR products are already involved, such as Oculus, Valve, Google, Razer, Sensics, AMD, Nvidia, ARM, Intel, Tobii, and more. Conspicuously absent are the likes of VR-Ready smartphone makers, which may - or may not - join the initiative in time. Also absent is Qualcomm itself - the company that powers most of the world's smartphones, and which already has in place a Snapdragon VR820 reference platform.
Though still in a "initial exploratory phase", and yet trying to "define the standard's scope and key objectives", this is indeed an initiative with merit, and which would pay to come to fruition - though considering Khronos Group's track record in delivering standards, it might take a while for it to materialize.
View at TechPowerUp Main Site
Khronos Group's solution: to create a standard API that interfaces with all hardware APIs and takes the extra work out of the equation for developers. It looks like the implementation of a high-level API, in essence - a common programming interface that allows developers to basically "ignore" vendor and device-specifics, potentially trading higher performance for simplicity of programming. Instead of fully programming for three different platforms - such as SteamVR (OpenVR), Oculus (OVR), and OSVR - with an assortment of different game-engines and hardware specifications, developers will instead be able to use a single API that scales through all of those, with the bulk of the work being done by the API itself. This is an apparent step-back from where the industry is going, lower level and closer-to-the-metal, at least on usual graphics workloads - as Mantle, DX 12 and Vulkan attest. In reality, it might give the VR platform the glue that keeps it all a coherent whole.
Khronos said that the new standard would include "APIs for tracking of headsets, controllers, and other objects, and for easily integrating devices into a VR runtime." The Khronos Group already has a variety of key players in the VR industry onboard with the initiative - almost all the big household names are working on VR products are already involved, such as Oculus, Valve, Google, Razer, Sensics, AMD, Nvidia, ARM, Intel, Tobii, and more. Conspicuously absent are the likes of VR-Ready smartphone makers, which may - or may not - join the initiative in time. Also absent is Qualcomm itself - the company that powers most of the world's smartphones, and which already has in place a Snapdragon VR820 reference platform.
Though still in a "initial exploratory phase", and yet trying to "define the standard's scope and key objectives", this is indeed an initiative with merit, and which would pay to come to fruition - though considering Khronos Group's track record in delivering standards, it might take a while for it to materialize.
View at TechPowerUp Main Site
