FOUR SENSOR ROOM-SCALE WORKING GREAT NOW!
I just thought I would pass along some technical obstacles I have gotten around with room-scale setup. I will try to keep it as short as possible but it's not likely as I want this formula to read logically and be detailed enough to offer useful information that anyone can relate to or follow and replicate. Until last week I had been running an under-spec gaming rig with a Z68 M-ATX MB with i5 2500k OCd to 4.5GHz and 8 Gigs of 1600 RAM with a 980ti Lightning. I've had many hours of DK2 and even some CV1 fun running on that spec but since getting a CV1 months ago and Touch when released then third and then fourth sensor I've been working around the under-spec nature of my rig.
The old Z68 MB had no compatible USB 3.0 ports but a couple good USB 2.0 ports to supplement the recommended Inateck PCI-E USB 3.0 card that I got. I had marginal success with two high diagonally mounted sensors at first but still wanted better 360 degree tracking and soon got a third only to find occlusion was still annoying. At that point I kicked myself for not just ordering the fourth sensor at the same time despite four being considered to be too high demanding on single controllers. I read many of the posts from all over the web for clues and tips and obviously there were things in the actual software at that point that needed fixed with the experimental nature of the 360 room-scale beta status.
So now despite my rig still being considered older, I have just moved up to a Z87 full ATX MB with an i7 4770k stable OCd to 4.3GHz and 16Gigs of 1600 RAM with same 980ti Lightning GPU. The new version of my up to spec rig now has compatible USB 3.0 ports to supplement the limited nature of even the powered multi-port add-on PCI-E USB 3.0 Inateck card which is in a 4x slot. So even with getting all this in order following guides and with trial and error I was still spending a lot of time experimenting with USB port combinations to get it to work long enough to go through setup. Right before my Rig upgrade and the 112.xx Oculus update I had been playing successfully with three sensors on the Inateck with the Rift and one sensor on USB 2.0 MB ports in conjunction with using the forum posted PowerShell script and Oculus Tray Tool.
First run of the upgraded system I fired up the newly released Robo Recall and as soon as the game actually started scene rendering, the left eye went black and I even later had the audio drop out as well. To my dismay after upgrading my rig and the latest Oculus software, I could no longer get it fully functional let alone have it run stable enough to play. Despite now having more PC grunt I went back to playing detective testing with and without extension cables and all the USB port combos as well as with only using three sensors and even trying one or two only on USB 2.0. After I kept hearing the occasional intermittent disconnect then reconnect Windows sounds I used a USB monitoring software called USBDview to try to see what it showed happening. I watched the readouts to get some sort of insight and notice Rift audio and sensor were what had the issue. That and the the following details below has lead me to my current conclusions as well as fully functional four sensor 360 room-scale tracking with no headset audio or visual dropouts.
When watching some Rift devices working and then dropping out and coming back it seemed as if the actual data connection could work fine but just wasn't stable, like it was a device with a low battery. My assumption was it seemed like the dropouts were caused by trying to pull too much power from the MB USB port so trying to power two devices over the extended length of their 4M non active cables when they already suffered form insufficient power for the headset and sensor just made it worse. That idea had stuck in my head after reading someone else's low power speculation as well as another that had mentioned using a particular powered hub successfully.
With my bigger and new-ish MB I now had more PCI-E slots if needed for an additional USB 3.0 card but instead I ran out to Best Buy and got that mentioned powered j5 create 4-Port Mini HUB and plugged it into my MB USB 3.0 rear port and then used the new hub for one sensor cam and my Rift. Another sensor closest to the PC which is non-extended is plugged into the PC front USB 3.0 port which comes from the internal 3.0 header on the MB. The other two sensors are on the PCI-E USB 3.0 Inateck card.
The last and other most important part of the puzzle is to use a 3rd party tool called OTT or Oculus Tray Tool which incorporated power setting features along with a few other useful setting tweaks. I had emailed that dev with a question about how I used his now previous versions of his tray tool alongside the script that was posted on this forum to help with USB power settings and the Inateck card. It turns out the script did the same thing as his tool but in a slightly different way so he asked me to beta test his next release (0.66) after he incorporated the script method into his helper tool to try to make the tool even better and more reliable so there was no longer a need to sometimes also still run the script in PowerShell opened as Administrator.
So the bottom line is as soon as I used the powered j5 HUB in conjunction to the Inateck card I got reliable function and tracking with four sensors listed at 3.0 speed. Only the Rift still shows at 2.0 speed but it has NEVER shown running at 3.0 even since day one with only one sensor and no extensions. The best part is it all is working as flawless as ever. So in recap no device is using the included active repeater cables.
==> First sensor is on the PC front Oculus compatible USB 3.0 MB port without a passive or active extension cable.
==> Second and Third sensors with 4M passive USB 3.0 extension cables are on the add-on powered internal PCI-E 3.0 Inateck card.
==> j5 create powered USB 3.0 4-Port Mini Hub is plugged into the rear Oculus compatible USB 3.0 MB port. (Just side noting that it happens to be the port indicated for Bios flashing on my Z87 MB.)
==> Fourth sensor and the Rift are each using 4M passive USB 3.0 extension cables which are plugged into the j5 powered hub.
==> Rift HDMI is plugged into a 9.8 foot HDMI extension cable from Micro Center SKU 014597 QVS brand (Spec is only listed as High Speed 1080p but works well.)
==> I tightly taped up my extension connections that drag on the floor to maintain solid connection to the Rift's HDMI and USB.
==> Load and run third party Oculus Tray Tool and get it indicating green then launch Oculus Home. (Some OTT power settings may take a close and re-launch cycle or two of OTT to show green indicator.)