HackPerception

@cate The USB-A to USB-A that connects the battery to the headset can become frayed with use since it gets flexed a bunch. You can purchase an after market USB-A -> USB-A cable to see if that fixes the problem. You'd want something in the 1-2 meter range and you might want to go with something that's braided since it will be more durable (at the cost of being heavier and stiffer) Like this - but selection will vary by your country

@Thor777 Depends on how quickly the reflections happen. The tracking system is 120hz interleaved so 100 reflections all in succession is enough to trigger tracking loss. A few hundred in a session isn't bad - when you start getting into the thousands you'll probably notice it. The number in your case is moderate. Over 100,000 in those reports is severe (like a mirror) I also recommend disabling 2.4Ghz WiFi in your area if possible and seeing if sticking to 5Ghz WiFi helps. Wood floors can be shiny enough to cause problems. Try to get that number down and see if that affects your problem. Happy hunting.

11698 back-facing hits would be a moderate reflection issue. It depends on how long that session covers. That's definitely enough to cause multiple seconds of complete tracking loss. Back-facing hits are definitely physical reflections. This error code is derived the laser's time of flight calculations and a bunch of other complex sensor maths. You for sure have some sort of IR reflective surface - so you'd want to try to debug that and see if the behavior improves. There's not a great way to do this without specialized optics. Using a LED flashlight is the best way to do it without special equipment:

