Lacota

Yes, I've discovered this. This was a result of not being able to actually Quit Direct Preview. You can select Quit from the menu but it does nothing. You have to run something else like Vive Business which forces Direct Preview to shut down.

Once direct preview is running in the headset, there is no native way to stop it. Selecting quit from the menu doesn't seem to work. When you try to quit you think it is closed but are then unable to run steam. I found that if I run vive business it shuts it down and then I am able to run steam. Feels like a bug.

I'm getting a missing dependency on the Jelbee demo: HTC.UnityPlugin.

I have the same issue. SteamVR says, headset not detected. Vive streaming hub is fine. Have reinstalled steamvr and followed the recommended steps to resolve the issue but no luck. Launching steamvr from steam doesn't help. I'm dead in the water. Note: this all happened after trying to implement Wave in unity. But have rebooted many times since then so there is no running server.

Appears to be fixed

Clicking sign in on the below URL returns you to the same page. https://developer.viveport.com/console?next=%2Fconsole%2Ftitles

Are you using Wave? I had a similar issue. Switched to OpenXR and things are working. Only a work around though as I need wave to work if I want to publish on viveport

I currently have a scene with a single point light in additon to ambient light. The point light works on the PC but does not render in stand-alone mode on the XR Elite. My understanding is that this is an Android issue. Baking is not an option so I am assuming the work around is to use multiple spotlights unless someone has another suggestion. Unity 2022.2.18

Unity 2022.2.18. I have been able to get some scenes working in URP so my guess now is that it is a performance issue on the headset.

Had to abandon Wave because of build issues and return to Open XR. Somehow I managed to get it working but not sure how. I think the original issue was with Vive Input Utility but can't confirm. Right now I am only using the Vive OpenXR Plugin for Android.

I have the same experience.

There is a hack where you can block the sensor, I used a bandaid, so it thinks you are still there but it is actually worse because as soon as I put the headset on my desk it loses tracking info and I have to recalibrate. Would be nice to have a developer setting. The better option is to develop on the desktop with a mock HMD and only use the real one for beta testing.

No, I had to cut-bait and go back to OpenXR which works fine. I will have to return to this soon though as I want to publish through viveport and can only beta test in wave. Hopefully they will resolve the issues soon.

I've been testing a standalone app on the XR Elite created in Unity using URP. When I build it to the headset and run it, I get stuttering and image duplication. If I switch it back to the standard pipeline I'm fine. Is this a known issue? If so, when do we anticipate URP will be supported. If not, is there something I need to do to setup URP for standalone deployments?

This is related to other bugs reported that Wave - Direct Preview does not work. This seems to still be the case. I can build and run the project and it will "work" in Unity but pressing play does nothing.

I've tried a couple versions of unity now 2022.2 and recently 2021.3. Noticed that when I, Start Streaming Server, the machine does not appear on the headset like it does when running Vive Streaming Hub. Headset is the XR Elite.

Wave 5.2.1 does not have the ability to set the connection type or Start and Stop Device APK

I followed the setup video in Getting started with and porting to Wave, but I am unable to run my unity game on the vive xr elite headset. The only difference I noticed between the video and my setup was direct preview control panel does not have start and stop device APK options. I've tried using Vive Streaming Hub and Start Streaming server to no effect.

"Remove from library," isn't an option, only, Pin/Unpin

Unity: 2021.3.19f1 Wave: 5.2.0-r.8 This is the error I get when enabling direct preview DllNotFoundException: wvr_plugins_directpreview assembly:<unknown assembly> type:<unknown type> member:(null) Wave.Native.WVR_DirectPreview.GetInteractionMode () (at Library/PackageCache/com.htc.upm.wave.native@5.2.0-r.8/Runtime/Scripts/WVR_DirectPreview.cs:69) Wave.Native.Interop.WVR_GetInteractionMode () (at Library/PackageCache/com.htc.upm.wave.native@5.2.0-r.8/Runtime/Scripts/wvr.cs:2442) Wave.Essence.WaveEssence.GetInteractionMode () (at Library/PackageCache/com.htc.upm.wave.essence@5.2.0-r.8/Runtime/Scripts/WaveEssence.cs:1027) Wave.Essence.ClientInterface.get_InteractionMode () (at Library/PackageCache/com.htc.upm.wave.essence@5.2.0-r.8/Runtime/Scripts/Utilities.cs:135) Wave.Essence.Controller.Model.ControllerTips.Update () (at Assets/Wave/Essence/Controller/Model/5.2.0-r.8/Scripts/ControllerTips.cs:1486)

I tried a second project and have the same issue. I also tried the ScenePerceptionDemo mentioned above but get a gradle error and can't build no matter which version of Unity I use. I suspect the root cause of the Viveport launch problem is Android but am unable to isolate it at this time.

I have the same issue with Unity 2022.2.15, WaveXR & Vive XR Elite. Build is fine. App shows up in my library. When I try to launch it, it brings up the loading screen for a second then falls back to the library. Don't know how to get a detailed log from here.

Fixed by switching from Open XR to Wave XR

I had to restart everything. I have since switched from Windows to Android and Open XR to Wave XR and that seems to resolve the issue. Initially, I had a number of problems implementing Wave because of some issues, so I went back and cleared them and managed to get it working. I may need to use windows on a future project but this should work for now.

Running XR-Interaction-Toolkit-Examples for the first time in a session works fine but after stopping and restarting the tracking on my controllers is lost. Not only are their positions incorrect but their x and z axis seem to be swapped. Lifting the controllers causes them to move to the right. The only way to fix them is to close and reopen unity, steamvr and vive hub. Other dev demos have the same issue. The problem goes away when returning to steamvr home or other games but resumes if I go back into my game. Unity 2022.2.14 OpenXR - Vive XR Support - Android