Search the Community
Showing results for tags 'htc'.
Just wanted to share this https://www.thingiverse.com/thing:4124195 HTC Vive Wireless Dual 30mm Cooling Fan. 2x - 30x30x6mm 12v Fans @ 7.5v (Low speed fan resistors I had sitting around) 1x - 1.3 ID x 3.5mm OD DC Jack This was built due to Grey/Blue screen flashes on the HMD, Falling through the world or slowly losing tracking on the Vive Cosmos during wireless play. Looking at logs in C:\ProgramData\Vive Wireless\ConnectionUtility\Log The HTC Vive Wireless would start with temps reporting [2020-01-19 17:36:58 +10 0xB70 INFO LOG] M_Temperature=36, R_Temperature=33 -After 20minutes play time- [2020-01-19 17:56:46 +10 0xB70 INFO LOG] M_Temperature=91, R_Temperature=62 After the modification was performed the log output reported [2020-01-24 14:45:39 +10 0x4394 INFO LOG] M_Temperature=30, R_Temperature=23 -After 20minutes play time- [2020-01-24 15:05:19 +10 0x4394 INFO LOG] M_Temperature=48, R_Temperature=49 Both of these were experienced with the same room temperature of 24c and 20minutes of playtime in Beat Saber. After extended use it originally used to display temperatures reporting [2020-01-07 18:19:42 +10 0x32B0 INFO LOG] M_Temperature=99, R_Temperature=63 [2020-01-07 18:19:52 +10 0x32B0 INFO LOG] M_Temperature=100, R_Temperature=65 [2020-01-07 18:20:22 +10 0x32B0 INFO LOG] M_Temperature=102, R_Temperature=66 With a grey/blue HMD flicker every few minutes. This has cut cut the temperature by half and resulted in no drop outs after hours of use. Cheers
I've contacted steam support and they said it was a vive software issue. Then I contacted vive support and they said the resolution couldn't be changed. I've completely reinstalled and uninstalled steam vr and even reset my headset. Is there any way my super sampling can be improved?
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.