cancel
Showing results for 
Search instead for 
Did you mean: 

"Jerk" problem with 3 sensor tracking

Elgsdyr
Honored Guest

[Firstly: I'm already in direct contact with a supporter, but since my tolerance for supporters going through huge check-lists of standard suggestions is very low, I decided to try my luck here as well since others might have had this exact tracking problem.]


I'm experiencing serious tracking problems with my Rift, which started when I added a 3rd sensor to my setup.




The problem:

When using the full 3-sensor 360° setup, the whole (virtual) world
jerks in a direction frequently. For a long time I thought it was
completely random but I've finally managed to find a predictable pattern
to it, and I can now consistently reproduce the jerk.




With a 2 sensor setup I get fine 360° tracking of the
headset (the touch controllers are a different matter, though) with no
signs of the jerk problem described.




Adding a 3rd sensor: Initially, if I keep facing the front
sensors there's no jerk. If I turn 180° so that I'm partially facing
the rear sensor and wait there, there's suddenly a massive jerk in one
direction after a short while - usually within 5-20 seconds. If I then
stay facing that direction, there are no problems. But if I turn back
towards the front sensors again and stay there, I get a massive jerk in
the exact opposite direction of the first one within 5-20 seconds.
Again, if I stay there, there are no problems until I turn towards the
rear sensor again in which the above pattern repeats. Of course, in most
games where I constantly turn around, I get the jerks all the time,
which is highly annoying in itself as it is massively breaking the
immersion, but even more so as I'm quite sensitive to motion sickness.




The jerk is typically around 20-40cm and it always moves
in one direction and then moves back about 50% towards the starting
point, like it's overcompensating first and then settles. The entire
movement takes around 0.5-1 second.




General information:



- This happens in all VR games and programs - even in the Oculus Home.



- I've tried every conceivable sensor placement like
moving front sensors closer to each other or further apart, trying the
rear sensor in both corners behind or even more towards the middle,
having sensors at different heights or completely at level, placing them
in the corners of a perfect rectangle, and many other variations.
Whatever the setup I still get the jerks. My current setup is "corners
of a perfect rectangle" with 2.9m between front sensors and 3.1m to the
rear and all sensors level at 1.25m (height) - all pointing towards the
middle of the play space and towards chest height.



- I've tried swapping the rear sensor with one of the
front ones to see if it's a somewhat defect sensor, but I get the exact
same behaviour.



- I've tried swapping the sensors around in the USB ports
in pretty much every conceivable way. I have an onboard Intel USB
controller as well as the recommended Inateck/Fresco 4-port controller -
both seem to work well. Of course, some setups tend to stress the
tracking but any setup will still give me the jerks. The front sensors
are connected through USB 3.0 - one on the Intel controller and the
other on the Inateck, and one of them currently with a high quality 1.8m
extension (I've tried without, of course - no difference). The rear is
connected to USB 2.0 through the active extension cable that came with
the sensor. I've also tried changing one or both of the front sensors to
USB 2.0 with no change in regard to the described problem (all sensors
on 2.0 gave me additional tracking problems, though). Right now I'm
using the latest Fresco drivers for the Inateck card, but I've also tried
with the generic Microsoft drivers with no change.



- All USB power management has been turned off in the
Device Manager - both on the Rift sensors themselves as well as any
port/hub. I'm running the High Performance power plan as well as turning
off the profile's power management (USB selective suspend + PCI Express
Link State).



- Nothing is standing in the way of the tracking - all
sensors have a full uncluttered view of the play area. I've also tried
covering everything in my room up with bed sheets in case there was a
problem with reflections or something else messing up the tracking. No
change.



- This is a headset problem only. It doesn't matter if I'm holding the touch controller or if they are sleeping somewhere.



- Some people with (somewhat) similar glitch/jerk problems
apparently got rid of it using specific NVidia drivers. I've been
through all the suggested driver versions with no change. That includes
v384.94, 388.00, 388.59, as well as the latest 391.01.



- Some have suggested problems with XMP being enabled in BIOS. As far as I can see this isn't enabled on my system.



- Some have had problems with RAM being clocked at 3000
MHz that were fixed by clocking at a lower speed. My RAM is clocked at
1600 MHz.



- I even tried making a completely fresh and fully updated
install of Windows 10 on a separate partition with nothing installed
apart from the Oculus software. Still didn't help.




My system:

Motherboard: Asus Maximus VI Hero

Processor: Intel Core i7-4770K

RAM: 8GB Kingston HyperX Gen DDR3-1600

Graphics: Asus Strix GTX1060-6GB

Extra USB: PCI-e Inateck KTU3FR-4P

OS: Windows 10 Pro (fully updated)



1 REPLY 1

Anonymous
Not applicable
I have the exact same problem, did you ever find a solution to this?
Get 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.

Check out some popular posts here:
Getting Help from the Meta Quest Community
Tips and Tricks: Charging your Meta Quest Headset
Tips and Tricks: Help with Pairing your Meta Quest
Trouble With Facebook/Instagram Accounts?