Ratfink Posted April 16 Posted April 16 Hi All First time flying with QPro in a few weeks and noticed quad view eye tracking not working. Long story short, it seems Meta is the issue with a new update that breaks eye tracking using Link (USB in my case) https://communityforums.atmeta.com/t5/Get-Help/Latest-Meta-Update-Breaks-eye-tracking-and-avatars-for-QUEST-PRO/m-p/1311837#M363318 Rolling back to V74 could be a slolution according to the link above, but I'm happy to sit tight for a fix Anyone else having this issue? 1 CORSAIR 5000D AIRFLOW Mid Tower | AMD RYZEN 7 9800X3D | G.Skill Trident Z5 Neo EXPO RGB 64GB (2x32GB) DDR5 PC5-48000C30 6000MHz | ASUS ROG X870E-E GAMING WIFI | Gigabyte RTX5080 Gaming OC 16GB | 4TB Lexar NM790 M.2 PCIe 4.0 | Seasonic Prime TX-1000 1000W 80 Plus Titanium Modular Power Supply | Lian Li Galahad II Trinity AIO 360mm | Meta Quest Pro | TM HOTAS Warthog | Saitek Combat Rudder Pedals | Win 11 Home | Asus PG348Q 34" 3440x1440 Monitor | Bose Companion 3 2.1 Sound
mbucchia Posted April 17 Posted April 17 I've heard it from quite a few people yes. I wasn't banned, but this account is mostly inactive and not monitored.
Tensorial_Architect Posted April 17 Posted April 17 (edited) No, Zuckweasel decided it is a "new" feature. I don't have this problem myself but am attempting to reproduce. If I can, I will submit a fix to Meta here shortly. Give me a few days .... Edited April 17 by Tensorial_Architect I left this forum on April 30th, 2025 bc I didn't like being censured when I posted perfectly legitimate content. Best wishes fellas!
Sprite001 Posted April 17 Posted April 17 Had this problem with Quest Pro, v76. Eyetracking not working in DCS. I did a repair/reinstall of Meta Quest Link that seems to have fixed the problem for now.
Qcumber Posted April 17 Posted April 17 7 hours ago, Ratfink said: Hi All First time flying with QPro in a few weeks and noticed quad view eye tracking not working. Long story short, it seems Meta is the issue with a new update that breaks eye tracking using Link (USB in my case) https://communityforums.atmeta.com/t5/Get-Help/Latest-Meta-Update-Breaks-eye-tracking-and-avatars-for-QUEST-PRO/m-p/1311837#M363318 Rolling back to V74 could be a slolution according to the link above, but I'm happy to sit tight for a fix Anyone else having this issue? Thanks for the heads up. I'll avoid upgrading. 9800x3d; rtx5080 FE; 64Gb RAM 6000MHz; 2Tb NVME; Quest Pro (previous rift s and Pico 4).
Ratfink Posted April 17 Author Posted April 17 Rolling Quest Link back to V74 as per the link I included restores eye tracking I've turned off auto updates, and will stick to V74 until forced to upgrade CORSAIR 5000D AIRFLOW Mid Tower | AMD RYZEN 7 9800X3D | G.Skill Trident Z5 Neo EXPO RGB 64GB (2x32GB) DDR5 PC5-48000C30 6000MHz | ASUS ROG X870E-E GAMING WIFI | Gigabyte RTX5080 Gaming OC 16GB | 4TB Lexar NM790 M.2 PCIe 4.0 | Seasonic Prime TX-1000 1000W 80 Plus Titanium Modular Power Supply | Lian Li Galahad II Trinity AIO 360mm | Meta Quest Pro | TM HOTAS Warthog | Saitek Combat Rudder Pedals | Win 11 Home | Asus PG348Q 34" 3440x1440 Monitor | Bose Companion 3 2.1 Sound
Tensorial_Architect Posted April 20 Posted April 20 I was finally able to reproduce the problem. I submitted a fix to Meta on Wednesday night and they released an update earlier today (April 19th). This bug has now been fixed I believe. Check it and see. 1 I left this forum on April 30th, 2025 bc I didn't like being censured when I posted perfectly legitimate content. Best wishes fellas!
Qcumber Posted April 20 Posted April 20 6 minutes ago, Tensorial_Architect said: I was finally able to reproduce the problem. I submitted a fix to Meta on Wednesday night and they released an update earlier today (April 19th). This bug has now been fixed I believe. Check it and see. Is this the PTC version? I have been avoiding using PTC but might give it a go if it's working OK with the QP. 9800x3d; rtx5080 FE; 64Gb RAM 6000MHz; 2Tb NVME; Quest Pro (previous rift s and Pico 4).
Tensorial_Architect Posted April 20 Posted April 20 (edited) Nope, this is a regular update. Give it a shot Qcumber, ... don't like it, simply roll back. I fixed deir s h i t z before, ... I'm a known variable you might say. Edited April 20 by Tensorial_Architect 1 I left this forum on April 30th, 2025 bc I didn't like being censured when I posted perfectly legitimate content. Best wishes fellas!
Ratfink Posted April 21 Author Posted April 21 I upgraded the Qpro firmware to the latest V76 using the advice in this video and eye tracking restored - On 4/20/2025 at 9:15 AM, Tensorial_Architect said: I was finally able to reproduce the problem. I submitted a fix to Meta on Wednesday night and they released an update earlier today (April 19th). This bug has now been fixed I believe. Check it and see. Thanks for sorting that, I don't see the newer version available but using adb sideload to force V76 into the headset has fixed it for now CORSAIR 5000D AIRFLOW Mid Tower | AMD RYZEN 7 9800X3D | G.Skill Trident Z5 Neo EXPO RGB 64GB (2x32GB) DDR5 PC5-48000C30 6000MHz | ASUS ROG X870E-E GAMING WIFI | Gigabyte RTX5080 Gaming OC 16GB | 4TB Lexar NM790 M.2 PCIe 4.0 | Seasonic Prime TX-1000 1000W 80 Plus Titanium Modular Power Supply | Lian Li Galahad II Trinity AIO 360mm | Meta Quest Pro | TM HOTAS Warthog | Saitek Combat Rudder Pedals | Win 11 Home | Asus PG348Q 34" 3440x1440 Monitor | Bose Companion 3 2.1 Sound
Ratfink Posted April 21 Author Posted April 21 On 4/20/2025 at 9:27 AM, Tensorial_Architect said: Nope, this is a regular update. Give it a shot Qcumber, ... don't like it, simply roll back. I fixed deir s h i t z before, ... I'm a known variable you might say. I couldn't figure out how to stop it upgrading back to V76 after rolling back to V74 - do you know if there's a way to force it to stay at a certain version? CORSAIR 5000D AIRFLOW Mid Tower | AMD RYZEN 7 9800X3D | G.Skill Trident Z5 Neo EXPO RGB 64GB (2x32GB) DDR5 PC5-48000C30 6000MHz | ASUS ROG X870E-E GAMING WIFI | Gigabyte RTX5080 Gaming OC 16GB | 4TB Lexar NM790 M.2 PCIe 4.0 | Seasonic Prime TX-1000 1000W 80 Plus Titanium Modular Power Supply | Lian Li Galahad II Trinity AIO 360mm | Meta Quest Pro | TM HOTAS Warthog | Saitek Combat Rudder Pedals | Win 11 Home | Asus PG348Q 34" 3440x1440 Monitor | Bose Companion 3 2.1 Sound
Tensorial_Architect Posted April 21 Posted April 21 Yes, there is a way. Open your Meta Quest Link desktop software -> go to Settings (on the left side) -> go to the General tab (on the top) -> find the setting entitled "Automatic App Updates" and make sure it is turned off. Then your Version will remain rolled back. I left this forum on April 30th, 2025 bc I didn't like being censured when I posted perfectly legitimate content. Best wishes fellas!
skywalker22 Posted Sunday at 12:51 PM Posted Sunday at 12:51 PM Yesterday I tried to fly DCS in VR after some time off (on v74), and I couldn't start the Quest Link, it was not connected. I tried all kind of things to make it work, but unsuccessfully. I was focrce to install the latest v76 for Quest Link to work again!!! And now eye tracking in not working.
diamond26 Posted Sunday at 05:04 PM Posted Sunday at 05:04 PM (edited) Similarly my quest link crashed out of the blue and then after reinstalling I got v76 and eye tracking stopped working Luckily I have VD installed. Headset is still on v69 (switched off updates) Edited Sunday at 05:05 PM by diamond26 MAIN SYSTEM SPECS: MSI PRO Z690-A WIFI DDR4, Intel Corei7-12700K @ 5.0, 64Gb RAM Kingston KF3600C18D4/16GX, EVGA RTX 3080 FTW3 ULTRA GAMING 12GB, Samsung SSD 970 EVO Plus 1TB, Virpil T50CM3 Throttle, VKB Gunfighter MkIV Ultimate with 20cm extension, VKB T-Rudder MKIV, Quest Pro Laptop SPECS: Alienware X16 R2, Intel Core Ultra 9 185H, RTX 4090 mobile 16GB, 32GB LPDDR5X, 2TB Micron NVMe SOFTWARE: Microsoft Windows 11
Tensorial_Architect Posted Sunday at 07:00 PM Posted Sunday at 07:00 PM One thing to watch out for always if your eye-tracking goes down is the stupid Meta Horizon phone app. Don't ask me why, ... but when the Meta developers were creating the software environment for the Quest Pro, ... it is almost as if by design that they wished to make it as complex as possible, ... there are three places where settings must be adjusted, ... the Meta Horizon phone link, the Meta Quest Link desktop app, and the in-game "Cliff House." All three MUST be set correctly or you will lose eye-tracking. Every time that Meta updates their Meta Quest Link desktop app, ... you will need to go back to the silly Meta Horizon app on your phone and re-enable the developer option under "Devices" and turn on eye-tracking there as well. Occasionally, this step is not needed, ... but often, ... it is. This may be the source of your eye-tracking problems for some of you. I left this forum on April 30th, 2025 bc I didn't like being censured when I posted perfectly legitimate content. Best wishes fellas!
skywalker22 Posted Sunday at 07:50 PM Posted Sunday at 07:50 PM 48 minutes ago, Tensorial_Architect said: One thing to watch out for always if your eye-tracking goes down is the stupid Meta Horizon phone app. Don't ask me why, ... but when the Meta developers were creating the software environment for the Quest Pro, ... it is almost as if by design that they wished to make it as complex as possible, ... there are three places where settings must be adjusted, ... the Meta Horizon phone link, the Meta Quest Link desktop app, and the in-game "Cliff House." All three MUST be set correctly or you will lose eye-tracking. Every time that Meta updates their Meta Quest Link desktop app, ... you will need to go back to the silly Meta Horizon app on your phone and re-enable the developer option under "Devices" and turn on eye-tracking there as well. Occasionally, this step is not needed, ... but often, ... it is. This may be the source of your eye-tracking problems for some of you. Good point! But I can't connect headset to my android phone via bluetooth. It pairs, but it instantly disconnects as well. Any ideas how to overcome that?
Tensorial_Architect Posted Monday at 02:13 AM Posted Monday at 02:13 AM Uhh, ... Google search. (All right, ... just sh#$@ing you man. It is likely that you need to reboot your Quest Pro. Also, close the Meta Horizon app and then restart it. I've had this happen to me before. If the problem persists, check your NFC settings on your phone (NFC = near field communication).) I left this forum on April 30th, 2025 bc I didn't like being censured when I posted perfectly legitimate content. Best wishes fellas!
Picchio Posted Monday at 07:41 AM Posted Monday at 07:41 AM (edited) Eye tracking isn't working in DCS/Quad Views, but it is enabled and working in the headset. Mobile and Link apps are set correctly (same as before), Dev mode enabled, Eye tracking over Link enabled. QV log reports this error: No data received from the eye tracker in 60 seconds! Image quality may be degraded. This was discussed in Meta forums: https://communityforums.atmeta.com/t5/Get-Help/Meta-Quest-Link-app-version-76-0-0-452-315-has-stopped-eye/td-p/1313274 Still no solution, apparently. Edited Monday at 07:52 AM by Picchio
Tensorial_Architect Posted Monday at 08:09 AM Posted Monday at 08:09 AM That likely means you don't have your Open XR layers stacked correctly. Look up a tool called OpenXR-API-Layers-GUI and read about how to use it and then move Quad Views up or down as needed. DCS can't see Quad Views if you've got other Open XR layers blocking it. I left this forum on April 30th, 2025 bc I didn't like being censured when I posted perfectly legitimate content. Best wishes fellas!
Picchio Posted Monday at 08:43 AM Posted Monday at 08:43 AM 33 minutes ago, Tensorial_Architect said: That likely means you don't have your Open XR layers stacked correctly. Look up a tool called OpenXR-API-Layers-GUI and read about how to use it and then move Quad Views up or down as needed. DCS can't see Quad Views if you've got other Open XR layers blocking it. Definitely something users expect to have to do... Thanks for the tip, I'll give it a go if I have time.
Picchio Posted Monday at 08:56 AM Posted Monday at 08:56 AM (edited) Uhm, nothing out of the ordinary. Just to be clear, DCS can see Quad Views and it is correctly logged and I can see and modify the foveated region etc., it is the Eye Tracking feature that isn't working. Edited Monday at 09:01 AM by Picchio
diamond26 Posted Monday at 10:32 AM Posted Monday at 10:32 AM It's definitely an issue with META PC software as everything is enabled as before, Layers are correct but eye tracking is not working anymore with META Link in DCS. With exact same configuration in terms of layers in DCS, eye tracking works as always in VD. MAIN SYSTEM SPECS: MSI PRO Z690-A WIFI DDR4, Intel Corei7-12700K @ 5.0, 64Gb RAM Kingston KF3600C18D4/16GX, EVGA RTX 3080 FTW3 ULTRA GAMING 12GB, Samsung SSD 970 EVO Plus 1TB, Virpil T50CM3 Throttle, VKB Gunfighter MkIV Ultimate with 20cm extension, VKB T-Rudder MKIV, Quest Pro Laptop SPECS: Alienware X16 R2, Intel Core Ultra 9 185H, RTX 4090 mobile 16GB, 32GB LPDDR5X, 2TB Micron NVMe SOFTWARE: Microsoft Windows 11
markturner1960 Posted Monday at 10:47 AM Posted Monday at 10:47 AM 15 hours ago, Tensorial_Architect said: One thing to watch out for always if your eye-tracking goes down is the stupid Meta Horizon phone app. Don't ask me why, ... but when the Meta developers were creating the software environment for the Quest Pro, ... it is almost as if by design that they wished to make it as complex as possible, ... there are three places where settings must be adjusted, ... the Meta Horizon phone link, the Meta Quest Link desktop app, and the in-game "Cliff House." All three MUST be set correctly or you will lose eye-tracking. Every time that Meta updates their Meta Quest Link desktop app, ... you will need to go back to the silly Meta Horizon app on your phone and re-enable the developer option under "Devices" and turn on eye-tracking there as well. Occasionally, this step is not needed, ... but often, ... it is. This may be the source of your eye-tracking problems for some of you. So, out of interest I looked at this as I have a sneaky feeling my quad views is not working either after the update. I have literally NEVER looked at the meta app on my phone....so I just did, in devices I have the option to pair my headset, it does something then says look in my headset foir a code, nothing shows up there. Both devices are on the same network and bluetooth turned on.....so I am stuck here. I still have quad views and eye tracking enabled in DCS and the meta settings on my PC System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
Tensorial_Architect Posted Monday at 07:36 PM Posted Monday at 07:36 PM Check your Bluetooth and NFC settings on your phone and Quest Pro. Then try repairing. As I said, ... they tried, ... really hard, ... to make it absolutely as difficult as possible. I left this forum on April 30th, 2025 bc I didn't like being censured when I posted perfectly legitimate content. Best wishes fellas!
skywalker22 Posted Tuesday at 07:32 AM Posted Tuesday at 07:32 AM I tried everytihng, also with another phone, but nothing seems to work to connect headset to the phone via bluetooth. It pairs, also connects for a few seconds, but then it disconnects and stays disconnected!
Recommended Posts