HackPerception

, I've PM'ed you with additional information.

, it looks like that product page has been updated in the past month - Thank you for pointing that out, I'll have to edit posts that reference that link. So this turns out to be an a-typical question as we're primarily asked about USB-C -> Displayport solutions to work with the Vive Pro; it's far more common for a laptop to have HDMI rather than Displayport. Because of this, I onlyhave USB-C -> Displayport adapters on hand to verify myself. We've recently switched over to using Nekteck USB Type-C to DP/DisplayPort Adapters internally for laptops with USB-C only. I was able to successfully test this adapter in combination with a 4K Displayport -> Minidisplayport cable (3 foot cable matters) with two laptops I have on hand (Razer 2018 and an MSI). That may be a valid pathway for your setup; I don't have any HDMI adapters to test compatibility against. Overall, the question of if the HMD itself will initialize it's a little more complex as I've seen identical laptops with 1050 chipsets both succeed and fail to initialize an HMD based on their Windows installation, BIOS settings, and GPU driver. Getting a Vive to work on a 1050 is inconsistent at best.

, I'd be interested in hearing more about your issue via PM so I can alert the care teams about the conflict that you experienced. , In so far as I can tell, that laptop doesn't have a desktop sized PCI-E 1x slot - It appears to have a PCI-E compatible M.2 HDD bay but this is not the same as a 1X-sized desktop slot.

, as far as I can tell, this model doesn't have a dedicated GPU option and the stock model has the following Kabby Lake architecture: Integrated Intel® UHD Graphics 620. If so, then this is the root of your issue. That specific chipset is dramatically under the Vive's minimum requirements and often times that incompatibility is reported by SteamVR as an HDMI issue or displays error 108/208 depending on how it's interpreting the issue. If this is the case, than your base laptop is unfortunately not compatible with the Vive. The way to check what GPU you have is to open a command prompt window (windows key + R) and then typing "dxdiag" and hitting enter. Next, go to the display tab on the resulting window and it will report your GPU. If you have multiple graphics systems, you may see multiple display devices. We've been recommending the following USB-C to MiniDisplayport adapter for the Vive Pro, it likely will work with the standard Vive if your laptop has a compatible GPU in combination with a compatible cable (3-foot) . I can't speak to the HDMI flavor of that adapter and if it's compatible with the standard Vive.

, the tracker 2018 firmware does not currently support the low pass filter option that's supported on the most recent firmware version of the first generation tracker so at this time tracker 18' may actually be more susceptible to the types of shock your exposing as you don't have an LPS option to help clean the data.

, so the installer successfully worked? I heard back from the installer team overnight. A firewall (which can be on your PC, on your modem/router, or even at the ISP level) would really be the main source of this error message. The port itself may be closed on your modem. The other option is that the port in question is not listening. They recommended you use this guide to check if the port is listening.

, this may be related to the distance you stated. The 1.0 basestations are only rated to 5 meters (~15 feet). As a first step, I would try to reduce the distance between the two, the size you currently have them at are simply beyond their rating and can definitely lead to the loss of tracking (and subsequent reestablishment of tracking leading the jumps that you described).

, I've pinged the installer team for assistance on your specific issue as it's not a common one. If possible, it would be helpful if you could upload and PM me the installer logs from your specific case as they'll provide more specific hints as to what's happening. The installer logs' location varies depending on your windows setup. You can typically find them by searching your primary harddrive for "localappdata\temp\ViveInstall" and locating the logs contained within. On that note, aside from windows defender, do you have any third party firewall or network monitor tools (sometimes they can be OEM tools)?

I am sending you a PM with further instructions.

, I'll request a status update - Firmware updates take quite a while to author and validate. The bug only affects the status change of the LED light from orange to white - this bug does not mean that your controller is at risk of overcharging.

, the USB data functionality is still present in the original trackers and is detailed in version 1.5 of the Vive Tracker Developer Guidelines. No updates to share on the 2018 integration - as far as I'm aware that project is on track.

, at this time, the wireless adapter is only officially compatible with Desktop motherboards.

, Yeah - I'm confused as well. Can you describe in greater detail why you're unable to use the 3rd HMD in the tracked volume?

- Sorry your response came in without much context. Are you also having issues with your display powering on or is it limited to the audio device not initializing?

- Have you tried setting the bound style to "developer" and unchecking the "always-on" box? That should hide them

Hi - We' d like to examine the error your encountering in greater detail, and if possible reproduce it. We have a couple of questions for you - you can reply via this thread or private message them to me if you'd prefer more privacy. Are you running a desktop or a laptop? If possible, can you provide details about your system? Which version of SteamVR are you currently on? The Main branch (default) or the beta branch?Have you updated the firmware of the HMD at all? Please go into SteamVR's settings -> Audio and check which device is selected at the top where it says "Set Playback Device To" Is it currently set to "Vive Pro Multimedia Device" or is it Set to something else? Do you have an Nvidia Card? If so, do you see an option for Nvidia audio? Does switching to it improve the behavior? Which displayport cable are you using to connect the Pro to your PC? Is it the one supplied with the HMD or is it an aftermarket cable? If so which cable?Same with the USB cable. Thanks!

I've responded to you via PM

, we have a dedicated team working on this - I don't have a specific timeline to share as this is a complex integration but we're targeting to have it out ASAP - hopefully within 1-2 months.

, As stated above, the controller error seems to be a firmware/SteamVR status reporting error - It may take some time to fix simply due to the fact that it's a pretty lengthy process to get firmware updates validated and published via SteamVR. If you unplug them and replug them back in, they should indicate white if they are fully charged. Bluetooth power management is not supported on 2.0 lighthouses currently via the Pro. I'll look into seeing if I can get a status update about both of these ticket items.

, the Vive is a desktop setup meant to be used in a fixed space. You wouldn't be able to use it on a plane as it requires to external laser sources to be mounted in the environment. We have a standalone VR HMD called the Vive Focus but its only available to developers. This is probably one of those cases where you'd probably want to get a cellphone based VR solution or look into standalone system currently available as our hardware platform is still in pre-release.

, while the goal is to maintain parity with the v1 implementation, quite a bit of codebase is being rewritten to make this happen (hence the timelines involved). While the protocol at large should be as functionally similar as possible, it's probably a little bit too early to judge which if any of these more nuanced "inaccuracies" you've encountered will be represented in the 18' implementation.

, I've checked in with the tracker team and they said that PoGo pin #1 is designed to be a digital output to control the vibration motor (on/off) and it is not intended to be a power source, hence the lower voltage.

, MDP can be pretty weird on laptops with both discrete and integrated graphics. You may need to set the following option if you're using an Nvidia card. `