HackPerception

@Tausendberg - Adding more ram and CPU will generally increase responsiveness for anything traffic that touches the router. 86U: Has a newer "Multi-Gig" 2.5Gbps WAN/LAN port which could be helpful if you can actually leverage speeds faster than 1Gbps. This port enables it to work with Asus' AiMesh mesh networking. The extra ram and CPU allow it to support support more more "mu-mimo" users (high speed connections to devices). 84S: Same radios Has gigabyte LAN Both are great routers that have the same radios. 86U is more future proof but you'll probably have a reasonable experience on both.

@Tausendberg It's just a sharpening function that's calibrated to the headset's displays. It can improve contrasting detais, highlights, and edges. These type of filters generally work by comparing neighboring pixels and thus the end result can be heavily dependent on the image source you're feeding in. This is why this value is adjustable. PCVR headsets run off uncompressed high-bandwidth video and so sharpening works well because the signal isn't compressed. I could try to ask what specific methods they're using but I don't think HQ would respond in detail.

You can download it as a standalone app on Steam https://store.steampowered.com/app/1635730/VIVE_Console_for_SteamVR/ . This is probably the most direct option Otherwise, the installers specific for the Vive Pro 2 or Vive Cosmos to get Vive Console

@Raeldor No, the headset itself isn't account based and it doesn't require anything special. Just give it a factory reset and you're good to go.

@Haiticloud You probably don't want or need to use that many stations. Figure out how to use as few as required, and stash the spare ones to use as replacements. Basestations are mechanical devices that spin very quickly like hard drives - it's best to turn them off while not in use to maximize lifespan.

