@VibrantNebula, thank you so much for your informative reply. This is very helpful in understanding and diagnosing the problem. I immediately took a look at the SteamVR report that I had generated yesterday, and indeed, there is multiple lines with the "back-facing hits". Tue Feb 19 2019 21:45:30.831 - lighthouse: LHR-AF5B20EB C: Dropped 2289 back-facing hits, 4 non-clustered hits during the previous tracking session Wed Feb 20 2019 00:50:15.841 - lighthouse: LHR-176D1AE4 H: Dropped 363112 back-facing hits, 20 non-clustered hits during the previous tracking session I cannot say for sure, but the first record might coincide with my "troubleshooting session", when I would try to cover any reflective surfaces in the room that is my play space. I understand that the goal here should be to minimize or possibly eliminate this factor? I am, however, unsure as to what causes the "dragging" that I am getting in the controllers, when turning to or away from one of the base stations. What worries me is that this particular issue never goes away. This was (and still is) a slightly different thing, and it's been a persistent issue no matter what I did, including covering reflective surfaces. The USB bandwidth issues and/or wireless interference sound like a solid lead. Here's my take on that: I tried plugging the Link Box into other USB ports in my PC, both 2.0 and 3.0. Unfortunately, it did not make any difference as regards the tracking issues. I currently have the Link Box plugged to a USB 3.1 SuperSpeed port. Could it still be incompatible with my Vive (Pro) and hinder the tracking? Aside from my own home WiFi network, I am reading two other strong signal networks over here at the moment, most likely all on the same 2.4 GHz frequency. If this is the case, and they do cause trouble to my Vive, then the question is, would it help to switch the base stations' Bluetooth channels? (I am, however, not aware of any methods to do the same with the headset or the controllers, is there a way to do that?) Thank you so much again for your help. It's not a simple matter to resolve, but your reply already seemed to have pointed in the right direction.
... View more
I'll give you a sadder story. I have put together an ITX beast machine - to be semi mobile. It's designed for both a VR development and a live performance. It cost me months of work and thousands of USD. I have recently returned a complete and fully functional Rift + TP Cast, thinking I was making an upgrade getting the new Vive Pro (with the Knuckles and inhouse wifi module I hoped). But since the initial disappointmement of not being able to even run the headset without all the accessories (unavailable separately atm), I also found out the wireless kit won't do, as my ITX motherboard simply doesn't have a second PCIe slot. So TPCast is my only hope to ever even think of running the Vive Pro wirelessly on my rig. That, or going back for Rift and saving another few thousand bucks. I still have two weeks to decide, but I've got to tell you, looking at the VIVE Pro sitting here like a paperweight, each new wasted day makes it less and less appealing.
... View more