Jump to content
 

Corvus

Employee
  • Content Count

    72
  • Joined

  • Last visited

Posts posted by Corvus


  1. @dNazarik It looks like you're checking the Tobii XR SDK.  I cannot offer support for the Tobii SDK but there is a VIVE eye tracking SDK called "SRanipal" which you can download the SDK and documentation here:

    https://developer.vive.com/resources/knowledgebase/vive-sranipal-sdk/

    The SRanipal SDK provides support for tracking each eye position separately, I would start by checking the "ViveSR.anipal.Eye.SingleEyeData" Struct Reference.

     

     


  2. Vive Pro Eye Calibration Initialization Error Troubleshooting

    Problem:
    Launching calibration shows error: "Initialization Failed"

    Solutions:

    - Power off/on PC & Link Box.
    - Run 'sr_runtime.exe' as Admin. Default install path: 'C:\Program Files (x86)\VIVE\SRanipal'.
    - Update SteamVR Runtime.
    - Update graphics card drivers.
    - Possible issue with some models of MSI laptops fixed with rollback to earlier NVIDIA driver. Fresh install of NVIDIA driver 417.71 (GPU BIOS not being updated and it does not support the latest NVIDIA driver).
    - Uninstall 'VIVE_SRaniaplInstaller' & 'Tobii VRU02 Runtime'. Restart and Install latest 'VIVE_SRanipalInstaller_1.1.0.1.msi'. Plug in HMD and wait for any updates to complete.
    - Update motherboard integrated Intel Graphics Driver (fixes system reference to incorrect openCL.dll (intel) instead of NVidia).
    - Disable integrated graphic card
    - Possible issue with wireless adapter, try running calibration with wired.
    - Possible issues with early dev kits.

    Check System Requirements:
    - Use DisplayPort, mini-DisplayPort, or USB-C output from the dedicated GPU.
    - Windows 8.1 or later (64-bit).

     


  3. This is just a warning that you will need to resolve before submitting to the store. You should be able to develop and test without any issues.

     

    Instructions from the Viveport Submission Guide are below if you want to update the manifest.  If you have any questions or need some example manifests let me know.

    https://developer.vive.com/resources/knowledgebase/viveport-docs-eng/

     

     

    Below are optional components that we recommend you fill in to help us better understand your content. The meta data might affect how Viveport store distributes your content across different devices. After uploading your APK with correct manifest file to the console, please help confirm the values that we parsed from your APK.

    Examples are given in each component.

      1. Capability of DoF support for the head-mounted display (HMD):
        <meta-data android:name="com.htc.vr.content.NumDoFHmd" android:value="6DoF"/>
        

        Please consider the DoF support of HMD and controller individually for your content.
        – Set value “3DoF” if your content only considers the rotation pose.
        – Set value “6DoF” if your content considers both rotation and position pose.
        – Set value “3,6DoF” if your content is capable of supporting both 3 and 6 DoF playing.

      2. Capability of DoF support for the controller:
        <meta-data android:name="com.htc.vr.content.NumDoFController" android:value="6DoF"/>
      3. Total number of controllers that your content supports:
        <meta-data android:name="com.htc.vr.content.NumController" android:value="1"/>

     

×
×
  • Create New...