Rift S Touch Controller positional tracking timeout on slow movements (1.37.0.245188)

Tuuvas · June 2019

As seen in the below gifs, there appears to be some sort of timeout for positional tracking of the new touch controllers. If I'm making slow movements, the touch controllers appear to be "lost" and cause massive issues with position; however, performing the exact same movement only a little faster produces no issues.

Steps to Reproduce:

Install fresh batteries
Restart Oculus Software via Settings -> Beta -> Restart Oculus
Launch any software as long as you can see your hands
Hold hand out in-front of you
Begin turning very slowly as seen in below gifs

Expected Results: no tracking loss
Actual Results: tracking loss, but only on slow movements

sraura · June 2019

Well... unfortunately my touch controllers seem to be working fine on 1.37.0.245188. Can't repeat what u show on those gifs.

Another mystery there...

Tuuvas · June 2019

sraura said:

Well... unfortunately my touch controllers seem to be working fine on 1.37.0.245188. Can't repeat what u show on those gifs.
Another mystery there...

This is more easily reproduced when using something like a gunstock to keep things steady. One way to simulate this is to pretend you're holding a pistol with two hands very very steadily... as if trying to line up a headshot from 30 yards. Then pretend that person is walking slowly left and right while you continue to track them with the ironsights.

Jorgec81 · June 2019

I have exactly the same problem I have the protuve vr and cannot use it because of that, when I try to follow some one and try to do a precise shoot I lose tracking in less than 5 seconds, it is extremely annoying.

Any way to get support for this? This doesn't happen on the CV1

Koiz · June 2019

So I was able to reproduce this with the latest update.

I noticed something in Onward... when I was backed to a wall where you clip and the controllers rumble the controllers never stopped tracking. I would hold it the same way and move back and forth, if it wasn't rumbling then it would stop tracking, if it was rumbling it wouldn't stop tracking at all. All while pointing it at the same position.

Its not a huge deal breaker at the moment for me but its going to be frustrating when it actually impacts a potential shot.

This is using a protube, and there is ZERO occlusion.

Jorgec81 · June 2019

For me is a huge deal breaker because every time I'm steady waiting for someone to show across the street the tracking fails and cannot aim properly until I move the controller a little bit

jb295mano · June 2019

Seems like this is a general issue with the current controller tracking firmware, the problem also seems to occur on the Quest: https://www.reddit.com/r/OculusQuest/comments/bx0lio/controller_tracking_issue_with_slow_and_subtle/

crock5 · June 2019

Tuuvas said:

As seen in the below gifs, there appears to be some sort of timeout for positional tracking of the new touch controllers. If I'm making slow movements, the touch controllers appear to be "lost" and cause massive issues with position; however, performing the exact same movement only a little faster produces no issues.
Steps to Reproduce:
Install fresh batteries
Restart Oculus Software via Settings -> Beta -> Restart Oculus
Launch any software as long as you can see your hands
Hold hand out in-front of you
Begin turning very slowly as seen in below gifs
Expected Results: no tracking loss
Actual Results: tracking loss, but only on slow movements

I have contacted the developer support with the exact same issue on Quest (described in the reddit post that is linked in the comment above), here is the response:

"Very slow motions are likely triggered by our motion detector, which is used to help prevent tracking glitches when the user puts the controllers on their desk. We are looking into adjusting our thresholds and parameters to see if we can improve the experience for these edge cases."

Apparently, they are afraid of error drift or other tracking glitches and therefore ignore the camera tracking input once the IMU of the controllers stop detecting large enough changes. A simple fix, in my opinion, would be to check if the suer is still touching the controllers via the capacitive touch buttons. But since this is a firmware issue, we can only wait and see what happens.

I would like to encourage you to open a support ticket yourself, so that they know you are affected as well.

Jorgec81 · July 2019

Yea I will do it because for me the protuvevr is not usable, I'm happy that at least they almost fixed the issue with aiming when your controller is to close to the headset tracking is almost perfect now except for this issue I still cannot use the gunstock precisely

adam.poole.313 · July 2019

I am having the same problem using the latest update. Happens if you move too slow or don't move it at all. This is a serious problem in my opinion that will effect most games. You don't necessarily realize that it isn't tracking your controller because its stationary anyway. But if you need any kind of quick movement from a stationary position it will never happen.

mastixas · July 2019

Any news on this "feature" that keeps on destroying my fps experience? It also happens on Quest where its very annoying trying to rest my hands on my chair arms navigating on my pc with virtual desktop and freezing all the time doing slow movements. I am currently on beta.

