A consultation on using the extension XR_META_foveation_eye_tracked

[Hope10086]

I was wondering if [XR_META_foveation_eye_tracked](url:https://registry.khronos.org/OpenXR/specs/1.0/html/xrspec.html#XR_META_foveation_eye_tracked) would be able to export foveation_center for use in the application without actually running foveation render.

### Background:
My team 's research content is the video coding and decoding in cloud VR scenarios. So the rendering is done by the server 's GPU(NVIDIA 3060), and then the texture content of each frame is video encoded and sent to the client. Similar to the principle of foveation rendering technology, we will preprocess the texture image before video coding (or adopt different quantization parameters for different macroblocks in the rate control step of video coding) to achieve less data volume. This is not the same as foveation renderingin the traditional sense. So we need to use extension :XR_META_foveation_eye_tracked to get the foveation center, but we don't need the Meat Quest Pro‘s ’ GPU to render the texture image.

### Description:
I have read the extensions: XR_META_foveation_eye_tracked, XR_FB_foveation_configuration and XR_FB_foveation in the openxr documentation. We all konw XR_META_foveation_eye_tracked depends on XR_FB_foveation and XR_FB_foveation_configuration .So in my client code, could I declare and configure XR_FB_foveation and XR_FB_foveation_configuration but not call them actualy, only the foveation center of XR_META_foveation_eye_tracked is used.

[rpavlik-bot]

An issue (number 1962) has been filed to correspond to this issue in the internal Khronos GitLab (Khronos members only: KHR:openxr/openxr#1962 ), to facilitate working group processes.

This GitHub issue will continue to be the main site of discussion.