PTC v69 Quest Pro - pointers dissappear when launching eye tracking calibration.

[kyungho.won]

Dear community,

Hello. I am a researcher and am currently using Quest Pro with eye-tracking functionality.

I know using PTC is not a good idea when doing research, but I made a mistake.

It's been a week, and controllers and hand pointers (cursors) disappear when I select the "calibrate" button in the eye tracking menu. However, controllers are still connected, the selected button is highlighted, and the haptic is alive, so I am asking participants to find the "start" button somehow using haptic instead of invisible pointers.

It isn't very pleasant, as not all participants are familiar with Quest Pro.

I tried rebooting and factory resetting several times but still had the same issue.

Is hotfix planned, or is downgrading easy enough?

Thank you for your time reading my post.

Have a nice day!

[MetaQuestSupport]

Hi @kyungho.won , we understand that it could be very frustrating. We understand that you have done all the basic troubleshooting on your end. In order to get more precision on your issue, we would like to invite you to our private messages. Please select our name to get to our profile page, or click here: https://metaque.st/CommunitySupport. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.

Speak soon! 

[morfaine]

I have the exact same problem. I am also planning to use the headset for a research study.

Not being able to see the the pointers when trying to calibrate will make things too hard for participants.

Hopefully this gets fixed soon.

[kyungho.won]

I sent a private message to MetaQuest support above and got an answer that downgrading is not possible. 

I heard that PTC v71 is rolling out, so I hope it would resolve this issue even though I cannot see v71 yet.

[morfaine]

I never subscribed to the PTC. The issue we are talking about is in the full v69 release as well.

[kyungho.won]

That's too bad.. hopefully it will be resolved soon. So far participants are adapting invisible pointers, but definitely it's annoying that I have to explain this issue every time.