Oculus 1.11.0.335615 (1.11.0.335772) Issue Tracking Touch and Sensors Jump

[AlehandoroVR]

I have 3 constellation, in the previous version everything worked "well", had micro jumps but little more. Now the change is very radical and the jumps are much worse.

https://youtu.be/ULwuvaMkLu8

And in this video you can see how the constellation jumps

https://youtu.be/RgszmbRsIM8

All with the last versión release today: Oculus 1.11.0.335615 (1.11.0.335772)

[danybonin]

also you must not place the 3rd sensor directly behing like that. Touch controler and headset himself have led emitting infrared light. If the 3rd sensors is directly behind, there coud be some light that reflect on the front sensors glossy finish that the 3 sensor can see and cause bad tracking. Keep that in mind

[AlehandoroVR]

YoLolo69 said:

@Alehandoro That's a very good report and I'm sure Support Team will be glad if you get in touch with them showing this.

I know it's not a good solution, but did you try to set the 3 sensors exactly same height, same vertical angles, at least for testing purpose? The rear one don't seems to be same height, and I'm pretty sure the height glitch seems related to the height differences between sensors... I had such problem with my 2 sensors (before the last update) and my sensors had 15cm differences, and it was exactly the height glitch I had (15cm), so setting them exactly same height and angle fixed the problem (even before the last update). Could worst to try...

All this information is in the hands of the support team since last night, with logs and videos explaining the problem.


 I have also tried to place the sensors at the same height, and the problem continues.

In the previous version I did not have any of these problems, currently this situation I can not play quietly.


 I have also connected the 3 sensors directly to the USB 3.0 of two different controllers so as not to saturate them. I reduced the distance from 4m to 3m. I changed cables. I connected the Constellation back directly to the motherboard.


 For now I have not found any solution and I continue to do tests desperately.

[YoLolo69]

Ok. As said by danybonin, Oculus don't recommend to put the third sensor right behind you at the middle. I know it seems logical, but they have several reasons to not recommend this setup it seems. Did you try behind left or behind right corner? I ordered today my third sensor so I'll be able to do some testing soon...

[regularears]

Sudden massive improvement this afternoon.

I realised I hadn't re-run full sensor setup so I did that.

I also have one monitor that slightly occludes vision from one camera so made sure that was out of the way.

When I'm not using the headset I keep it out of the tracking area so I made sure it was in the tracking area when I started the PC. The controllers too.

And bingo.

Over 2 hours of pretty good (but not perfect) play. Arizona Sunshine and SportsBar VR through Oculus and Eleven Table Tennis on SteamVR.

Towards the end I was getting a bit of dancing from the right hand but it quickly recovered. No resets, restarts or batteries out and in.

Just as I was losing heart this has come along to remind me that when it works this system is good enough. If I can have 2 hours of pretty much trouble free play then this thing can work.

I just need to be able to recreate the circumstances so that it works that well all the time.

[AlehandoroVR]

YoLolo69 said:

Ok. As said by danybonin, Oculus don't recommend to put the third sensor right behind you at the middle. I know it seems logical, but they have several reasons to not recommend this setup it seems. Did you try behind left or behind right corner? I ordered today my third sensor so I'll be able to do some testing soon...

I know, but with this installation i havent problem in previous versions of Oculus Home. Even so, I just did a recommended installation and still has the same problem. All this set at the same height (1.90m) and recommended distances.

I just discovered that the sensor jumps exactly match the jumps of the Touchs.

In the final configuration screen, when you must check that the sensors are positioned correctly and press the triggers, if I turn and force to see the jump of the sensors looking at my hand I observe how exactly the same movement and shape does.

The only way to demonstrate this and that can be seen, is through SteamVR.

Sensor back:

https://youtu.be/MXy_sU05vis

Sensor in diagonal:

https://youtu.be/7mgFFjRLY2Q

[cybereality]

For anyone experiencing issues, please upload your LogGatherer log zip file so we can take a look.
https://forums.oculus.com/community/discussion/33792/how-to-get-logs-for-bug-reports-for-consumer-ri...
Also, feel free to reach out to Oculus Support too so we have a record of your case. Thanks.
https://support.oculus.com/

[AlehandoroVR]

cybereality said:

For anyone experiencing issues, please upload your LogGatherer log zip file so we can take a look.
https://forums.oculus.com/community/discussion/33792/how-to-get-logs-for-bug-reports-for-consumer-ri...
Also, feel free to reach out to Oculus Support too so we have a record of your case. Thanks.
https://support.oculus.com/

All this is already in the hands of the support team. With Logs and Videos.

[dougchism]

I dont seem to be having the huge problems everyone else has, 3 sensor setup, cant say the tracking is improved by a noticable amount but things seem to be working properly,

[YoLolo69]

@Alehandoro It seems computing lose the ground level or height of sensors when you turn, like a cumulate error which made change in high detection. After a short while each time you stopped, it see a problem and fix the height, and so on. Weird...
Did you try turning like this with only your headset (so Touch out of sensors view)? IMO this is linked to the very last step when you are scanned by all sensors and they deduce an height.
If it's a computing mistake, I have the feeling they should add something during the configuration process, like asking the user to walk around the whole play area to be able to create an array of average ground level values using only the headset, and avoid those "height fixes" on the fly...

[AlehandoroVR]

YoLolo69 said:

@Alehandoro It seems computing lose the ground level or height of sensors when you turn, like a cumulate error which made change in high detection. After a short while each time you stopped, it see a problem and fix the height, and so on. Weird...
Did you try turning like this with only your headset (so Touch out of sensors view)? IMO this is linked to the very last step when you are scanned by all sensors and they deduce an height.
If it's a computing mistake, I have the feeling they should add something during the configuration process, like asking the user to walk around the whole play area to be able to create an array of average ground level values using only the headset, and avoid those "height fixes" on the fly...

Just came to describe that the problem only occurs with CV1.


 The touch has no problem, it is the CV1 when it is detected that a adjustment is made in the height that produces the jump, also dragging the positioning of the touch.


 Also, if I unplug the USB from the CV1 and then connect it, for a few seconds everything works fine.

I did not have these problems before, neither the problems of height nor the problems of the soil. It seems that when trying to solve this, in other users has generated the problem that others have solved.