[Could not update WaveXR package, server down?]

Confirmed I'm able to access all npm-registry.vive.com packages

[Could not update WaveXR package, server down?]

The NPM server is still down, can you please provide a separate link from which to manually download the Vive Wave Unity XR plugin, native plugin and essence plugin? @Tony PH Lin @JustinVive

[When will we have OpenXR support for Vive Wave]

@Dario our main concern is limiting the coding rework when targeting Wave vs Oculus and potentially others, so we're trying to limit as much as possible any WAVE specific code....obviously there is inevitably rework between devices/platforms, but I was wondering if there is a list somewhere that clearly enumerates the specific assets, scripts, etc deployed by the Essence plugin

[VIVE Cosmos OpenXR Developer Preview]

If you need beta developers for OpenXR + Vive Focus/Focus Plus please contact us asap! We're also working on the NVIDIA XR Cloud SDK for Vive Focus Plus and would be very interested in developing on OpenXR for unity instead of Unity XR plugins as is the current strategy https://hub.vive.com/storage/docs/zh-cn/UnityXR/UnityXRPackages.html

[When will we have OpenXR support for Vive Wave]

Oculus, Valve, Microsoft, Unity and Unreal are all moving towards the Khronos Group standard of OpenXR (not to be confused with Valve's API for SteamVR called OpenVR). We are in the middle of a big decision on where to take our 3 year old OG focus wave sdk for unity based VR apps for the Focus. Staying pat on legacy wave sdk for unity is a bad option as it will be deprecated,  moving to one of the 3 plugin options for Wave SDK for  Unity XR will also require us to rework our code again when they port to OpenXR. I realize there is no rework free path, but what is Vive's plan for OpenXR when it comes to your Wave SDK for Unity developers (not referring to Cosmos as I've seen @Dario's posts in the other Vive Cosmos centric forums). Thoughts? Guidance? Looking for an alpha preview guinea pig? 

https://uploadvr.com/microsoft-openxr-unity/

https://developer.oculus.com/blog/openxr-for-oculus/?locale=en_US

https://uploadvr.com/valve-openxr-steamvr-beta/#:~:text=“With OpenXR%2C for the first,a statement from Valve explains.&text=“SteamVR's OpenXR implementation supports D3D11,on both Windows and Linux.

https://venturebeat.com/2020/10/23/unity-promises-initial-openxr-platform-support-by-the-end-of-2020/

[Inconsistency in Vive Wave SDK 3.1.6 Wave VR_Button List Prefab]

Back in release 2.1.8 we were told to make sure to handle BOTH the new Alias1_Trigger and Alias1_Digital_Trigger in our code. 

 

In Wave SDK 3.1.6 the new WaveVR_Button List was introduced but for some reason the DigitalTrigger is commented out. Our app needs to run on BOTH focus and focus plus. Can someone help us figure out what buttons map to which enum values as of 3.1.6

 

See the Assets\WaveVR\Scripts\WaveVR_ButtonList from the latest unitypackage for Wave SDK 3.1.16:

 

@Cotta @Tony PH Lin

[Android + Unity Settings Best Practices Guide for Wave SDK]

@VibrantNebula @JustinVive @Dario and team. It would be really great if your could publish a Best Practices Guide on Player/Build/Preferences settings in Unity. It would be VERY helpful understanding how WAVE SDK changes might be impacted by the version of unity you might be running. For instance, having a better understanding of how Unity 2019.x player settings impact the performance of our Wave VR 3.1.6 SDK based app on a Vive Focus/Plus would be EXTREMELY helpful...THoughts?

Here's ours if its helpful. We are running Unity 2019.3.6f1 + Wave SDK 3.1.6 and we develop for BOTH Vive focus and vive focus using latest build of Visual Studio 2019 Enterprise as our editor.

@Tony PH Lin @Cotta

[Wave SDK 3.1.94 Early Access and Experimental ROM 3.07.623.336 - How to Request Access]

Count us in at RazorEdge!

[[NEW] Vive Wave SDK Links (Latest SDK release: August 11, 2020)]

@JustinVive, is it recommended that we import upgrades one at a time or can we upgrade our app from 2.0.37 to 3.0.2? What is the recommendation?

[SN of HMD]

  but assuming we do migrate our client apps to use Vive Input Utility, what about IVRModuleDeviceState.serialNumber as  mentioned in the reply above this?

[Unity 2x MSAA has huge affect on performance]

We can confirm 's findings as well! FPS jumped by 50-100% by changing only this quality setting...

[SN of HMD]

   Is there a way to get the serial number for Vive Focus devices not yet running VIU? Possibly from WVR_GetParameters?

 

Something like this? 

char pchString[256] = "SerialNumber";char retString[256] = { 0 };uint32_t size;//Get the result from device servicesize = WVR_GetParameters(WVR_DeviceType_HMD, pchString, retString, 256);

 

 https://hub.vive.com/storage/app/doc/en-us/WVR_GetParameters.html

[When is VivePort Enterprise Launching?]

We create apps based on Wave SDK for the Vive Focus/Focus Plus and we are working with Enterprise clients. These apps CANNOT show up on a public store. 

VivePort Enterprise was teased back in 2017 but since then we have not been able to find any guidance for Enterprise Customers wanting to deploy to a private app store (like Google Play Private Apps).

 

Please provide guidance. We are also wondering if the device management system will eventually provide the ability to remotely push apps to a given device. At present it only allows you to push the SteamVR runtime.

 

Thoughts?

 

[Getting Started with Unity and Wave SDK (including using the VIU plugin!)]

Has anyone authored a pros/cons of leveraging this approach? Performance issues? Every abstraction layer always comes with a price, I'm just curious of what the considerations are? For instance, will VIU continue to be updated to support Vive Cosmos as well?