01-19-2021 06:48 AM
Solved! Go to Solution.
04-11-2021 05:12 AM
I managed to solve this by reseting the heatset and logging in with my gf's facebook account. This imeediately fixed the problem, I removed every trace of the occulus app from my phone. Then logged in the headset with my account. It is perfect now. I think it is a shame, that oculus doesn't provide the means to reset the sensors, and they are even ok with replacing it instead of figuring out a solution.
01-19-2021 07:56 AM
01-19-2021 11:12 AM
kojack said:
I haven't tested it myself with Virtual Desktop, but you should be able to run the Oculus Monitor program in my signature (it's a PC app, so needs a Link cable or Virtual Desktop for Quest 2).It's a test program that shows the tracking and input state of Touch controllers, so you can see exactly what the trigger is doing (is it not changing at all? Limited range? Is it the raw, normal or no dead zone trigger values? Etc). It won't fix anything, but it should expose any problems.(That version will say you have a Rift CV1, but it still works fine with the Quest 2, the Oculus SDK from back then just gets the name wrong)Yep, Oculus don't support countries other than the 23 they officially sell in.
01-19-2021 11:24 AM
01-19-2021 12:43 PM
01-20-2021 09:07 PM
01-21-2021 02:56 AM
01-25-2021 02:05 AM
01-25-2021 02:33 AM
04-11-2021 05:12 AM
I managed to solve this by reseting the heatset and logging in with my gf's facebook account. This imeediately fixed the problem, I removed every trace of the occulus app from my phone. Then logged in the headset with my account. It is perfect now. I think it is a shame, that oculus doesn't provide the means to reset the sensors, and they are even ok with replacing it instead of figuring out a solution.