@Thor777 With this level of troubleshooting, I would suspect only a few options You have very strong RF/Bluetooth interference in that local environment which is preventing the trackers from talking to the dongles. Radio Towers, Strong WiFi 2.4 signals, etc... Your base stations are on the same channel (more common than you'd think). You have some weird SteamVR/PC-specific thing. Try on a friends VR setup if possible. Could be software. Nuclear option is reinstalling Windows - if it survives that then that rules out alot of things. You actually do have a reflection in the environment that's not obvious because the object is reflective only in IR Test for a reflection using the following method:

@chrisjordan09 I think it's worth downloading an update if it's a game ready driver specific to a game you're playing or if it has specific new feature or bug fixe that you want. I personally update sporadically or when I reinstall Windows (something I do every 2-4 months). It's just more stable that way. Get a hard drive or partition a virtual drive specifically for an installation of Windows solely for VR. Treat that install of Windows like a "VR Server" that's sole purpose is to do VR. If you do this, and clean install Windows regularly; you'll avoid most of the problems people in the PCVR community face. PCVR is a bunch of different technologies duct-taped together by constantly changing drivers. If you isolate VR from your general computing, you're going to have less troubleshooting. All you'd have to do is reboot your computer to switch between your installs. I always recommend doing an Nvidia Clean Install every time you install an Nvidia driver.

@kholzrpi- What did you order exactly? If you ordered an HMD only - than you need at a minimum SteamVR compatible base-stations and controllers. Thouse could be 1.0 or 2.0 base-stations, Vive wands, or Valve Index controllers. If you ordered a full kit, than you have everything for a turnkey VR experience. Everything else would be "upgrades" e.g. Vive Trackers or something like a bHaptics vest.

@Bendy121165 - No. You cannot convert an HDMI port into a Displayport that will work with VR. For VR, your GPU/Laptop must be hardwired to support native Displayport 1.2+

@spectrumhaze Base-station tracking probably isn't the best solution for this use-case. You probably need to use an optical tracking system. You're going to see too much G-Force for SteamVR's sensor fusion system to work.

@VRCenter I highly recommend using an app like BS Companion when managing that many stations. Turn them off when not in use to maximize their lifespan.

@VRCenter - I'm not aware of a way to query the Vive serial number OpenVR. OpenVR obfuscates device IDs with the LHB-xxxx schema for privacy reasons. I would recommend capturing the serial numbers of all devices when you first take shipment of them, and then maybe using your own simplified numbering system for simplicity. The Vive console can display the serial number of a Vive Cosmos / Cosmos Elite because we rolled our own runtime for that, but there's not really a tool on the SteamVR tracking side for this.

@Gabriela As a developer or as an end-user? The SDKs individually have demo scenes in their packages.

@cees You should definitely contact your regional care center to figure out why your specific order has been listed as canceled. There's a chance that the payment you see in your bank is either an auth or is a full charge that will will be refunded to your account after several business days processing. They should be able to figure out the specifics of this order. As far as I'm aware, there aren't other reports of this happening so it's likely specific to something with your order. In 2016, the number of people who were rejected by Digital River's process was pretty small and I'm surprised press bothered to write about it as many of those cases were people who specifically didn't type in a CCW code for their card and so their payment couldn't be processed. We do still use Digital River as our payment processor, but Digital River is super widely used and processes $3bn a year in transactions. That said, some banks don't play as nicely with Digital River.

@AlexManelda - There might be something triggering an AV signature - that specific installer trigger my AV on my testbed. I am going to look into this.

@AlexManelda - The Vive Pro installer is unnecessary for standard usage. Just plug the device in and Steam will auto detect a VR headset is plugged in and will let you either launch or install SteamVR. The installer just adds some additional stuff like Viveport, an overlay, and an advanced settings tool which lets you adjust Vive Pro's microphones. All of this is optional in terms of the hardware itself actually working. Use the generic installer rather than the one specific to Vive Pro: https://www.vive.com/us/setup If the installer is crashing straight away, that might indicate that it's not able to contact Vive's servers for the installation package. AV/Firewall could be causing that.

@cees Contact a live chat agent specific to your region - every region has their own customer care team. Go to www.vive.com/support -> contact us -> contact us (in the top banner) to start a chat with a live agent. There's a chance that what's currently on your card is either just an auth or will be refunded if the order was rejected for whatever reason. I assure you, this would be completely unrelated to anything that happened 4 years ago.

If you're still having this issue - please post here with your region. I suspect Testgrounds is right and that this could be tied to region but more data would be helpful. Any and all data points are appreciated - if you've posted here thus far, you inadvertently created a timestamped record documenting your problem and so we'll make sure you're taken care of.

@drwrose (moderator note: If you make any additional changes to your driver, try preforming a "clean install". It simply deletes old settings and which could be a contributing factor).

@CMDRZOD - That's amazing feedback. This is the type of hyper-specific stuff you can only really reproduce if you have a very specific hardware. Can you share what your motherboard is just to add another data point for other users? Thanks

@Darkflamespirit The white is definitely tracking loss. I ask because I have a specific hunch based off your description. The reason I mentioned the disconnect sound is that it sounds like the controllers are becoming momentarily unpaired. One potential scenario here is that you have a bad/loose HMD tether and when you move in a specific way, it causes the cable to short/disconnect momentarily. The controllers connect to the HMD and the data goes through the cable - if you have a bad tether or something - exactly what you describe can happen. You usually hear the USB disconnect sound though if you have a valid audio device to fall back to - hence why I asked. If you had just a standard tracking problem, the screen would turn white but the controllers would remain paired and shouldn't make nose. This could maybe also be a power surge or related to static electricity. I had a carpeted playroom in one house where the static was so bad, something similar to what you're describing would happen all of the time once enough static built up - that is until I finally shocked it to death one say day.

@Darkflamespirit When this happens, do you hear the Windows 10 hardware connect/disconnect sound? Does your audio change devices (say back to your TV/monitor)?

I would suspect one of three things. That specific base-station has a mechanical problem (i.e. has a dead laser). Ensure the base-station has updated firmware. The older firmware can't detect when a base-station is sending out bad tracking data. The newer firmwares have error detection and error reporting and will send a notification back to SteamVR letting you know the base-station has a mechanical problem. You have a reflective surface in your environment that is causing the lasers to bounce around. Please see below for instructions in the quote bubble below on how to verify if it's a reflection issue. Usually controllers flying off in a direction is a symptom of reflections. You have some source of infrared or electromagenetic interference coming from that direction (e.g. sunlight). bonus: That basestation may not be getting a clean & steady supply of power. This can happen when the station is on the same electrical circuit as a high draw device like an air conditioner or a fridge.

Hello everyone. Our teams identified the root cause of the issue and have applied patches. This specific issue you had was caused by an unexpectedly high surge of pre-order volume spread that sustained. Pro 2 is hot. Our teams needed to implement some quick fixes to smooth everything out. Don't worry - we will ensure you're taking care of. Either you can try again (it should work now), or reach out to a livechat agent in your region (www.vive.com/support -> contact us -> contact us) - we'll ensure you get a discount code applied for Pro 2 order. If you've already placed a pre-order without the code so you wouldn't loose your place in line, still do reach out to see if they can apply that on the backend. We're super sorry for the inconvenience and are here to help if you have any further issues trying to place an order. @testgrounds @Kikette @Dre64 @Fox is Vibin @VirtualSteve

@testgrounds - Confirming here that it's HORIZONTAL and it's glorious. Here's hoping these headsets help drive 120+ as the minimal acceptable FOV moving forward.

@Teebee76 Go by the release date on your order confirmation. While the headset might release in a region on a given date, your place in line relative to that will be unique. If the estimate changes, you'd like be notified.