Jump to content

halcyonWas

Verified Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by halcyonWas

  1. I should also say that when I first initialize the tracker it provides a slightly better range, going up to 0.6 or so, but it seems to self-calibrate and gets worse as time goes on.
  2. I've tried smiling more than I ever have in my life, attempting to pantomime to my face tracker indescribable joy in the hopes that MouthSadLeft will blip the needle off 0.0, and the most it'll manage is an intermittent visit to 0.1 or 0.2 out of a normalized range of 1.0. Similarly, I watch the MouthSad{Left,Right} parameters and summon all my acting ability to frown as much as I can, and they rise merely to a 0.2 or 0.3, making a mockery out of my capacity to express human emotion. Are they just worthless, pointless, time-wasting parameters? Is it because I have a moustache and beard? Is there a word for an -ism against facial hair? Is this a known bug and will it be fixed?
  3. They do seem to have confirmation that the combined current draw for the Cosmos w/ wireless and any external USB devices is too much for it: People on Reddit claim that it doesn't work on the Vive Pro with wireless: This is a niche product attached to a niche adapter for another niche product, but it'd be awesome if someone with a Vive Pro [Eye] w/ wireless and the lip tracker, and the latest firmware, can confirm or deny if it works.
  4. I've been using my facial tracker with my Vive Pro Eye with wireless. According to posts online and a single line on HTC's site, this shouldn't work. Yet I can verify that it most certainly does, and I've used it in VRChat for a few hours now, testing a mod. Am I on some old firmware that didn't disable it? Should I never update again? It seems to work just fine.
  5. The following problem has developed in my Vive Pro w/ Wireless: 1. Start SteamVR 2. Connect battery pack, wireless connects 3. HMD red LED, then dim/bright green LED. Screen turns on 4. A few seconds later, HMD turns off, LED is off, the wireless program reports no headset connected Disconnecting and reconnecting the USB cable to the battery pack restarts the adapter and headset. Sometimes the above steps occur, sometimes step #4 doesn't happen for many minutes, or 30 minutes, or for the entire gaming session. Tried rebooting. It happened once when I touched the USB cable to the battery pack, but this may be coincidental. I tried a different battery pack and it happened. I reseated the cable going from the wireless adapter to the HMD, at both ends. Each time it happens the wireless adapter will stay on, even though both the adapter and HMD are powered. When it happens the HMD and cables aren't being wiggled. I'm not sure if it's caused by disconnecting/reconnecting, but now sometimes when a game renders a black screen, I'll see a scintilating red ribbon of pixels, repeating in a pattern, maybe 100 pixels long and repeated vertically about 100 pixels apart. It moves with the headset, as if it's a corrupted texture. The red pixels also blink on and off. The visual corruption reminds me of when a DisplayPort cable is loose. I have a cable I can try for wired mode, but not a spare one for the wireless adapter. The corruption only seems to appear when a game is loading and I temporarily see part of a black screen, usually with a cone of the original content in the center and the corruption on the periphery, until I turn to look at it.
  6. This appears to have worked for me! I'm using the Vive Pro Wands and disabled controller sleep, which was set at 5 minutes in Steam. I didn't change the PCIe settings, though previously I'd tried disabling USB power saving in the Windows Device Manager.
  7. Disabling or enabling direct mode didn't work for me either. It goes to a black screen. The workaround I've found is to put the headset down, push the steam button on the wand, and wait a minute. Sometimes I'll cover the proximity sensor too. So far that's worked every time, and takes a minute or two to do. Still annoying.
  8. I got my wireless adapter back after ~7-10 days (and had to wait for an unrelated repair of my headset, which was ~5 days), but it still happened! I'll try "enable direct display mode" if it's not enabled for me.
  9. After a few more troubleshooting sessions with HTC, they agreed that it's worth trying to replace/repair the wireless adapter itself. Things we tried: * Using wired mode (worked, no black screen) * Clearing SteamVR cache (Steam UI -> Library -> Tools, right click on SteamVR, select Properties, click Local Files, click Verify Integrity of Tool Cache) * Manually clearing SteamVR settings (delete steamapps/common/SteamVR/resources/settings/default.vrsettings, Steam/config/steamvr.settings Steam/config/lighthouse/lighthousedb.json) * Reinstalling USB drivers (SteamVR -> Drop down -> Developer -> Developer Settings -> Remove all SteamVR USB devices) * Using the wired cable between the HMD and adapter (too long, no signal) * Trying a different battery pack * Trying a different USB cable for power * Testing over and over (I discovered that the black screen ALWAYS happened 5m22s +/- 1 second after turning the battery pack on) * Discovering a workaround: once the black screen happens, waiting ~2m15s for it to fix itself I'll add that I was friendly and patient with the reps (all over chat) and they were friendly and patient with me, and didn't push back on replacing the hardware. However, I let them do all the troubleshooting steps they recommended and was willing to entertain the notion that it might work.
  10. I'm three days into troubleshooting this with HTC support, and I'll post again with updates. They've had me clear Steam cache, delete some files, clear the USB drivers, and make a bunch of system reports, but so far nothing has helped. They also had me test wired, which works fine. When I reproduced this most recently it took 2m30s before it went black. Wireless used to be rock solid for me for weeks.
  11. I'm having the same symptoms with my wireless Vive Pro. i7 8700K Gigabyte Z370 motherboard MSI GTX 1080 Ti 16GB DDR4-3200 PC4 Nothing overclocked It was rock solid for a few weeks, then it said it needed a firmware update. I told it to go ahead and it just sat there and spun indefinitely. Now in every single VR session the following will happen after ~10 minutes: * Headset goes totally black * LED on side of headset is red * Motion tracking and all controllers still work * If I cycle the power to the headset by disconnecting and reconnecting the cable, 50% of the time it'll come back after 30s. * Sometimes when it comes back the buttons on my controllers don't work, but motion tracking does This is infuriating
×
×
  • Create New...