I turned the public test channel on to download the beta update and it fixed the problem. it was the Oculus Link software causing the issue.
Hello tom.leylan . Thank you for the update. Yes, please send me the PS script. That would be most helpful.
Regarding the issue where your PC is no longer detected on the Quest headset and/or the requiring to pair the headset and PC again, I am thinking these are separate issues from the original report(Quest Link taking 5 minutes to launch).
Can you provide the following information below that would be most helpful.
Your detailed input will greatly assist us in reproducing and addressing the problems. Please use the following format when sharing your feedback (copy paste and fill out if possible):
Issue Reporting Template
Description:
Provide a detailed description of the issue you're experiencing.
Steps To Reproduce:
Be as specific as possible. The more detailed your steps, the easier it is for us to replicate the issue.
Observed Results:
Describe what you saw or what went wrong.
Expected Results:
Explain what you expected to happen instead.
Test Environment:
Include relevant information such as:
Additionally, please provide any relevant pictures and logs using our Horizon app, and log-gatherer tool under the diagnostics folders.
For more information on checking your software version, visit this link, and for collecting logs from your PC, refer to this guide.
Thank you for taking the time to help us improve Link. Your feedback is invaluable, and we look forward to hearing from you!
It can look on the surface to be a different situation but that is how software works. Bugs in software can manifest in various ways as conditional runtime statements execute depending upon a user's particular setup.
In any case I experimented with various solutions and found restarting the service to be the fastest way for me to solve it. Why this works is slightly less interesting to me, I'm just trying to meet up with friends online.
Here is what you should do. Determine how many employees work at Meta and how many use the Quest headset. Find out how many can use or do use Link.
Set up a series of test scenarios. You can have them start the headset, connect to Link and report their experiences. Then have them connect to Horizon World and then VRChat and possibly run a few VR games.
In each case have those employees report on what they experience. Can't find the menu option? Report it. See way too many ads for Horizon World? Report it. Jiggling visuals, non-connecting controllers, etc. Report it.
In the long run if these issues never get fixed it doesn't really impact me or your customers they will move on when an opportunity presents itself.
If the problems reported here were rare or unusual it might warrant a report from an end-user but if Meta employees can't bother to test a product that helps pay their salaries why would anyone want to spend a day writing up reports?
If you want to capture GPU, PC specs, etc. (even time of day) could be useful data then provide a repo and/or template that user can set this info once and edit every time they want to report yet another problem.
One of us works for a company generating billions of dollars annually... it isn't me.