DSolt · September 2019

I have the same problem. Is there a solution or are we waiting for the firmware update? Someone already made a video of the problem ...

pappythefoo · September 2019

Exact same problem Im having. This is really killing Rift S + gunstock combination.

dan108 · October 2019

Any news?

zoli3348 · October 2019

My friend has booth headset. Rift S and Quest. He told me in the Quest works prefectly the tracking with gunstock already. He was tested it months ago and when not works but he tested today and the result is good.
So Quest updated already to usable but Rift S not yet

pappythefoo · October 2019

No update for Rift S user on this issue yet??? this issue keeps me from playing VR with Rift S.

David_30 · November 2019

I have the same issue...

GeekyGami · November 2019

I am having tracking issues on my Rift CV1 as well now since two updates ago.
I am on 1.42.0.314906.

mastixas · November 2019

No fix yet, dissatisfied customer here.

pappythefoo · November 2019

mastixas said:

No fix yet, dissatisfied customer here.

I want them to take this issue seriously....
Do they even notice this issue though

Jorgec81 · November 2019

no news so far, i actually bought an Vive pro to have an option to this but guess what the vive pro tracking is worst than the actual rift s tracking, they have the old issues of gittering and drifting the oculus cv1 had when they released the 360 experimental, its a shame but i returned the vive pro and stick to the oculus.

by the way i found a way to varely use the gun stock, if i dont use the cups and just use my small finger grabbing the stock grips (where you put the magnetic cups) to stabilize, the tracking doesnt freeze, it seems that inside out tracking need an small continuous movement ot keep tracking, its a shame because besides that the rift s tracking is really really good with the latest updates i can punch my face and ruber my cheek and the thing just keep tracking lol.

pappythefoo · December 2019

Not fixed yet?? Oculus does NOT support gunstock then????????????????

gramah501 · January 14

Same problem, any solution?!

afoxinspace · January 17

Bumping, just got a ProTube VR to play Onward. It works perfectly until I use a scope and move very slowly. Exact same problem. There should be a simple ticker in Settings to disable the 3-second auto-shutoff, because this is making long-range gunstock use in the Rift S 100% impossible. How many of us need to put in a ticket for this?

pappythefoo · January 27

I kind of gave up on Rift S on this matter.
Can anyone name a VR headset that works well with gunstock? and doesnt stuck on slow movement?

natedizzy · February 17

oculus please respond to this. i mean, c'mon its not even an issue that isn't able to be fixed. a person above gave you a simple fix: if the person is touching or manipulating ANY of the buttons, don't put the tracking to sleep.... btw tracking overall is fantastic. fix this one thing and you're pretty much done for good with this.

javivi0000 · April 6

Escribe tu comentario

javivi0000 · April 6

Yo también tengo el mismo problema, y seguimos sin respuesta, nada más que saben lo que sucede, y que lo corregirán.... pero no sabemos cuando.

javivi0000 · April 15

javivi0000 said:

Yo también tengo el mismo problema, y seguimos sin respuesta, nada más que saben lo que sucede, y que lo corregirán.... pero no sabemos cuando.

Ninguna respuesta de Oculus... solo silencio. Es una vergüenza que algo tan sencillo de solucionar y tan molesto para jugar a shooters y no hagan nada.

sclennon · April 29

I sent a ticket in. Oculus seemed to act like they had never even heard of this issue. After a couple weeks of sending emails back and forth with the standard "trouble shooting." I got a reply saying that Oculus will continue looking into the issue, and get back to me in 3 to 4 business days. They did and the response was, "We are receiving a larger volume of tickets than usual and we will work your ticket in the order it was received." My guess is that my ticket is benched. Unless a fix comes for this tracking issue then I would say the Oculus S is only better than the CV1 in one aspect its display. Sucks because I really like my CV1 and really liked what Oculus was doing, but if this is where Oculus is going then I will probably upgrade away Oculus next time I buy a headset. For Oculus next time someone sends you a ticket regarding this issue try not to insult your customer by pretending y'all are unaware of this issue.

sclennon · April 29

In the mean time I found that tapping my controllers when using a scope while tracking my target was one way to make sure the controllers do not freeze. Its not great but it works for me.

Rift S Touch Controller positional tracking timeout on slow movements (1.37.0.245188)

Comments

Howdy, Stranger!

Quick Links

Categories