ISSUE DESCRIPTION
Description of the issue:
After enabling the quad views foveated rendering options, the high resolution area in the centre of the screen is in a fixed position and does not track eye movement. This is when using a Quest Pro with eye tracking enabled and the latest PTC v76 runtime which supports XR_EXT_eye_gaze_interaction. Eye tracking is confirmed working via several other eye tracking OpenXR applications.
Did you experience this issue before you joined the Beta?
No, this feature is new to SU2.
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes, removed and issue still occurs.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- Enable quad views setting under VR Graphics Settings.
2.Enter cockpit in VR.
3.View edges of FOV by moving eyes and observe lower resolution rendering. With eye tracking, this should remain at higher resolution.
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are currently plugged in, as well as your VR headset? Please name all of them as there could be a potential conflict.
Quest Pro via AirLink. No other peripherals.
[PC Only] Are you using Developer Mode or have you made any changes to it?
No.
[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
NVIDIA 4090
[PC Only] What other relevant PC specs can you share?
AMD 5800X3D
MEDIA
Please add a screenshot or video of the issue occurring.
[END OF FIRST USER REPORT]
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•