(Meta quest link isn't working) !Needs Developer Update! Temporary Solution Included
Hello, I have been experiencing this along with many others. META QUEST 3
My hypothesis on the situation is that it could have something to do with two programs installed with meta quest link and a setting (AsynchronousSpacewarp) used by the oculus debug tool for performance.
- OculusDash.exe and/or OVRservice.exe interaction when connecting to headset with Async Spacewarp disabled through oculus debug tool. (OculusDash.exe seems to be the culprit in this scenario but not ruling out the OVRservice)
- No registry edit available for async spacewarp through the oculus debug tool software and it reverting back to auto or disabled after changing compromises working link session.
I change this a lot for my headset because I have a beefy computer that can run my headset just fine at max settings and don't like the setting at all.
Someone said in another solution that they got it to work by disconnecting internet so that OVRservice is no longer connecting to a server which is probably the reason why the headset is trying to use spacewarp. I have tested the above solution and it did load into the dashboard no problem but like I said the developers need to fix the issue when OVRService connects to the headset with conflicting configs.
I am no developer or software developer of any kind and don't claim to have the answers to the solution but developers should atleast fix this problem with the one setting no one wants to use.
The solution for now though is to goto device manager on your computer by pressing Windows key + X and then goto network adapters and disabling the ethernet or wifi temporarily before you load into the dash for meta quest link.
!Update! - I have noticed that when using the headset while ethernet or wifi is offline and connecting to the link software, the headset automatically switches Asynchronous Spacewarp back to auto every time.
This switching of ASW is avoidable by using regedit on the following path to file in registry editor;
HKEY_CURRENT_USER/SOFTWARE/Oculus/RemoteHeadset
Once locating this folder, you can put the registry as DWORD 32 bit value and set the name to AswDisabled and set that registry to 1.
This will disable the automatic switching when the headset enters link mode but this does not solve the issue mentioned in the beginning of this post. NOTE: This is also a manual fix for the ASW setting and Oculus has still yet to include the missing registry for this setting in the file mentioned.
