HackPerception

Hi , So, unfortunately this may be a difficult one to troubleshoot since it's a very uncommon error that can be highly specific to a single machine. We'll try out best to lend a hand. You may also want to contact SteamVR support who may be able to lend and hand in parallel. First off, our team is curious about what will happen if you launch SteamVR with the Vive HMD unplugged. If it launches; what subsequently happens if you plug in the Vive (with SteamVR open). Does your bluescreen list a crash dump location? If so, that dump file is by far our best lead. If you do have one, you can upload it to a service like pastebin for analysis. Other ideas: Go into your BIOS settings and ensure that you have disabled all overclocking utilities and options. While there, look into your power options and ensure that there is no power throttling at play.In windows, ensure that you're using a "high preformance" power plan. What's your PSU wattage? One possible cause is that the GPU/CPU is underpowered. You can try running a memory check to verify that it isn't a RAM issue. You can access a memory debugging tool by typing in "mdsched.exe" into the searchbar. In your device manger, do you see any devices with a yellow "!" indicating an issue? (with and without the Vive plugged in) Which version of windows are you running? 8 or 10? This error can apply to both. Due to meltdown/specter OEM patching; having the latest version of windows could possibly be a trigger for this on the CPU side. See here. Have you tried bypassing the HDMI/USB from the linkbox and plugging the 3-in-1 directly into the computer? When doing this you must keep power connected through the linkbox. Are you using any sort of display adapter to connect the Vive to the GPU?

I found a community tool that lets you check out the standard dev of your basestations. This may be related to your issues: https://www.reddit.com/r/Vive/comments/4n4y6x/test_your_vive_jittershaking_before_its_too_late/

, Yes, it's possible but most applications will not support this kind of setup. Each user will require their own HMD/PC but they can share a single set of ligthhouses. You can calibrate the rooms similarly and if the networking and level design allow it, you can have people in a 1:1 shared space. It's typically easiest to build out the app for the users to be in seperate spaces. Take a look at Nvidia Holodeck.

, bump.

, Did you try 's solution? You only need the SteamVR folder as it contains all of the compositor layer stuff required to run the HMD. The Chinese version of the Vive installer contains a Standalone SteamVR folder since Steam severs cannot be legally accessed from the mainland. ------------- Moderator edit: We now offer a tool called the Vive Enterprise Device Manager that’s able to handle network management of SteamVR distributions. It enables SteamVR to be deployed without the need for the Steam client on secured/firewalled networks. This tool is available to all Enterprise Advantage customers. For more information about the tool, or to download and activate it please visit https://enterprise.vive.com/us/product/dms/. If you have further questions, you can submit a support ticket here: https://developer.vive.com/us/contactus/

You should connect with - Activating educators in the VR space has proven to be systemically challenging but I think we'll see major improvements in the near future since HMD-side technology is getting pretty snappy. Lighthouse 2.0 will make virtual-classrooms dramatically easier. This is super helpful for understanding and maximizing laser sweep coverage: https://steamcommunity.com/sharedfiles/filedetails/?id=711411281 Remember, in a classic classroom setting, reflections from windows will be your biggest pain point for the lighthouse tracking system.

, Sorry the the long reply due to the holiday weekend. I would recommend contacting PPGun as that may be an issue on their side. We really only provide support for the tracker itself and the accessory makers handle care of the actual product. , Happy to send it over. I've sent you an email with further instructions.

, Sorry for the slow reply due to the holiday. What material are the partitions made out of? The partitions need to be made of material that is completely opaque to ~850nm IR light. The lasers that the basestations emit are pretty powerful and one possiblity is that they're penetrating the partition or are bouncing off surfaces such as the floor. IR light interacts with materials so differently than visible light that these types of issues can be hard to diagnose without knowing what types of materials are in your environment.

, Asus motherboards are a brand that we've consistently seen USB-chipset issues with, particularly the Z170 . Valve has recommended that users facing these types of motherboard chipset issues to use a Inateck PCI-e USB card to solve these types of issues, however, there may be other underlying issues at play and thus it isn't a solution to everyone's problem. One thing to look at is the companion software that comes with your motherboard that is intended to allow you to optimize and control the features of the moterhboard. Although this is less common with Asus' software suite, these can often have hidden settings which affect USB performance and connectivity. If you google your motherboard model along with the search term "Vive" you will likely come across threads with similar issues which may be the fastest way to self-diagnose the issue if it's specific to your chipset.