@Ligthmare This might be difficult on current SteamVR-native headsets. SteamVR headsets that use integrate Valve's SteamVR hardware (Index, Pro 2) are entirely dependent on the basestations at a fundamental level and the SteamVR compositor overall. It's possible to write custom headset drivers to do more advanced stuff (Optitrak) but SteamVR hardware. Alot of enterprise users solve get this type of content into the headset by creating custom Unity projects that take their stream feeds and builds a basic SteamVR/OpenXR client for it. What you were doing on DK is called "extended mode". SteamVR support for this varies by headset - it's . Because Vive Pro 2 needs a compositor (Vive Console) - I don't think extended mode is supported. The "Disable Direct Display Mode" within SteamVR's Developer setting does not seem to be working. @C.T. One way you can try to replicate "extended mode" but with way more customization is by using OVRDrop. It has a "screen" feature which lets you pipe content as an overlay to the headset in a fixed position on the display panels. If you set the alpha to 1, and use the sliders to position and scale your content correctly - you might be able to recreate . It has support for stereoscopic content & I've seen a few people have success hacking a solution together with it. You can sort of use the headset without a basestation by disabling the loss of tracking screen (grey) screen by editing Program Files (x86)\Steam\config\steamvr.vrsettings with the following: Under "steamvr" : { Add "forceFadeOnBadTracking" : false, This could net you a fixed view that might be useful. SteamVR native headsets are really designed to be used with other SteamVR hardware. I couldn't figure out how to get this to work in conjunction with OVRDrop. \

@MSAWe've improved hand tracking integration with SteamVR with an update

There is a new streaming client release that adds a 200mbps option and some new tools and quality improvements for both wired and wireless. The headset will require the latest 3.0.999.368 firmware. @evertec @Steve76

There is a new streaming client release that adds a 200mbps option and some new tools and quality improvements for both wired and wireless. The headset will require the latest 3.0.999.368 firmware.

There is a new streaming client release that adds a 200mbps option and some new tools and quality changes. The headset will require the latest 3.0.999.368 firmware.

@vrsimdavid, I don't think we've released that on a spec sheet. They both use a 3.85v x 740mAh = 2.84Wh battery as far as I can tell.

News on this soon.

@ozten Try installing the current chrome (chrome99) and then launching the following commmand from a run prompt: chrome.exe --disable-features=XRSandbox

@HackPerception I was just able to find a workaround (for me at least). Using chome 99, from a run prompt I used the following command: chrome.exe --disable-features=XRSandbox. I suspect there are old SteamVR/WebXR bugs that aren't being fixed since the industry focus is on mobile VR rather than Desktop VR.

@SeanMauney - Some of these features were released in firmware v3.0.999.368 - These customization tools are currently being distributed via contacts in the Vive Enterprise team since each LBE site has unique requirements. They're funneling clients towards https://business.vive.com -> Contact Us.

You can also directly install the Vive Console app directly from Steam: https://store.steampowered.com/app/1635730/VIVE_Console_for_SteamVR/ @ChrisPro

@VRZach Here's some documentation Vive has created that might be helpful.

@VRZach 1. Valve only has a few limited public commands/APIs around the basestations - specifically around pushing firmware updates. I'm not aware of ways to programmatically interface with SteamVR. These are all Valve controlled systems so they're deciding the access level and tools. 2. If two stations are duplication channel within line of sight of a SteamVR sensor - that's direct interference. There is no correction mechanism expect it displays a 3. We think of it in a loose concept of primary and secondary stations. A headset can have upto 4 "primary" stations, but SteamVR also seems to pull some sampling data from other stations in the environment as well. We generally recommend physically unplugging the stations that you don't want to act as primary tracking stations when doing setup. Only have the 2-4 stations you want to weigh into your calibration plugged in when preforming a room setup/quick calibrate. SteamVR seems to factor in data from "secondary" stations - but how that works seems to be mostly proprietary and black-box. Physical isolation is the only way to ensure you fully isolate the tracking systems. For more serious installs, I recommend using something like a smart plug to control the power state of the base stations to automatically turn off the stations when the system isn't in use to maximize their lifespan. There is a pinhole on the back of the unit you can manually channel change with. You could use that to preconfigure the unit somewhat so your clients don't have to adjust the channels.

@Haiticloud SteamVR -> Developer Options -> Developer Settings -> Quick Calibrate is super helpful for mass setups. For something like this, you might need to use more than 4 2.0 base stations. If you do, we recommend spacing your stations out so that each HMD has solid visibility of 2-4 stations within ~4.5m range. When running calibration, we recommend only supplying power to the 4 "primary" stations that you'd want to calibrate against, and physically unplugging the other stations in the room during calibration to ensure Be sure to either use base station power management, or use physical/smart switches to turn the base stations off when not in use. This will maximize the lifespan of the base stations. Engage, VictoryXR are some leaders in the space right now. This is a good twitter account to follow: @steve_bambury

@Jack83 In the video you provided, it looks like there is quite alot of bright light or sunlight which is at the maximum range of the SLAM system's sensitivity. It means that huge portions of your environment are completely washed out and have a lack "tracking features" for the cameras to view and and calculate agaist. That headset does not have standard RGB cameras - they're infrared sensitive. Tune down the environmental brightness of your room and use pass through to identify and remedy large that are washed out and devoid of tracking features - that's definitely a factor. You ideally shouldn't ever have your headset out in a room where the lenses could get exposed to direct sunlight. It only takes a few seconds of direct exposure to cause a burn on the display due to the use of lenses. If it's sunlight, that has the added affect of moving throughout the day which can cause drift on slam headsets. The video also doesn't show the floor plane setup - it would be helpful to see that step too.

@Raeldor I'd recommend NAM enterprise sales over CS. CS is much further removed from this than sales. Semi-shot in the dark here about W/N: Wide gaskets tend to work better with glasses as well as European/American facial shapes. It's mostly a western product. I'm not sure if other SKUs ship with N.

@Raeldor If you pull away the gasket from the unit and check the inside of the very center of the gasket between the top two magnets, you'll find a letter (W or N) that corresponds to the style. Mine USA SKU came with W(ide). I'm not sure what's up with the narrow not being available in USA - my first guess is that it might be shipping chain related. It might be easiest to request one from a US sales team member - they'd be closer to that side of the product.

@Tone, That is supported and it's easy to set up. Go to SteamVR -> Settings -> Audio Mirroring. Simply turn that setting on, and then below it, selected the desired audio output.

Manually: Power down (all three buttons at once - vol up, vol down, HMD button on the right) Power up (vol down and hmd button at once) In the bootloader menu select reboot to download mode (navigate with vol buttons, select with HMD button) In the download menu select Factory Reset (navigate with vol buttons, select with HMD button) Via ADB Command: Connect Flow to your workstation via USB-C Run command: adb reboot download The device will reboot into a bootloader menu Navigate to the bottom menu option using the volume keys Press the device's power button to initiate the process

@andreasnielsen We have a coming soon page. https://www.viveport.com/section-coming-soon That lists all of the titles where a developers has indicated they intend to publish, as well as some that we've worked out publication deals with. Our content team actively engages with the developer community to scout out titles that are in development, or already have already been published elsewhere and attempts to onboard them into the ecosystem. We pretty much talk to everybody - it really just depends on each VR studio's or publisher's approach.