Jump to content

MarcusN

Employee
  • Posts

    18
  • Joined

  • Last visited

Everything posted by MarcusN

  1. Hi @Ilia, If you are testing eye tracking on the Focus 3, have you taken a look at the Wave SDK? The Wave SDK can be downloaded from here: https://developer.vive.com/resources/vive-wave/tutorials/installing-wave-xr-plugin-unity/?site=kr Here is some documentation on getting eye tracking working with the Wave SDK: https://hub.vive.com/storage/app/doc/en-us/UnityXR/UnityXREyeTracking.html
  2. Hi @Ronan13, What version of Godot are you using? I was testing Godot last week and wasn't able to make a working apk with Godot 4.2.1. I was able to get a working apk with Godot 4.1.3 and was able to test on XR Elite, Focus 3 and Quest 1. I also used the Godot XR Template sample app. Downgrading the Godot XR Template sample app to Godot 4.1.3 caused a compatibility issue with the OpenXR Android plugin, but I was able to remove the plugin and download a compatible version. I would also recommend using adb to troubleshoot the app issue if you aren't using it already. I use this command when testing a Godot app: adb logcat -s godot
  3. Hi @jboss, No need to apologize. I'm happy to hear that you were able to get up and running with the tutorial. I'm not familiar with the AndroidManifest issues you were seeing. The VIVE Wave XR Plugin installs all 3 packages including the Essence package. I'm curious as to how your project was in a state where the VIVE Wave XR Plugin was installed, but your project didn't have the Essence package.
  4. Hi @jboss, I'm having difficulty reproducing your issue. I used Unity 2021.3.29f1 to create a new project and downloaded version 5.5.0-r.10 of the VIVE Wave Installer. I have pasted a screenshot of what the plugin looks like in Package Manager. I have also pasted a screenshot of the location of the Wave Rig. Based on your screenshot, can you confirm that you have the VIVE Wave XR Plugin - Essence package installed?
  5. Hi @jboss, If I understand your question correctly, you are searching for the Wave Rig prefab inside of the Search window of the project folder, seen in the screenshot below, correct? If that is the case, can you confirm that you have your Search window set to All or In Packages. If you have it set to In Assets, you will not be able to locate the Wave Rig because it inside the packages.
  6. Hi @VAR Systems, I wouldn't say that I am someone important, but I can say that HTC has gaskets coming that will make the XR Elite more comfortable for you. Thanks for supporting us and I hope you enjoy the headset.
  7. Hi @Ring, Have you tried referencing this link for Passthrough and seeing if it helps resolve your issue? https://hub.vive.com/storage/docs/en-us/UnityXR/UnityXRPassthrough.html?highlight=passthrough
  8. Hi @cluelou, There is a sample project that you can reference inside the Wave SDK. It is located here: Assets/Wave/Essence/InputModule/5.2.0-r.8/Demo/EyeTracking.unity. You will also need to enable Eye Tracking under Project Settings > XR Plug-in Management > WaveXRSettings.
  9. Hi @Radicals, Based on your last edit, sounds like you were able to resolve your issue. Can you confirm?
  10. Hi @toshi, If you have another Vector3 that you can compare against, you could use something like Vector3.Angle() to calculate the degrees between your gaze_direction_normalized Vector3 and the other Vector3. The method can be referenced here: https://docs.unity3d.com/ScriptReference/Vector3.Angle.html
  11. Hi @nikkelei, I did some research and wasn't able to find much information about accessing files from Androids download folder. I did find this post where some other devs were trying this, but some of them ran into issues with different devices. The post suggests that this is something that would require a native plugin. https://forum.unity.com/threads/using-files-in-android-folders.347800/
  12. Hi @RancherosDigital, Are you still seeing these issues after updating to the latest firmware on the headset and updating SDK in your project?
  13. Hi @Radicals, Here is a link to getting OpenXR working on the Focus 3. This was created late last year, so it should be up to date right now. https://developer.vive.com/resources/openxr/openxr-mobile/tutorials/unity/getting-started-openxr-mobile/ I also downloaded VIVE OpenXR Plugin - Android and VIVE OpenXR Toolkit Samples - Android. Inside the VIVE OpenXR Toolkit Samples, there is a sample scene called OpenXRInput. I was able to test out controllers with this scene. Does this not work for you?
  14. Hello@InfoPocket-Scott and @Ryam, I've done some testing with the eye tracking and played with a sample for face tracking in Unity. The tracking works well. Have you guys tried this FaceGym sample https://github.com/ViveSoftware/FaceGym?
  15. Hi @MaxJay, Have you seen this documentation for eye tracking? https://developer.vive.com/resources/vive-sense/eye-and-facial-tracking-sdk/download/latest/ You should be able to download the latest SDK and obtain the latest documentation.
  16. Hi @taa11, My apologies. Referring back to a screenshot you posted earlier, it appears that your project is using VIVE Wave OpenXR Plugin - Android 1.0.2 and not the VIVE Wave XR Plugin 5.0.2.014. I have reposted that screenshot below. If this is the package that you are using, have you tried importing the samples from the VIVE Wave OpenXR ToolKit Samples - Android 1.0.2 package? If those samples work for you, are you able to compare your scene to one of the scenes in the samples?
  17. Hi @taa11, I would like to provide some assistance if you are still having an issue. I was informed that your environment is the following: Headset software version 5.0.999.624 Unity Version 2020.39LTS Headset Wave SDK version 5.0.2.014 Have you tried comparing your project to the HandInput and ControllerInput sample scenes found in the VIVE Wave XR Plugin - Essence package? Have you tried updating to the latest version of the VIVE Wave XR Plugin? If you have already tried these troubleshooting steps, then I would ask if you could provide a sample project that reproduces the issue or provide some steps that would help me reproduce the issue in a sample project.
×
×
  • Create New...