I'm currently at a point where I should do some alpha testing of my project (developing under Linux). Unfortunately, I have massive issues with drift. I'm now sure that the problem is not related to the bug I reported in this thread, where I found out that the Linux SDK's configuration utility generates malformed JSON files, and thus, calibration data is unusable. What I did now is to copy the respective configuration JSONs from Windows (which btw do use a "." a decimal seperator). But still I have massive drift issues. I spent the whole day to track down the reason without success. I made the following confusing observations:
The drift is not only a yaw drift, but a combination of yaw + pitch. The pattern always seems to be the same: A very fast downward drift right after initialization (the floor becomes the wall in front of me) followed by a slower yaw drift (but still about 3 min for 360°).
I did not have any drifting issues in Linux a few weeks ago, when developing and testing with the old SDK. So my initial guess was that the drift came with SDK 0.3.2, but it looks like this is not the case since:
In Linux I have this massive in every application: The 0.2.5 world demo, the 0.3.2 world demo, and my own projects irrespective of which SDK I use.
Now to the situation on Windows: If I reboot my PC from Linux to Windows, there seems to be a side-effect of having run Linux first (!) with the result, that I have the exact same drifting pattern in every application on Windows as well (irrespective of SDK version or whether I re-calibrate the yaw correction). This almost led me to conclude that the tracker really must have been damaged recently. However, unplugging+replugging the USB connection solves the problem! Cold-booting Windows also avoids the problem.
Now I only see a few reasonable explanations:
In the last few weeks something on my Linux system must have changed that influences the communication with the Rift.
Having executed the 0.3.2 configuration utility had a side effect on the Rift (very unlikely!?).
My tracker is broken in a very strange way which allows Windows to still work properly with the device, while Linux cannot deal the tracker any longer.
It would be great if you guys at Oculus can comment on the likelihood of the two latter causes. If I would know the issue is caused by my system I would be willing to dig deeper to resolve this problem.
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
