HackPerception

@Calebsdream Your photo contained your serial number so I removed your photo. Note the serial number from the top left corner of the back of the affected base station contact support via https://developer.vive.com/resources/vive-sense/srworks-sdk/download/latest/ Sometimes this happens when the unit becomes damaged during transit to you - it's most likely covered by warranty in your case.

@Leggir Please note that the Cosmos requires a higher wattage supply than Vive Pro/OG Vive. Aside from the cabling, the battery in the Cosmos-specific version of the wireless adapter kit has a specific battery that you'll need to use (21watt output).

@That Purple Fox Should be safe - there is integrated protection circuitry should shut things down if things get out of spec. If the battery charges, it will probably charge pretty quickly. I've done this before while testing, but never off another powerbank. The issue here is that your Powercore isn't QC3.0 compatible. It seems like it's supplying enough current to the wireless adapter to then power that. Weird work around.

@That Purple Fox Which HMD are you referring to? This is very confusing - are you talking about charging the Vive Wireless while also drawing power from it? There's a few versions of the vive wireless power bank and I don't have access to test with them all. I'd recommend just testing your specific setup.

@Cao - Yeah, you should significant perf-win. Perhaps another portion of your application is using the headroom that's being fried up to automatically increase a quality setting or feature elsewhere in your app?

Enable USB-Debugging to enable ADB commands, and then simply install your apk via: adb install The only limitation is that Vive Flow/Focus 3 cannot support .OBB files. You have to package your binary as a .APK for it to work.

@J74656 Is it the same BSOD stop code?

@Vivenado I'll ask about this - I haven't seen this question arise in this content. Are you talking about over Miracast? Do you have examples I can point to? My gut check tells me that the content needs to be opened in a program that has a native WaveSDK integration, or that you'd have to get the file into a application that does (e.g. Vive Video). WebXR on Firefox might be able to playback supported content. For other 3D content - it's wild west in terms of the format, and the DRM.

@Magdalena - Good post. I wasn't super familiar with the term "MUX Switch" and learned something from the linked articles. What makes it even confusing is that so many laptop manufactures were doing "VR-ready" marketing just one generation ago. I really wish OEMS would just directly state if their laptops had an MUX switch or not - it prevents customers from returning their products when they find out it isn't compatible with PCVR. I think you may be able to do USB streaming on at least some of these, but native display port is definitely the desired goal.

@Fangh This is usually called "direct preview" or something similar. It's integrated into WaveSDK but we're finding that it isn't currently working for many developers. We're currently working to rectify that. Right now, you'd unfortunately have to build the APK and sideload it 😕

@massimo74 - Focus 3 is driven by the WaveSDK. To deploy content to Focus 3 in Unity, you would need to integrate our WaveSDK 4.x plugin into your project and then build out an APK for your desired target device (as WaveSDK targets multiple devices). Focus 3 and Flow both support APK files, but do not support .OBB application containers. If you're working in a version of Unity prior to Unity 2019.3 - it's much harder to port to Focus 3. https://hub.vive.com/storage/docs/en-us/

@gscholten I believe they made a version of a linkbox that's specific for LBE that has an always-on circuit. I think it's literally called the "always on" linkbox and that it's something our enterprise team handles. The power button is one of the more controversial additions - I personally am a huge fan because I usually have multiple types of Vive/SteamVR headsets connected to my PC and it let's me switch off between HMD without having to unplug cables. I think one reason the power button exists is that it helps with conditioning the power by ensuring the current is stable before it hits the headset. It prevents a huge spike of amperage from entering the headset in the first second when the linkbox gets plugged into mains power.

@lummex I'd recommend trying it on another PC if possible - that would isolate it to your system or the headset. If it doesn't work wired, and doesn't work with wireless - that might eliminate the cable as the culprit and place more suspicion on the headset. Some of what you're saying is consistent with headsets that I've had fail - specifically that it was hit and miss before completely dying.

It's all based on the chip set of the device. Flow runs a Qualcomm chip, and thus works best at the hardware level with phones that are based on Qualcomm chips. With Flow's latest update, we were able to add support for Samsung Exynos chipsets. iOS is a unique challenge because it is a walled garden not only at the hardware layer, but at the IOS app store layer as well. @Vivenado@andreasnielsen