, Aside? Asus?

, How does the disconnect manifest? Do you see error messages? Does the compositor crash? Any error codes? At a glance, this sounds like a USB issue so disabling the camera was in the right direction; which type of motherboard are you using? Have you tried switching to a USB 2.0 port (typically they're black rather than blue). Other things that may help: double check Window's power settings are set to "high performance" and that devices won't shut down when idle as well bypassing the HDMI and USB on the linkbox and plugging the leads from the 3-in-1 cable directly into the PC.

, Sorry your having issues with the download; can you please share some info on your PC that may help us troubleshoot the issue (as well as which region you're in, any additional error codes you may see, and any other steps). Remember, you'll still be able to use the Vive by launching SteamVR through Steam so if this is a present, you'll still be able to use the HMD and we can continue to work towards troubleshooting the installation process.

Hi , This is a particularly challenging error code to troubleshoot as it typically has it's basis in how your PC's hardware and drivers are communicating with SteamVR and thus the solution varies from PC to PC. In some cases where you see this combo of codes, it's a conflict between which device (the GPU or your integrated graphics) is being chosen to drive the HMD. I'd mirror 's response and update your drivers as a first step. Uninstalling and reinstalling the drivers may help. Here is a guide that may help with that; be sure to toss in a reboot to ensure that all of the changes take effect.

, Emailed. Be sure to check your spam folder.

, Sorry for the late reply. The PPGun manufacturers seem to be shipping the Vive trackers to consumers in a non-standard state. I can send you the piece of software you need to use to alter the "role" of the controller. Please shoot me a private message with your email address and I'll email the software to you as soon as I see your message.

Hi , Our SDK support team is out for the weekend but should be able to get back to you Monday morning in Taipei (Sunday evening in the US).

, This is awesome! Thanks for sharing; it should prove to be helpful both to users as well as our engineering team as it helps us isolate where the issue is occurring. Thanks again!

, It turns out that this the low pass filter settings are covered in the v1.5 Vive Tracker Dev Guidelines document (attached below) but the firmware wasn't pushed to SteamVR until the updated that I pinged you on above.

Hi , I have been unable to track down a reliable solution for you as this is a difficult problem to reproduce. It seems like it relates to the windows registry. I'll add it to our QA list in hopes that we can more exhaustively test it. We may have a potential solution for you though! The client update that released this week (1.1.5) adds a "download wizard" which may be of us in your case. When a title is in your library and you hit "download", a new window will pop up which should allow you to change the install path. Given that your windows configuration is having trouble with keeping the correct option in place, I'd maybe refrain from using the "remember my choice" option to ensure that you can access the wizard in the future. Let us know if this works.

, Have you tried the instructions above, specifically launching the Viveport client by right-clicking its exe and choosing "run as administrator"? That contiunes to be the most reliable way of getting Window's to accept the change. I think this function requires additional scrutiny and hopefully our QA system can figure out why this fails on some setups.

, Hi Matt, I've shot you a PM.

Hi , Now that the consumer version is released, we know a lot more about the TPCast and its functionality. The official firmware/software doesn't support the mic, camera, or USB at this time. TPCast says it's still something they're working on. There exists a community software project called OpenTPCast that actually has solved most issues except the camera functionality. You can check it out here but be aware that this is 3rd party software that is totally unsupported or vetted for security (and this is not a recommendation from us to try it...)

, I don't have any additional info beyond that release note. I'll try to track down some updates today.

(and ) SteamVR updated today alongside new tracker firmware that changes how some of this filtering works. See http://steamcommunity.com/games/250820/announcements/detail/1451710752575118590

I actually prefer Win 7 to Win 10 for my personal VR installations. I think in this case, it's specifically that there may be an issue with that specific installation of Windows. Windows (and iOS installs for that fact) become very complex and messy after usage. Things like drivers and registry entry become complete messages through the course of daily usage. Windows generally isn't very friendly with how it handles updates. I personally reinstall my OS'es every 3 months (both Win and iOS) because it provides the best user experience and in many cases I've fixed SteamVR errors by simply reinstalling the OS.