Probably in the next OpenXR specification

There still doesn't seem to be any documentation for this. Getting frame timing data is essential for doing things like dynamic resolution scaling.

Originally posted by Rectus:

Getting frame timing data is essential for doing things like dynamic resolution scaling.

XR_EXT_frame_composition_report is still being worked on, but it is explicitly not intended to be used for real time feedback for driving application dynamic resolution scaling. Instead, it is more for generating reports for tools like Nvidia's FCAT.

I would encourage you to start a discussion on the Khronos forums to start gathering requirements for dynamic resolution scaling, etc.:
https://community.khronos.org/c/openxr/25

Thanks! I'll do that.

Originally posted by aaron.leiby:

Originally posted by Rectus:

Getting frame timing data is essential for doing things like dynamic resolution scaling.

XR_EXT_frame_composition_report is still being worked on, but it is explicitly not intended to be used for real time feedback for driving application dynamic resolution scaling. Instead, it is more for generating reports for tools like Nvidia's FCAT.

I would encourage you to start a discussion on the Khronos forums to start gathering requirements for dynamic resolution scaling, etc.:
https://community.khronos.org/c/openxr/25

There are now two meta extensions that seem usable for dynamic resolution:

https://registry.khronos.org/OpenXR/specs/1.0/html/xrspec.html#XR_META_performance_metrics
https://registry.khronos.org/OpenXR/specs/1.0/html/xrspec.html#XR_META_recommended_layer_resolution

Can you guys implement these in steamvr? I previously used openvr's 'GetFrameTiming(..)
m_flTotalRenderGpuMs' to drive dynamic resolution and it worked well. XR_META_performance_metrics seems to have most of the same stats.