Ohono

oops double post

Hello again, I hadn't replied to this since I was planning to get a new motherboard and CPU. I went from a ASUS z97-Pro to a Gigabyte Z390 Gaming SLI and from a 4690k to a i7-9700k. I was around the bare minimum for VR before and my CPU was constantly maxing itself out and probably bottlenecking with the 2070 so I figured I would report back if this didn't fix anything. The second controller is still always losing tracking and flying off at times and the first one is still 100% fine. I did not get a USB card since I'm running a wireless setup. I have already: Updated my BIOS to the most recent, non-beta version. Rechecked my entire room this time for reflective surfaces. Changed the position and angles of my base stations. Tried a wired setup. Checked to make sure all of the equipment was up to date. Troubleshooted with my additional controller that I bought in the beginning to test for that. Reinstalled Windows 10 64-bit. Reinstalled all of my Vive related software and uninstalled Viveport. Removed the 770 I had installed to use a third monitor Replaced the USB A-A that came with the power bank with the one that connects the link box to the PC since I've seen that be an issue for some people I did notice that the controller with the bad tracking would unpair itself if the HMD/Wireless Adapter (I don't know which is responsible for managing that) managed to get too far away from it and the "good" controller would always stay green. Too far away, in this case, was only around 2 feet away from the headset and it seemed like certain angles and positions would intensify these tracking issues. With more research, I found this another thread that sounded like how my controller would fly off and constantly lose tracking. So, I made a system report to see if the IMU was logging similarly to the user in the other thread and it seems close but not as aggressive. All of the times where my second controller, the right, would lose tracking, it logs something like this: Fri May 10 2019 15:43:52.072 - lighthouse: B12359B2F6: Triggered keepalive (succeeded)Fri May 10 2019 15:43:52.176 - lighthouse: B12359B2F6: Packet received after 0.163s, keepalive (0/1)Fri May 10 2019 15:43:52.633 - lighthouse: LHR-FD767FC7 C: ----- CALIBRATED base 043487CE at pitch 32.98 deg roll 5.96 deg -----Fri May 10 2019 15:43:52.662 - lighthouse: LHR-FD767FC7 C: Resetting tracking: IMU misalignment unreasonably large (19, 4.6, -17) deg sigma 1.8Fri May 10 2019 15:43:52.662 - lighthouse: LHR-FD767FC7 C: Dropped 1 rejected updates, 19 back-facing hits during the previous tracking sessionFri May 10 2019 15:43:52.737 - lighthouse: LHR-FD767FC7 C: ----- BOOTSTRAPPED base 043487CE (immediate) distance 2.02m velocity 0.63m/s base pitch ~35.2 deg roll ~5.9 deg ----- LHR-FD767FC7 being my headset dongle version and B12359B2F6 being my right controller. Here's the full system report: https://pastebin.com/Wm4RRZfR Also, my wireless adapter has always shown up as "DisplayLink_USB_6101-430Z189W00718" or "Unknown Tracking Device" with a green hexagon in SteamVR. I don't know if this is an issue or not. Here's a USBDevice report as well: https://mega.nz/#!J58E3QbI!dd1YTHnfYOcoN8uCEKgVWXq7F715QuJKw_KAxBrjWNc

Sorry for the double post but attempting to sync the base stations with a cable made no difference at all.

Gave this a try; didn't work. I also misplaced the sync cable that came with my Vive so I went ahead and ordered a really long 3.5mm to 3.5mm cable to sync my base stations since I hear that could help.

I don't have ASUS AI suite or anything like it installed and the problem still persists after making sure I'm only using USB 2.0 ports.

Sorry, I was bringing up the wireless card as something that was different from the older thread about this problem. I thought it would be important to mention that I may have different equipment. No, I have never used my headset outside of using it wirelessly and these issues started out of the box.

Hello, I would like some help fixing this issue that I see someone else had almost 2 years ago with no apparent resolution. Just like Oddball's thread linked above, I have this exact issue where the second controller that I pair always has poor tracking ranging from minor jumps and hiccups to full-on desynchronization while using every type of software in VR. I even purchased a third controller to make sure that this wasn't a hardware issue with the controllers themselves and all 3 of these controllers work fine as the first controller paired in SteamVR and all 3 of them show the same amount of poor tracking as the second paired controller. However, unlike the thread above, I also have the wireless adapter running in a PCIe x16 with a RTX 2070 and a 770 specifically for my additional monitor that doesn't have a displayport for the 2070. To try and troubleshoot, I have already: Completely reinstalled all VR/Vive related software Moved the WiGig card to a PCIe x1 and back Swapped base station positions, flipped their channels, adjusted their pitch several times. Having read that the wireless adapter uses a 2.4ghz radio, disabled my modem and router's 2.4ghz transmission to avoid interference Removed all reflections from the view of the base stations Updated my BIOS and OS. I haven't tried to use my headset wired via the linkbox since it isn't an option; I would prefer to keep my other peripherals plugged in for ease and to keep my workarea manageable and I don't really have the environment to have the cables running to the space I have set for VR. I do have an ASUS motherboard (Z97-Pro) and I saw that people were having issues with that but I don't see how the USB issues ASUS motherboards seem to have would also have this effect with the wireless adapter. I really hope that you guys can help me fix this without too much trouble. Thanks.