Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Corvus

  1. You will need a reference to the Canvas object and you can enable/disable the object to "open" and "close" it.
  2. Android requires every app to use a manifest file to define the app requirements and other useful information. The Wave SDK uses the Android manifest to define HMD degrees of freedom (3DoF/6DoF), controller DoF (3DoF/6DoF), number of controllers supported (0,1,2), and the minimum Wave SDK required. https://developer.android.com/guide/topics/manifest/manifest-intro WaveVR Attributes Please ensure that these metadata in your manifest matches the capabilities of your title. This metadata will affect how VIVEPORT store distributes and displays your title. (NOTE: Required for store submissions and betas but not necessary for testing) https://hub.vive.com/storage/app/doc/en-us/ConfigureAppCapabilities.html https://developer.viveport.com/documents/sdk-wave/en/VRActivity.html Unity https://docs.unity3d.com/Manual/android-manifest.html - Download example manifest (attached below) - Copy example manifest into 'Customize' folder Assets\WaveVR\Platform\Android\Customize - Rename 'AndroidManifest_EXAMPLE.xml' to 'AndroidManifest.xml' - Edit the manifest, set values for NumDoFHmd, NumDoFController, NumController, and minWaveSDKVersion Unreal (UE4) https://docs.unrealengine.com/en-US/Platforms/Mobile/Android/AndroidManifestControl/index.html https://docs.unrealengine.com/en-US/Platforms/Mobile/Android/AndroidManifestControl/index.html#extrasettingsforapplication - Advanced APK Packaging - Extra Settings for <application> section (\n to separate lines) <meta-data android:name="com.htc.vr.content.NumDoFHmd" android:value="6DoF"/> \n <meta-data android:name="com.htc.vr.content.NumDoFController" android:value="6DoF"/> \n <meta-data android:name="com.htc.vr.content.NumController" android:value="2"/> \n <meta-data android:name="minWaveSDKVersion" android:value="1" /> Example to copy: <meta-data android:name="com.htc.vr.content.NumDoFHmd" android:value="6DoF"/> \n <meta-data android:name="com.htc.vr.content.NumDoFController" android:value="6DoF"/> \n <meta-data android:name="com.htc.vr.content.NumController" android:value="2"/> \n <meta-data android:name="minWaveSDKVersion" android:value="1" /> Skip Controller Pairing (Vive Focus & Focus Plus only): To skip the controller pairing dialog when you're app starts you can use add the following line to the manifest <application> section. <!-- Disable Controller Pairing (set to 'true' to skip controller pairing dialog) --> <meta-data android:name="no_controller_pairing" android:value="true" /> AndroidManifest_EXAMPLE.xml
  3. @MyBug Are you still experiencing this issue? The calibration offset issue was fixed with a recent version of SteamVR Beta. Can you test again to see if that fixes your problem?
  4. @harryh2019 There is a fix for this issue in the latest SteamVR Beta.
  5. @paul It looks like there is a a bug in your manifest. Specifically the "android:configChanges" line is in the wrong section and the activity tag is closed twice. Can you try again with these changes: <?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.unity3d.player" xmlns:tools="http://schemas.android.com/tools"> <application android:icon="@drawable/app_icon" android:label="@string/app_name" android:theme="@style/Theme.WaveVR.Loading" android:resizeableActivity="false" android:configChanges="density|fontScale|keyboard|keyboardHidden|layoutDirection|locale|mnc|mcc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|uiMode|touchscreen" tools:replace="android:theme"> <!--You can use your theme here.--> <activity android:name="com.htc.vr.unity.WVRUnityVRActivity" android:label="@string/app_name" android:screenOrientation="landscape" android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:enableVrMode="@string/wvr_vr_mode_component"> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> <category android:name="com.htc.intent.category.VRAPP" /> </intent-filter> <meta-data android:name="unityplayer.UnityActivity" android:value="true" /> <meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="true" /> </activity> <meta-data android:name="minWaveSDKVersion" android:value="1" /> <meta-data android:name="com.htc.vr.content.NumDoFHmd" android:value="6DoF"/> <meta-data android:name="com.htc.vr.content.NumDoFController" android:value="6DoF"/> <meta-data android:name="com.htc.vr.content.NumController" android:value="2"/> </application> <uses-permission android:name="vive.wave.vr.oem.data.OEMDataRead" /> <uses-permission android:name="vive.wave.vr.oem.data.OEMDataWrite" /> </manifest>
  6. @harryh2019 Is the offset you're experiencing only during the calibration screen? And what version of SteamVR are you using?
  7. @paul Can you share the androidmanifest.xml file here so we can take a look?
  8. @imarin18 That is correct, the function is not supported yet and it will be made clear in the next release.
  9. @Nastaran That's correct, the bug is only with the calibration test shown in the OpenVR overlay. The offset bug should not occur in the SDK samples or other content.
  10. @aarelovich You will want to use the OpenVR SDK to render to the HMD. For using eye tracking you will want to use the SRanipal Native SDK. https://github.com/ValveSoftware/openvr https://developer.vive.com/resources/knowledgebase/vive-sranipal-sdk/
  11. Hey everyone, thanks for reporting this issue. It appears to be a bug introduced with SteamVR 1.8.20 and we are working on a fix.
  12. @Annabell The HMD position is tracked with the Unity Camera so you can use that to detect head rotation (nodding/shaking).
  13. @mjean No, Viveport does not currently have Cloud saves. You can use the Stats API if the functionality works for your use case.
  14. @Claud I was able to reproduce the issue with accepting the license agreement. It wont allow you to accept the license and calibrate unless running as an admin account. Once I tried running as admin it allowed the license and calibration.
  15. @Pulse Sorry things have been moved around a bit. I have attached the Cosmos controller Unity package to this post. cosmos_controller.unitypackage
  16. @Claud It doesn't matter what account you use to download the installer. It seems the issue/bug is with accepting the license agreement. The calibration button will be grayed out until you have accepted the agreement. @Daniel_Y
  17. @Claud Can you check this troubleshooting guide and see if any of the suggestions work for you: https://forum.vive.com/forums/topic/6482-vive-pro-eye-calibration-initialization-error-troubleshooting/
  18. @Claud Can you try disabling any antivirus before the SRanipal installation? Some antivirus may corrupt the installer.
  19. @huiwang Did you receive a dev kit before release or is this a release version of the HMD? Also, what are your system specs?
  20. @RobertsonLab Thanks for the feedback. Currently the SDK does not support customizing the calibration process but we are looking at potentially adding this feature in the future.
  21. @ScottHerz Thanks for reporting this we will look into it. Just to confirm is it working for you now?
  22. @ScottHerz What version of the installer are you using? and do you have any antivirus enabled? If so please try disabling antivirus as it may corrupt the installer.
  23. @dNazarik No that functionality is currently not possible. Thanks for the feedback.
  24. @Tatiana_K Please see this post about getting tracking data at 120hz in Unity: https://forum.vive.com/forums/topic/5897-getting-verbosedata-at-the-fastest-rate-possible/?do=findComment&comment=26428
  • Create New...