VIVE Cosmos Public Release 1.0.7.1 – Release Notes 

We just released the largest software update to VIVE Cosmos since launch, and we’re tackling a number of fixes to ensure you’re getting the best experience possible. We’ve heard feedback from you on social and in the beta forums surrounding specific issues—including low-light tracking, controller stability, room setup, and a few other compatibility bugs. Please see details on each topic below along with visuals to showcase the updates.

The latest software for Vive Cosmos has been publicly updated to v1.0.7.1 as of 10.31.19. Please update from your Vive console to ensure you have the latest version.

Tracking

HMD:

• Improved low light tracking, with better prediction during fast movements.
• Fixed a bug where the too bright/low light notification would not show up – see example.
• Enabled VIVE Wireless Adapter compatibility.

Known issues: 

• You may experience performance issues on older & lower end CPUs. We are working hard to improve this in the next release.
• If you experience connectivity, audio or display issues, please disable USB power management.
• Please note Cosmos requires a new 21W power bank, the connection cable for Cosmos, Velcro clip, and a new pad to attach to the headstrap. Due to the new inside-out tracking on Cosmos and other features, the headset draws slightly more power than the current Vive Wireless Adapter battery can support, so this new battery is needed to power this headset wirelessly. In addition, Vive Cosmos processes all the camera tracking data solely in the headset and never sends the visual tracking data to the PC. While this means we are securing user privacy in their play space, this approach results in a higher headset power consumption.

Controllers:

• Improved low light tracking stability. The minimum brightness requirement for reliable tracking is now 60% lower.
• Improved high brightness tracking stability. The controllers will now track much better against a bright background, such as windows and studio lights.
• Improved prediction models for the case when a controller exits the headset’s field of view (FOV).
• Positional recovery is now faster and more accurate when returning into the headset’s FOV.
• Improved tracking close to HMD. Optimal range is now reduced up to 10 cm/4 inches from the HMD. 
• Improved slow movement occlusion tracking prediction, which will help with content where the controllers are frequently occluding one another.
• Improved the tracking algorithm to be better at ignoring other Cosmos controllers and patterns that may resemble the Cosmos controller, especially when the connected pair are out of the headset’s FOV.

*We will be continuously improving all aspects of the tracking algorithm in future updates.

[youtube https://www.youtube.com/watch?v=gM6-R0XVq_M?start=3&feature=oembed&wmode=opaque&w=730&h=411]

ViveVR Runtime

• Fixed Error Code 210 runtime bug.
• Non-HDCP errors on certain laptops caused by old Nvidia V-BIOS identified, notably on some MSI laptops. It will now be separately reported as Error Code 220 (previously aggregated with Error Code 210). If you encounter this on an MSI laptop, please reach out to MSI Technical Support for an updated new V-BIOS.
• Fixed a bug with the play area boundary transparency settings and fine-tuned its appearance behavior.
• Optimized the camera passthrough vignetting to better align and render safety boundaries. 
• Added error logging and troubleshooting for SteamVR compositor crashes, installation path and cases involving Safe Mode.
• Improved mapping of error codes for edge case situations.
• VIVE Origin is no longer forced as the default home environment.
• Optimized tracking pose prediction to improve visual experience.
• Resolved an issue where the IPD display would sometimes show when the HMD was moving quickly.
• Updated low light notification strings for Dutch, Danish, Finnish, Norwegian & Swedish languages.

[youtube https://www.youtube.com/watch?v=bJhJ6o77eNA?start=3&feature=oembed&wmode=opaque&w=730&h=411]

Next Update (Mid–November Beta)