Jump to content
 

Search the Community

Showing results for tags 'issues'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • VIVE
    • Vive Community Forums
    • Vive Technical Support
    • Developer Forums

Blogs

  • Viveport Blog
  • Viveport Reviews
  • Viveport SDKs and Downloads
  • Developer Blog
  • Vive Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 3 results

  1. Dear HTC I am trying here as i now have tried 3 times through your advantage program without any response on the matter from Lisa. We are a development company in EU, primarily developing for Vive and Vive Focus+ the casting is still very unreliable and exact as other have mentioned back from September 2019 and onwards. The casting to MiraCast doesn't work on all devices and are very buggy. I could cast to PC, Win10 the first 2 times and after a software update from VIVE the casting to PC wont work, and casting to anything else than Microsoft Wireless Display Adapter wont work. We have tested 17 different HTC Vive Focus+ with the danish government over the past year and all with the same result, so no its not a issue in 1 headset but a software issue. I am, while writing, sitting at my pc, with the Vive Focus+ headset next to me, on the same 5GhZ internet and can see the PC name in casting on HTC Vive Focus+ but when connecting it crasches and cannot connect. So the statement that it works for Pc is not correct. It wokrks for Pc 20% of the time and for casting to a dongle 80% of the time. (Based on 1 year of daily usage with the Danish government, conferences, event and presentaitons) It is very unreliable as we not have been to events and conferences with it all working and next day no casting, with same setup and not changes from prior day. Please please please fix the casting, its a standard format as you HTC mention yourself in your documentation and should work 100% as in any other product on the market. The headset is sadly unusable without casting when developing and using with patients and governmental rehabilitation, as the staff need to monitor the patient when training. - Best VR Rehab @Tony PH Lin @Cotta @JustinVive
  2. I've recently purchased a VIVE Pro with the wireless kit. I originally installed the WiGig card into a PCIe 1x slot. Upon encountering rather random (yet frequent) watchdog violations, I decided to try switching to a the second 'large' (16x?) PCIe slot. According to my mobo's manual, all 1x PCIes are only 2.0, while the two larger ones are both 3.0 (AB350 Pro4). However, the WiGig does not get recognized in this slot, even after cleaning, checking connections, etc. ('Please shut down your pc an d make sure the WiGig PCIe card is properly inserted'-error). No idea why, no change in bios settings seems to make the card recognizeable to the system. When I slot it into the 1x PCIe, it gets recognized without a problem. In both slots, the card is powered (blue LED glowing). My question is the following: is it even true that you need PCIe 3.0? I haven't actually heard any official statement to this effect. I.e.: should I try to somehow connect the WiGig to a PCIe 3.0-like slot (e.g. via an M.2 adapter) or is this likely not the issue at all? If it's the latter, I'd just try and solve the issue whilst using the PCIe 2.0 slot (where the HMD actually works most of the time). That said, so far all watchdog bsods happened during intensive first-time asset load events (i.e. they didn't occur during subsequent loadings of the same app, typically). This suggests that the watchdog violation has something to do with bandwidth bottlenecks. But that's just guesswork at this point :( Any suggestions? Any surefire ways to make my mobo recognize the WiGig in the 3.0 slot? Any reassurances that PCIe 2.0 is perfectly okay for the WiGig, bandwidth-wise? Specs: Motherboard: AB350 Pro4 CPU: Ryzen 5 1600, 16 gigs of RAM GPU: Radeon RX 580 Bios fully updated, new AMD chipset drivers, Ryzen gaming mode activated, SATA AHCI controller drivers updated, gfx drivers updated, UEFI reset to defaults.
  3. I can't find anything on this so far. My Vive Pro has been rock solid, and then starting last night, having this issue; Start SteamVR, and it says the headset is tracking and looks ok, drivers up to date. Lenses are black, but then flash white 3 times, and go black again. I tried re-plugging in cables, different video port on video card, rebooted windows, restart Steam, hitting the button on the left side of the HMD - no change. However, if I let the headset sit, it does go into standby mode. If I leave it alone for a few minutes, suddenly the headset just turns on, stops flashing, and works as normal. I turn off SteamVR, turn it back on, it goes back to flashing white 3 times in a row, and I have to wait a few minutes for the lenses to come on and work again. Anyone have a clue on this? It's a 3 flash pattern every time, which must have a meaning? -Windows 10, full updates. -GTX1080ti, patched to current drivers. -Full Vive Pro setup, including the 2.0 controllers and lighthouses. My original standard Vive never did this in the 2 years I had it. I don't know if the Pro HMD is going out, if it's needing time to warm up, a driver issue, etc.
×
×
  • Create New...