Jump to content

epsilon748

Verified Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by epsilon748

  1. I had this issue with my desktop only when I was using the Vive Pro + wireless for some reason. It worked fine with Vive OG + wireless. In my specific case it seems to crap out with two GPUS when they aren't running SLI. Monitor connected to card 1 with displayport, got the error. Switched to card 2, same error. Turned on SLI and plugged back into card 1 - worked fine. It's a bit weird that the pro requires SLI enabled to "hide" the second card and clear the error.
  2. Agreed, I put my notes back on page 2 and it's running great on my Threadripper 1950x with the card installed in the second PCI-E x16 slot on my motherboard (running at x8). Motherboard is Gigabyte x399 Aorus Xtreme, never had any issues but I saw this popping up on reddit for others.
  3. My comments are in a reddit thread here https://www.reddit.com/r/Vive/comments/9k8thl/has_anyone_tried_the_vive_wireless_card_with_an/ In short, would not recommend. It might work OK on a system where Thunderbolt routes directly through the CPU as someone else mentioned but that may only be on Mac notebooks. Waiting on an M.2 riser cable to try directly attached to the motherboard without TB in the way.
  4. Just wanted to add a counterpoint here that I had no issues testing mine for about 3 hours tonight. Specs: Threadripper 1950x 64GB G.Skill Trident Z RGB 3200Mhz Gigabyte Aorus Xtreme x399 SLI EVGA 1080Ti Founders Edition (newest 411.70 drivers) Windows 10 (latest patch) HTC Vive (original). Everything hooked up and ran great the whole time. My only two issues were: 1) I lost mouse control on the deskop when using BigScreen, not sure if that's a bigscreen issue but it was infuriating 2) Hotplugging the battery didn't work, SteamVR and the wireless utility came back up but the HMD display was dark until I restarted the wireless utility. I don't yet have the kit to test this with my Pro. I'll be able to find out tomorrow. Other aside: This absolutely does not work with thunderbolt enclosures either, there must be too much latency because it's barf city despite steamvr showing good frame rate.
  5. Well I have good and bad news: Good news: it might not be officially supported, but it installs just fine and SteamVR loads up with wireless enabled. Great! Bad news: It's atrocious to actually use. Latency is really bad, turn your head and a half second later the image turns. SteamVR shows excellent frame rate, but the wireless display acts like it's getting nasty latency and losing some frames. It's unusuble as it is if you try to use thunderbolt enclosures.
×
×
  • Create New...