The second paired controller has poor tracking

[Ohono]

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:

1. Updated my BIOS to the most recent, non-beta version.
2. Rechecked my entire room this time for reflective surfaces.
3. Changed the position and angles of my base stations.
4. Tried a wired setup.
5. Checked to make sure all of the equipment was up to date.
6. Troubleshooted with my additional controller that I bought in the beginning to test for that.
7. Reinstalled Windows 10 64-bit.
8. Reinstalled all of my Vive related software and uninstalled Viveport.
9. Removed the 770 I had installed to use a third monitor
10. 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

 

[Ohono]

oops double post