Hey guys, I just set up my third sensor set up behind me today sort of like this(The front two are more like 9 feet apart and the back is about 11 feet back, this way when I stand in the middle each one is about 8 feet from me). I set it up so my front two sensors have one 3.0 and one 2.0 (Which is what it initially was and had absolutely zero problems) and the back sensor is 3.0. The first thing I noticed is that when I am turned around facing the single camera I have some "stuttering" issues bad enough to interfere with game play. It tracks decently well otherwise but the whole point of the third sensor is so I can turn around fully without issue. Also, when I look down past like a 40 degree angle it starts making the screen shake as if the HMD is not being tracked correctly. This did not happen with just the two sensors and It is very nauseating.
Things to note:
-The back sensor constantly gives me a RED warning in oculus home: "Poor tracking quality" When I hover over this warning it says "sensor truncate 271 (Expected <=1) frames in last period"
-I re-ran the set up (Had to skip the part where you would configure sensors due to the controller not showing up on the display, I was NOT standing in the way of any of the tree sensors)
-All sensors are mounted to the ceiling which is about 8 feet high.
-Everything is updated (Drivers, windows, bios...)
-I tried different USB hubs on my computer
-I use Oculus Tray Tool to disable USB Selective Suspend so windows does not turn off devices when they are not in use (I have also tried doing so manually)
-It's ONLY the back sensor having issues (The new one)
-The other things plugged in are my monitor, mouse, keyboard, the included xbox controller dongle and ethernet
-I DO havea homemade counterweight. I made sure that most sensors are not covered and have not had problems with it during use of just two sensors
-It is NOT dirty as I just took the plastic film off of it today
-The back sensor is using this extension cord. It shows up as 3.0 and all reviews say it works perfect for the rift
-I re-ran the set up (Had to skip the part where you would configure sensors due to the controller not showing up on the display, I was NOT standing in the way of any of the tree sensors)
I was able to get this part to work, please ignore this note.
What motherboard/CPU do you have and also what other USB devices do you have connected?
Also, it's possible that the extension is causing the issue as well even though it works for some people. HDMI cables can be finicky that way too. A small manufacturing tolerance could cause a cable to work for one person but not another.
Was just about to suggest the same as Drunk3nShaman - try some different sensor configurations with the affected sensor.... move that one to the USB2 port, other 2 in the USB 3. Swap the sensors out, see if the problem moves with the sensor or stays in the position. Just run with 2 sensors including the affected one - see if it works then. That'll tell you if you have a dodge sensor or if it's USB bandwidth.
Still need help?
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.
