April 30, 2020
Moving all drivers and the compositor to the service process brings many advantages to the previous in-process model. For this input and rendering needed to be sent over our new IPC infrastructure. With a separate render loop, now independent of the OpenXR client, the compositor can provide a constant frame rate, even when the application doesn't deliver frames on time. This is required and the foundation of future reprojection work, where old frames can be transformed with new tracking data for a smoother experience if the client lags behind. In addition, the obvious advantage of an out of process compositor is that the compositor can be started asynchronously to the application and run on its own without any application. This is also required for running multiple clients in the future and for implementing OpenXR extensions like XR_EXTX_overlay.
Amongst other small improvements to the compositor we improved support for direct mode on NVIDIA by recognizing more display identifiers like the Valve Index and the Oculus Rift series of HMDs.
Furthermore we improved the compositor's performance, which has a boost of up to 2x the received frame rate in certain conditions under GPU load. A small benchmark using Blender's OpenXR functionality can be seen here.
We would very much like to thank Pluto VR for sponsoring this work.
This latest release is the first to contain development work accomplished amid the lockdown measures. Despite these significant changes,…
Coding hss begun for this year's Google Summer of Code (GSoC) projects, announced earlier last month. The 2020 edition selected 1,199 students…
With the excellent (online) edition of Augmented World Expo 2020 in full swing this week, what better time to announce version 0.2 of the…