Hello there fellas. We have a problem. We use autodriver for E2E
testing. In our old codebase everything worked fine (Unity 2018.3.4 +
VRTK) in our new we see an offset between recording and playing back
.autodriver files which renders autodriver use...
@MetaQuestSupport I understand that factory reset seems to fix
everything. For example on my Quest-1, it was the only thing that fixed
my tracking, but also I also ALL progress on so many games. Cloud backup
is only supported by few games. BTW, the p...
I had the same issue. I had to use adb command adb shell svc usb
setFunctions mtp as a solution. I played around with the other settings
to see how they act. The answer is "with zero logic!" for example even
if you disable oculus link, you still get ...
For anyone reading, our temporary solution is place the quest device on
the EXACT compass bearing it had when the recording was started. This
seems to be the only way to eliminate the offset between recording and
playback
Hey there. We had similar issues and I just found out that you need
ARM64 as an architecture to have autodriver run. This happened after a
specific firmware update (I think it was around 44v-47v). Did you find
anything related to this?