Jump to content

ZombiePharaoh

Verified Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by ZombiePharaoh

  1. The workaround was, supposedly, that if you unplug litterally everything from a USB 3.0 port, and everything USB 3.0 from a 2.0 port, it might work. It didn't work. In six months of owning a wireless adapter, I have no been able to successfully use it once. Across twelve different Windows 10 installs, two graphics cards, and three motherboards. HTC Vive support was no help at all. I'm selling my HTC Vive w/ Wireless Adapter and getting a Valve Index. I'm just waiting for the annoucement so I can figure out if I can keep my existing lighthouses/controllers or not.
  2. Same. It never worked on my machine in six months. Ordered a new X470 Prime Pro motherboard so I can give my brother my old X370 Prime Pro for his birthday. Hoping that might fix it and if it doesn't then I'm going to try the USB3.0 trick I read about recently, or maybe, because the new motherboard has two m.2 slots available instead of just one like the x370, I'll have an extra m.2 available and can try that workaround for once.
  3. I'm pretty aware though I still appreciate the help. Here's my Friday night: 1. Move to install the latest DisplayLink drivers from their official website, I'm told I already have the latest drivers. 2. Move to install the latest SteamVR Beta and find that it too, is updated. 3. There's an update available for my BIOS, moving from v.4024 to v.4207 on the ASUS x370 Pro Prime. 4. Test. No luck. Error 208. 5. Unplug the LinkBox, removing all cables. 6. Disable the Power Management option across all list items under USB Hub Controller in Device Manager. 6. Test. No luck. Error 208. 7. Physically move my graphics card from the PCI-E 3.0 x16 #1 slot to the #2 slot. This opens up my PCI-E 2.0 x1 #1 & #2 slots for the Wireless Adapter. Previously it was in the #3 slot. According to the IRQ assignments in my motherboard manual, this should change it from Channel D to Channel C. See attachment. 8. Test. Still no luck. 9. Check out Steam VR settings. Try the usual things like enable/disable Direct Mode. No luck. I do notice that Steam VR very obviously can not see my GPU or GPU driver, much less the headset. Try to remember if this is new or not? And before anyone asks, this is the second GPU I've tried with Wireless (1070Ti to RTX 2070) and the second fresh install of Windows 10. 10. Google the internet for the 500th time looking for people suffering from a similar fate, find mostly my own posts. Give up. Decide to go back to playing Neverwinter Nights. See everybody in two more weeks. Another note: Steam VR can see every other part of the Vive unit, besides the actual display, over wireless, and the display itself works over wired.
  4. Thanks for the reply . You're right, in that my wireless adapter was free (or near to it). I'd rather not bother with a return, though if I had paid full-price I surely would have by now. The Watchdog violation did happen once. But it's mostly just Error 208. I've since done two fresh installs of Windows 10 (I do them about once a month) to no luck. I originally tried it without the Link Box plugged in, but I plugged it in a couple months ago to on the advice of some forum posters - I'll try again tonight without the Link Box. Thanks again!
  5. About once every two weeks I hook everything up, reload all the latest drivers (including DisplayLink from the website), make sure SteamVR is updated, check for BIOS and OS updates. Still get Error 208: HMD Not Detected. Every time. No change. It's been more then two months now.
  6. No fix available. Welcome to it. We sit and we wait. HTC recommends going ahead and f*king yourself to pass the time. Oh, and I've done three fresh installs. So no, that doesn't fix it necessarily.
×
×
  • Create New...