HackPerception

, I've generated a support ticket under the email address associated with your account. If this is your first time setup of the hardware, you're still able to use the hardware by installing SteamVR via the Steam client - it will detect that you have a VR HMD plugged in and will prompt you to install the SteamVR runtime.

, I responded to you via PM

, Apple controls UX on their hardware and software platform. Simply stated, Apple is managing the developer program for this integration, not Vive. Their keynote announcement last year was primarily a developer facing announcement - not a consumer facing announcements. As it stands, this is considered to be a developer/pre-developer level of hardware support for MacOS. Furthermore, as the overwhilming vast majority of VR titles have not been compiled for MacOS, only a tiny handful (>10) apps will work on MacOS natively hence it is not a consumer ready ecosystem. If you are a consumer trying to attempt to use Vive, you could try booting into Win 10 via Bootcamp but otherwise I would highly recommend not attempting to use Vive in the Mac ecosystem until the support is in place.

, The steps are identical to what's posted numerous times above. While Valve manufacturers 2.0 basestations, we process the return the basestation and have it repaired via an RMA process which will be covered under the warranty. Valve is technology owner for 2.0 stations as both the sole manufacturer and patent holder - we're a reseller in this situation. Record the serial number off the back of the unit, and reach out to our live chat to start the repair process. @Synthesis wrote: The only way to fix it is to set up a in-warranty repair (assuming you are within warranty) with our support at www.vive.com/us/support/contactus I recommend the Live Chat for fastest results.

wrote: The only way to fix it is to set up a in-warranty repair (assuming you are within warranty) with our support at www.vive.com/us/support/contactus I recommend the Live Chat for fastest results. , Syntehsis wrote out the correct response above. If there is a mechanical issue with the station it will need to be physically serviced. Given it's a 2.0 station - it's under the warranty period. Although Valve manufacturers the station, the repair booking is handled through us as the seller.

, This is possible but extremely unlikely given how the housing of the Vive is constructed - you'd be able to visibly see that the camera module is misaligned. Like I said, there was a known issue on the SteamVR/OpenVR side but that was patched by Valve in 2018 - that bug caused an issue very similar to what you're describing - I'll see if I can pull it up in the changelogs. The best thing to do in the case may be to open the VR mirror, and post a screenshot that shows both eyes and the offsets you're describing so we can get a better feel for what you're encountering.

There are legal complexities surrounding this branch of features. I am working behind the scenes on trying to drive this forward and will update this thread with any new information I am able to obtain.

, The adapter is designed to quickly allow you to switch from wireless to wired without having to uninstall the PCI-E card. If the linkbox has the HDMI lead plugged in, SteamVR will search for a wired HMD and not the wireless and display 208 if no wired unit is found. If the linkbox has only power and the USB leads plugged in, it will act as a bluetooth transciver for the watchman boards (i.e. it will be able to communciate with the basestations to enable bluetooth power management).

, We're still working with AMD and OEMs on this - this centers around how OEMs implemented the Ryzen architecture into their motherboard designs rather than the wireless adapter card itself. , I would generally not recommend purchasing a wireless adapter if you have a Ryzen based motherboard. This is a pretty motherboard specific type of error so your success will depend mostly on which specific MB you have - some work just fine, others see the watchdog error. I would recommend using the exceptions return pathway we've created for affected customers if your motherboard is not working with the adapter. If any substantial updates occur, it would be the type of thing you'd see posted here and on popular VR channels such as Reddit. That said, reviewing your post history it seems like you have a unique case as you did not actually order the wireless adapter (but rather a DAS), and that you're not seeing the watchdog error we're tracking with Ryzen systems. It could be another permutation of the motherboard behaviors we're tracking, possibly driver related (but I'm doubtful given the steps you've taken), or the wired linkbox is still plugged in (which would throw up similar error logs).

, I understand your frustration about silence, aside from the offical statement posted here, we're unable to speak into the investigation from a legal prospective as it involves numerous companies such as OEMs. We certainly have a vested interest in getting to the bottom of this and doing our best to ensure a positive customer outcome - it's just pretty complex behind the scenes. I personally apologize for not replying to this thread sooner.

, I understand your frustration about silence, aside from the offical statement posted here, we're unable to speak into the investigation from a legal prospective as it involves numerous companies such as OEMs. We certainly have a vested interest in getting to the bottom of this and doing our best to ensure a positive customer outcome - it's just pretty complex behind the scenes. I personally apologize for not replying to this thread sooner.

Hello all, I just sent out an internal email about this. I totally understand how frustrating this bug can be, especially if you're doing public demos. I want to use this post to restate that if you unplug the controller, and replug it back in - it should flip from orange to the correct white charge state if the battery is fully charged. I know it's not ideal but it is a way to get the LED to report the correct charge state if you absolutely need to know.

, We've opened an inquiry into your specific report and the overall support status of SRWorks on Titan series GPUs. The inquiry may take additional time due to the US holidays but we're definitely looking into it alongside Nvidia. We'll post any updates we may have in this thread. , I'm sending you a PM - please be on the lookout for it.

, as stated numerous times, SteamVR 2.0 basestations are managed, manufactured, and owned entirely by Valve and not HTC. We're not the ones who make the decisions about 2.0 rollout, Valve is. You should consider contacting Valve through their partnerships page as we simply don't have the authorization to sell individual basestations.

, When you hover over the icon for an installed title, a "..." icon apears in the bottom righthand corner. You open that context menu and select "remove from PC".

, I just tested this and was unable to launch the app into VR mode - something in a recent SteamVR update may have broken it. The publisher on DOTA 2 is Valve, you may want to drop a note on the SteamVR and DOTA2 discussion boards or try and submit a support ticket to let them know that feature may be broken.

, Did it work after motion smoothing was added to the main branch? That's a pretty old app and it may not be seeing updates anymore and may be conflicting with newer SteamVR rendering technologies. I'll try to give this a go tmw.

Just going to pop in and comment that we're still not encouraging customers to attempt this and that the wireless adapter is still certified strictly for desktop usage. There are a number of hardware, driver, and other software limitations that will prevent most eGPUs from working with the wireless adapter. We've been investigating this behind the scenes and have yet to find something that works reliably enough to recommend - most setups just outright don't work.

, Pretty much what's said above; the basestations can drive a number of devices and safety and practicality are typically the top two concerns. If you provide more specific details about your use case, I'd be happy to discuss what's applicable to your specific situation.

, Unfortunately as stated above, that error type will require an RMA in order to diagnose and correct. That repair will be covered under warranty. Please copy the serial number down from the affected unit and contact live chat (not the email us form) for your region. https://www.vive.com/us/support/contactus/

, we've not been able to replicate this but I am forwarding it to our web team to look into it further. Are you able to use Edge to handle the work you're attempting to do in the dev console?

I've PM'ed you with additional info

, I'll press for a public update on this - getting firmware revisions authored, QA'ed, and pushed into production is a pretty lengthy process as a bad update could negativity affect the entire user-base.