@sn6783 - We just recently announced a ton of features such as the ability to disable the out of boundary message https://blog.vive.com/us/2021/11/11/introducing-new-features-vive-focus-3/ I'd recommend contacting your sales contact, or because some of these features are customer-specific roll-outs at the moment. Some of these features are upcoming, but they don't specifically mention passenger mode. Are you specifically needing passenger mode, or just the ability to disable the boundary message? Between the increased play-space and the ability to disable the pop-ups, your problem should be solved. That said, all optically tracked headsets have a maximum volume where you can anchor the SLAM before you start getting unavoidable drift. If you're trying to do a mega arena outside of what's supported, you will hit drift eventually.

@Renniepoo Vive Pro/Cosmos/Pro 2 linkboxes are somewhat interchangeable. The cable is the same between the three and is fully interchangeable. The primary difference is that the Cosmos linkbox doesn't have SteamVR Bluetooth receivers in it - this means it can't do basestation power management. With Cosmos, that steamvr Bluetooth circuitry is built in the External Faceplate mod rather than the Linkbox. The net result is that if you try to use a Pro/Pro 2 with a Cosmos linkbox, your basestations won't be able to automatically enter/exit standby. I use all three headsets on my test stations and use them all interchangeably without even checking to see which generation of linkbox I'm plugging into. I use homekit outlets to control my basestation power state via voice commands anyways so the bluetooth power management thing doesn't affect me. OG Vive linkboxes/cables only work with OG Vives. That's the most product specific linkbox/cable.

I've flagged this to the Flow team. VRChat has not done a Flow-native port yet - it's still tbd on if they'll natively port to Flow but conversations are ongoing. What I suspect is happening here is that VRChat has a Focus 1 build and that the store is displaying it because most of the Focus 1 content also works on Flow.

@Meratreun - The SDK is called SRWorks. You integrate that SDK into your Unity package to achieve mixed reality. https://hub.vive.com/storage/srworks/ https://developer-express.vive.com/resources/vive-sense/srworks-sdk/

@Saba You can't drive Displayport headsets off an HDMI port. No adapter will allow you to do this - HMDI lacks the required bandwidth. Your computer needs to specifically needs to output Displayport 1.2+ on a port that's wired to the Nvidia dGPU (rather than the integrated graphics). This specs page indiciates that your model has a USB-C port that outputs Displayport 1.2+. It doesn't however say if it's wired to the Intel graphics or the Nvidia graphics. First step would be to contact Asus and see which USB-C port they're talking about, and if it's wired to the Nvidia card. If it is - this adapter is the most reliable we know of (Club3D CAC-1507). If the USB-C ports are wired to the integrated graphics - that means you're out of luck with any headset that requires Displayport (Rift S, Index, Varjo, Pimax, etc...) and could only use headsets that support HDMi natively or standalone headsets which support USB/WiFi streaming (Focus 3, Quest 2)

@Celer It's probably feasible but we haven't created a client with that functionality as far as I'm aware. I'll ask around and see if I can turn up anything related to this because you're probably right about there being some potential with other Miracast host devices.

@ManxJ Some of the features in that blog are still in the pre-release pipeline, whereas some require contact with our enterprise sales team to configure. I would specifically drop a note to your enterprise sales agent as CT said above. We just did a firmware release today - and at least a subset of those features in that blog are rolled into this update.

@Nonprofitflunky Sounds like a unit damaged in transit to you. Fastest thing to do is collect the serial number off the back of the unit and launch an RMA via https://www.vive.com/us/support/contactus/

@andreasnielsen It's there - but I wish it was clearer since it's make or break https://www.vive.com/us/accessory/wireless-adapter/ https://www.vive.com/us/support/wireless-adapter/category_howto/vive-wireless-system-requirements.html

@MarkeMark1972 Yes. The original SKU works with the OG Vive. There is an accessory specifically called the "Pro attach kit" or "Cosmos attach kit" used to add additional headset support for newer units. In some countries though - there have been some special SKUs and bundles though so it can be a little regional. Generally they include the OG cable in most SKUs I've seen though.

You kind of need the linkbox for power. If you have a first gen Vive, you can bypass HMDI and USB and plug the HMD directly into the PC, but you'll need some way to get the power lead also bridged.